You have an Azure subscription. The subscription contains a virtual machine named Server1 that runs Windows Server and is deployed to the West US…

The requirement is to route traffic between two virtual networks in different Azure regions (East US and West US) privately over the Microsoft backbone. Global virtual network (VNet) peering is the specific Azure feature designed for this purpose. It connects virtual networks across regions, and all traffic between the peered VNets is private and remains on the high-speed Microsoft backbone network, never traversing the public internet. This provides a low-latency, high-bandwidth connection between the resources in HostPool1 and Server1.

A. service endpoints: These provide a secure, direct connection from a virtual network to specific Azure PaaS services (like Azure Storage or SQL Database), not for connecting two virtual networks.

C. routing tables: These are used to define custom routes (UDRs) to control how traffic is directed within a VNet, but they do not establish the actual connectivity between two separate VNets.

D. Azure Traffic Manager: This is a DNS-based load balancer that directs client traffic to public-facing application endpoints. It does not handle private network traffic between virtual networks.

1. Microsoft Documentation

Azure Virtual Network

"Virtual network peering overview."

Section: Connectivity: "Once virtual networks are peered

resources in either virtual network can communicate with resources in the other virtual network with the same latency and bandwidth as if the resources were in the same virtual network."

Section: Global VNet peering: "Global VNet peering: Connecting virtual networks across Azure regions... Traffic between virtual machines in peered virtual networks is routed directly through the Microsoft backbone infrastructure

not through a gateway or over the public Internet."

2. Microsoft Documentation

Azure Virtual Network

"Virtual network service endpoints overview."

Section: Key benefits: "Virtual Network (VNet) service endpoints extend your virtual network private address space and the identity of your VNet to the Azure services

over a direct connection." This clarifies its purpose is for VNet-to-Azure-Service communication

not VNet-to-VNet.

3. Microsoft Documentation

Azure Traffic Manager

"What is Traffic Manager?"

Introduction: "Azure Traffic Manager is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public facing applications across the global Azure regions." This confirms it operates at the DNS layer for public endpoints.