On your first day at MDFT Pro, a well-known training agency, you learn that the agency has on-premises datacenters in New York and Seattle. The agency has an Azure subscription that contains the ExpressRoute circuits shown in the following table.
| Name | Azure region | Datacenter |
|---|---|---|
| ERC1 | East US | New York |
| ERC2 | West US2 | Seattle |
You need to ensure that all the data sent between the datacenters is routed via the ExpressRoute circuits. The solution must minimize costs.
How should you configure the network?
Public is incorrect. Public peering is deprecated and not used for this private inter-datacenter scenario.
Microsoft is incorrect. Microsoft peering is for accessing Microsoft public services, not for datacenter-to-datacenter private connectivity.
Private is correct. Private peering provides connectivity to Azure VNets and, combined with Global Reach, carries the inter-datacenter traffic privately.
FastPath is incorrect. FastPath improves performance to Azure but does not connect the two on-premises datacenters to each other.
Global Reach is correct. Global Reach links two ExpressRoute circuits over the Microsoft backbone, routing datacenter-to-datacenter traffic through Azure without extra cost beyond the circuits.
Direct is incorrect. Direct provides dedicated high-bandwidth circuits but does not link the two datacenters together over the Microsoft backbone.
Premium is incorrect. Premium enables global connectivity to Azure regions but does not connect the two on-premises datacenters.