Question

Difficulty: MediumConfigure Virtual Network Peering

An organization deploys three virtual networks in the West US region:

* VNet-Sales with address space 172.20.10.0/24172.20.10.0/24. VM-Sales is deployed in a subnet within VNet-Sales.
* VNet-Hub with address space 172.20.0.0/24172.20.0.0/24. VNet-Hub contains no virtual machines or gateways.
* VNet-Finance with address space 172.20.20.0/24172.20.20.0/24. VM-Finance is deployed in a subnet within VNet-Finance.

You configure a bidirectional virtual network peering between VNet-Sales and VNet-Hub. You also configure a bidirectional virtual network peering between VNet-Finance and VNet-Hub. There is no peering connection between VNet-Sales and VNet-Finance.

VM-Sales is unable to establish network communication with VM-Finance.

Which configuration change should you implement to allow VM-Sales to communicate directly with VM-Finance with the lowest latency?

  1. A
    Enable the Allow forwarded traffic setting on the peering connections between VNet-Sales and VNet-Hub, and between VNet-Finance and VNet-Hub.
  2. B
    Enable the Use remote gateways setting on the peering connections for both VNet-Sales and VNet-Finance.
  3. Configure a direct virtual network peering between VNet-Sales and VNet-Finance.Answer
  4. D
    Create an Azure Private DNS Zone, link it to all three virtual networks, and enable auto-registration.

Answer

Configure a direct virtual network peering between VNet-Sales and VNet-Finance.
Establishing a direct virtual network peering between the two spoke networks (VNet-Sales and VNet-Finance) is the correct solution. Since Azure virtual network peering is non-transitive, traffic cannot route from one spoke to another through a hub network unless a virtual network gateway or a Network Virtual Appliance (NVA) is configured in the hub network to route the traffic. Direct peering provides the lowest latency and does not require additional routing resources.

Step-by-Step Solution

1
Analyze the current network topology and identify connectivity limitations.
Identify that VNet-Sales is peered with VNet-Hub, and VNet-Finance is peered with VNet-Hub, but there is no peering between VNet-Sales and VNet-Finance.
To understand why VM-Sales cannot communicate with VM-Finance.
2
Recall the transitivity properties of Azure Virtual Network Peering.
Recognize that VNet peering is non-transitive, meaning traffic cannot traverse from VNet-Sales to VNet-Finance via VNet-Hub without a routing appliance or gateway.
To determine why the current hub-and-spoke configuration prevents direct communication.
3
Identify the configuration that provides the lowest latency direct communication path.
Determine that establishing a direct virtual network peering between VNet-Sales and VNet-Finance connects the spokes directly.
Direct peering routes traffic over the Microsoft backbone network with optimal latency and without needing intermediate virtual appliances.

Key Concept

Azure Virtual Network Peering is non-transitive. Direct peering between two virtual networks is required for direct low-latency communication unless transitive routing is established through a gateway or Network Virtual Appliance (NVA).
Estimated Time:1m 30s
Rate this question