What should you do?

A company has virtual machines (VMs) in the following Azure regions:

✑ West Central US

✑ Australia East

The company uses ExpressRoute private peering to provide connectivity to VMs hosted on each region and on-premises services.

The company implements global VNet peering between a VNet in each region. After configuring VNet peering, VM traffic attempts to use ExpressRoute private peering.

You need to ensure that traffic uses global VNet peering instead of ExpressRoute private peering. The solution must preserve existing on-premises connectivity to Azure VNets.

What should you do?
A . Add a user-defined route to the subnets route table.
B. Add a filter to the on-premises routers.
C. Add a second VNet to the virtual machines and configure VNet peering between the VNets.
D. Disable the ExpressRoute peering connections for one of the regions.

Answer: A

Explanation:

To ensure that traffic uses global VNet peering instead of ExpressRoute private peering, you should add a user-defined route to the subnets route table. According to 2, global VNet peering allows virtual networks across regions to communicate using private IP addresses as if they were in the same region. However, if there is an existing ExpressRoute private peering between two regions that also have global VNet peering enabled, traffic will prefer ExpressRoute over global VNet peering by default. To override this behavior and force traffic to use global VNet peering instead of ExpressRoute private peering for a specific subnet or virtual network gateway connection, you need to add a user-defined route with a next hop type of Virtual Network Peering.