Exam AZ-500 topic 6 question 13 discussion

Correct answer is D. Subnet12 or Subnet21 only. https://learn.microsoft.com/en-us/azure/app-service/overview-vnet-integration

To determine which subnets you can integrate WebApp2 with, we need to consider the constraints and configurations of Azure web app VNet integration. Given the configurations: Both WebApp1 and WebApp2 are in the same region (West US). Both web apps are using the same App Service Plan (ASP1). VNet integration is enabled for both web apps. According to Azure's VNet integration rules, a subnet can only be integrated with one App Service plan at a time. Since WebApp1 is already integrated with Subnet11, WebApp2 cannot be integrated with Subnet11. Therefore, the remaining options are Subnet12 and Subnet21. Thus, the correct answer is: D. Subnet12 or Subnet21 only This means WebApp2 can be integrated with either Subnet12 or Subnet21, but not Subnet11. Hesam

I did TEST this. I create an ASP, a webapp1, webapp2, vnet1/subnet11, vnet1/subnet12, vnet2/subnet21 Both web apps are using the same ASP I assigned vnet1/subnet11 to webapp1. ------When I check the network configuration for webapp2, I can see all both vnets and the three subnets available----- I did not stop there. I did add each vnet to the webapp for testing, and I was able to add all vnets/subnets

Azure Virtual Network Manager allows for the synchronization of network configurations and security rules across multiple regions. It provides centralized management for network configuration, enabling one to define and enforce connectivity and security policies globally across the virtual networks. https://learn.microsoft.com/en-us/azure/virtual-network-manager/overview

Subnet12 only VNet Integration Works Within the Same VNet Subnets in a different VNet Cannot be used Each subnet can only be used for "One" Web App at a time. Subnet11: Already used by WebApp1 Subnet21: In a different VNet (VNet2)

https://learn.microsoft.com/en-us/azure/app-service/overview-vnet-integration

Limitations There are some limitations with using virtual network integration: The feature requires an UNUSED subnet that's an IPv4 /28 block or larger in an Azure Resource Manager virtual network. MPSJ requires a /26 block or larger. • The app and the virtual network must be in the same region. • The integration virtual network can't have IPv6 address spaces defined. • The integration subnet can't have service endpoint policies enabled.

Labbed

Both apps are in the same App Service plan, and "an App Service plan can have virtual network integrations with up to two subnets/virtual networks". So for App2 you can - use the existing integration with Subnet11 - create a new connection to Subnet12 - create a new connection to Subnet21 https://learn.microsoft.com/en-us/azure/app-service/overview-vnet-integration

Now Linux function can also have 2 here answer is D. Explanation of colleague name by Feraso is correct just add my first note there.

https://learn.microsoft.com/en-us/azure/app-service/overview-vnet-integration

Correct answer is D. Subnet12 or Subnet21 only.

Subnet 12 or 21. See my explanation below under C12's answer.

"You can't have more than two virtual network integrations per Windows App Service plan. You can't have more than one virtual network integration per Linux App Service plan."

"The integration subnet can be used by only one App Service plan." "You can't have more than two virtual network integrations per Windows App Service plan." Only one app in an integration subnet. Only 2 virtual network per Windows App Service https://learn.microsoft.com/en-us/azure/app-service/overview-vnet-integration#subnet-requirements

D When you want your apps in your plan to reach a virtual network that's already connected to by apps in another plan, select a different subnet than the one being used by the pre-existing virtual network integration. https://learn.microsoft.com/en-us/azure/app-service/overview-vnet-integration

The subnet is dedicated to the vnet integration. subnet11 is already used