Azure ExpressRoute Global Reach Configuration
Short answer
Enable ExpressRoute Global Reach on the circuits. This allows the two separate ExpressRoute circuits to peer with each other, facilitating communication between the New York and Seattle on-premises datacenters via Azure without requiring a Premium SKU upgrade.
Question
You have on-premises datacenters in New York and Seattle.
You have an Azure subscription that contains the ExpressRoute circuits shown in the following table.
[sampleXML/xmlfile-31_1.jpg]
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? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
[sampleXML/xmlfile-31_2.jpg]
Key Takeaways
The question tests the specific use case of ExpressRoute Global Reach for connecting separate ExpressRoute circuits, often confusing learners who associate 'Global' with inter-region or cross-border traffic rather than inter-circuit peering.
This scenario addresses configuring connectivity between on-premises datacenters using Azure ExpressRoute circuits. The solution requires enabling ExpressRoute Global Reach to facilitate peering between circuits while minimizing costs by avoiding premium SKU upgrades.
Common mistake: Learners frequently select the Premium SKU upgrade because they believe it is required for advanced features like VNet-to-VNet or on-prem-to-on-prem connectivity, failing to realize that Global Reach is a feature available on Standard SKUs.
Expert Analysis
Why the Answer Is Correct
To connect two separate ExpressRoute circuits (one in New York and one in Seattle) so that on-premises sites can communicate via Azure, you must enable ExpressRoute Global Reach. This feature allows direct peering between your Microsoft-managed ExpressRoute router and the partner's router without needing additional transit infrastructure. It works across different Azure regions (East US and West US) and does not require upgrading the circuit SKU to Premium, thus satisfying the 'minimize costs' requirement.
Why Other Candidate Answers Are Wrong
Upgrading to a Premium SKU is incorrect because it is not strictly necessary for this connectivity; Global Reach is supported on Standard SKUs. Selecting FastPath is irrelevant as it optimizes packet processing latency at the edge, not routing between circuits. Choosing Direct refers to the connection type (Enterprise vs. Provider), which is already established, not the peering mechanism.
Community Comment Notes
Several users initially questioned why 'Global Reach' was needed since both locations are in North America. As noted by user SSETH78, there was confusion regarding geopolitical regions versus circuit peering capabilities. However, users like ironbornson and BlackZeros confirmed that Global Reach is the correct configuration for linking distinct ExpressRoute circuits, regardless of geographic proximity, referencing official Microsoft documentation.
Official Reference
https://learn.microsoft.com/en-us/azure/expressroute/expressroute-global-reach
This link opens the official vendor documentation in a new tab.
Exam Strategy
Always read the 'minimize costs' constraint carefully. When asked to connect two existing ExpressRoute circuits, check if Global Reach is an option before considering expensive SKU upgrades. Remember that Global Reach enables peering between circuits, not just VNet access.
Frequently Asked Questions
Can I use ExpressRoute Global Reach with Standard SKU?
Does Global Reach work within the same geopolitical region?
Discussion 18 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 18
-
MCCC454 👍 7On exam 7 februari 2024
-
ironbornson 👍 6A-Global reach: that is a difficult one as WEST US and EAST US are inside the same geopolitical region as "mauchi" wrote down, actually Standard SKU might be enough for the ER to connect together, but the question is which configuration is better, so Premium is not a configuration is an SKU, from Direct, FastPath and GlobalReach, globalreach seems the only logical: https://learn.microsoft.com/en-us/azure/expressroute/expressroute-faqs#do-i-need-expressroute-premium-for-expressroute-global-reach B-Private obiously
-
BlackZeros 👍 4seems like a right answer Global Reach https://learn.microsoft.com/en-us/azure/expressroute/expressroute-global-reach Peering https://learn.microsoft.com/en-us/azure/expressroute/expressroute-circuit-peerings
-
sserna 👍 3En examen 20/01/2023
-
NextBrand 👍 2Across on-premises connectivity with ExpressRoute Global Reach By enabling ExpressRoute Global Reach, you can exchange data across your on-premises sites through your ExpressRoute circuits. For instance, suppose you have two private data centers, one in California and one in Texas, each connected to an ExpressRoute circuit in their respective regions. You can use ExpressRoute Global Reach to link your data centers with these circuits, and your cross data-center traffic uses the Microsoft network. https://learn.microsoft.com/en-us/azure/expressroute/expressroute-introduction
Show 13 more comments
-
SSETH78 👍 2Both the location are within Geopolitical region "North America" as mentioned at https://learn.microsoft.com/en-us/azure/expressroute/expressroute-locations-providers?tabs=america%2Ca-c%2Ca-k#locations Then why do we need to have "Global reach" facility and pay high charges? Express route of type "Premum" would serve the purpose. isnt it?
-
sikbeats 👍 2Why is it called "Global Reach" if it is within US regions. I thought Global Reach was for different global regions like if a US provider doesn't have a locations in the other region.
-
AdityaGupta 👍 2Global Reach is a feature for connecting your On-Prem Datacenters over Express Route. And Private Peering allows to you connect On-Prem to Azure Platform Private Networks.
-
mauchi 👍 2that's not right, they are indeed under the same geopolitical region - check here https://learn.microsoft.com/en-us/azure/expressroute/expressroute-locations
-
Takloy 👍 2Global reach functions like a "Transit gateway" for on premise networks. hence, allowing them 2 different on-premise locations to communicate.
-
WhiteRhino1743 👍 2Looks correct. To confirm the second question - https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-set-global-reach.
-
Tightbot 👍 2Global reach https://learn.microsoft.com/en-us/azure/expressroute/expressroute-faqs#what-is-expressroute-global-reach
-
Himank20 👍 1From MS Docs:- https://learn.microsoft.com/en-us/azure/expressroute/expressroute-faqs#what-is-expressroute-global-reach If a metro in a supported country/region has more than one ExpressRoute peering location, you can connect together the ExpressRoute circuits created at different peering locations in that metro.
-
geekmichael 👍 1ExpressRoute configuration: ✅ Global Reach Peering: ✅ Private This is the lowest-cost solution because it uses the existing ExpressRoute circuits (ERC1 and ERC2) and adds Global Reach, rather than deploying additional connectivity solutions.
-
Apptech 👍 1I agree. Geoppolitical region is North America. It includes East US, West US, East US 2, West US 2, West US 3, Central US, South Central US, North Central US, West Central US, Canada Central, Canada East
-
DerekKey 👍 1Configure ExpressRoute Global Reach -> Azure private peering is configured on your ExpressRoute circuits. https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-set-global-reach
-
TJ001 👍 1East US and West US does not fall in the same geopolitical,,,,East US and East US 2 may
-
bakamon 👍 1:: Global Reach :: Private
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AZ-700 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-700 Practice Test →