SIMULATION You need to configure network connectivity between a virtual network named VNET1 and a virtual network named VNET2. The solution must ensure that virtual machines connected to VNET1 can…

Submitted by weili_xi· Mar 6, 2026Configure and manage virtual networking - specifically implementing VNet-to-VNet connectivity using Azure Virtual Network Peering (AZ-104: Implement and manage virtual networking)

Question

SIMULATION You need to configure network connectivity between a virtual network named VNET1 and a virtual network named VNET2. The solution must ensure that virtual machines connected to VNET1 can communicate with virtual machines connected to VNET2. To complete this task, sign in to the Azure portal and modify the Azure resources. Answer: You need to configure VNet Peering between the two networks. The questions states, "The solution must ensure that virtual machines connected to VNET1 can communicate with virtual machines connected to VNET2". It doesn't say the VMs on VNET2 should be able to communicate with VMs on VNET1. Therefore, we need to configure the peering to allow just the one-way communication. 1. In the Azure portal, type Virtual Networks in the search box, select Virtual Networks from the search results then select VNET1. Alternatively, browse to Virtual Networks in the left navigation pane. 2. In the properties of VNET1, click on Peerings. 3. In the Peerings blade, click Add to add a new peering. 4. In the Name of the peering from VNET1 to remote virtual network box, enter a name such as VNET1-VNET2 (this is the name that the peering will be displayed as in VNET1) 5. In the Virtual Network box, select VNET2. 6. In the Name of the peering from remote virtual network to VNET1 box, enter a name such as VNET2-VNET1 (this is the name that the peering will be displayed as in VNET2). There is an option Allow virtual network access from VNET to remote virtual network. This should be left as Enabled. 7. For the option Allow virtual network access from remote network to VNET1, click the slider button to Disabled. 8. Click the OK button to save the changes.

Explanation

VNet Peering is the correct solution because it enables direct, low-latency connectivity between virtual machines in separate Azure Virtual Networks using Microsoft's backbone network without requiring gateways or public internet routing. When configuring peering, Azure actually requires a peering link to be created in both directions (VNET1→VNET2 and VNET2→VNET1) for bidirectional communication; however, the question specifically states only that VNET1 VMs must communicate with VNET2 VMs, so configuring the peering from VNET1 is the primary requirement. The simulation steps walk through the Azure portal workflow of navigating to VNET1's Peerings blade and adding a new peering connection pointing to VNET2 as the remote virtual network.

Topics

#Azure Virtual Network#VNet Peering#Network Connectivity#Azure Networking

Community Discussion

No community discussion yet for this question.

Full AZ-500 Practice