You have two peered Azure virtual networks named VNet1 (address space: ) and VNet2 (address space: ) in the same region. VNet1 contains a subnet named Subnet1 () and a virtual machine named VM1. The network interface of VM1 is associated with an Application Security Group (ASG) named ASG-Web. An NSG named NSG-Subnet1 is associated with Subnet1. VNet2 contains a subnet named Subnet2 () and a virtual machine named VM2. The network interface of VM2 is associated with an NSG named NSG-NIC2. You need to allow inbound HTTPS traffic (TCP port ) to VM2 from VM1. You configure the following security rules:
* In NSG-Subnet1, you add an outbound rule with a priority of that allows TCP port outbound from ASG-Web to the private IP address of VM2.
* In NSG-NIC2, you add an inbound rule with a priority of that allows TCP port inbound from ASG-Web to the private IP address of VM2.
When you attempt to save the configuration for NSG-NIC2, the deployment fails. What is the cause of this configuration failure?
- AThe outbound rule in NSG-Subnet1 must be configured with a higher priority (lower priority number) than the inbound rule in NSG-NIC2 to allow traffic to cross virtual network boundaries.
- BVirtual network peering does not support routing of network traffic that is filtered using Application Security Groups.
- Application Security Groups can only be referenced in Network Security Group rules where both the Network Security Group and the Application Security Group reside in the same virtual network.Cevap
- DThe Network Security Group NSG-NIC2 must be associated with Subnet2 rather than the network interface of VM2 before referencing Application Security Groups.