Technical Lab: Select an appropriate ExpressRoute SKU and tier
Questions
Question 1 — Multiple Choice
A multinational company needs to connect offices on three different continents to their Azure infrastructure. The network team needs to ensure that traffic between branches passes through Microsoft's backbone network, without relying on the public internet for interconnection between circuits. Which ExpressRoute SKU meets this requirement?
A) Local
B) Standard
C) Premium
D) Basic
Question 2 — Technical Scenario
A cloud architect is reviewing the configuration of an existing ExpressRoute circuit. The circuit was provisioned with the Standard SKU and is connected to a primary Azure region. The company now needs to access Microsoft 365 services through this same circuit. When trying to enable Microsoft 365 peering, the team receives an error indicating that the operation is not allowed.
What is the most likely cause of this behavior?
A) Microsoft peering is not supported by the Standard SKU; Premium SKU is required
B) Microsoft 365 access via ExpressRoute requires explicit enablement through an authorization process with Microsoft, regardless of SKU
C) The Standard SKU does not support Microsoft peering in any configuration
D) The circuit is in a region that does not support Microsoft 365 connectivity
Question 3 — True or False
The ExpressRoute Local SKU includes unlimited outbound data transfer (egress) at no additional cost, but this advantage is conditional on the circuit being located at a point of presence (PoP) close to the Azure region it connects to.
True or False?
Question 4 — Technical Scenario
A company has two ExpressRoute circuits provisioned with the Standard SKU, each connected to a different Azure region. The network team wants to configure ExpressRoute Global Reach to allow direct communication between the on-premises environments connected by these circuits. After attempting configuration, the operation fails.
Error: GlobalReach cannot be enabled on this circuit.
Current SKU: Standard
What is the cause of the error and what should be done?
A) Global Reach requires both circuits to be in the same region; moving one circuit solves the problem
B) Global Reach is only compatible with Premium SKU; both circuits need to be upgraded
C) Global Reach requires a dedicated virtual network gateway; provisioning a gateway in each VNet solves the problem
D) Global Reach is not compatible with Standard circuits in different regions; only one of the circuits needs to be upgraded to Premium
Question 5 — Multiple Choice
When comparing ExpressRoute Standard and Premium SKUs, which of the following statements correctly describes a functional difference between them?
A) Premium SKU allows connectivity to up to 10 VNets, while Standard limits to 4 VNets per circuit
B) Premium SKU expands the private peering route limit from 4,000 to 10,000 routes and allows access to all global geopolitical regions
C) Standard SKU includes Global Reach support, while Premium adds Microsoft 365 support
D) Premium SKU removes the need for a Microsoft-approved connectivity provider
Answer Key and Explanations
Answer Key — Question 1
Answer: C
The Premium SKU is the only one that allows connecting ExpressRoute circuits in different geopolitical regions and enables ExpressRoute Global Reach, which routes traffic between distinct on-premises sites through Microsoft's backbone network. The Standard SKU limits connectivity to the geopolitical context of the circuit's region. The Local SKU is even more restricted, tied to a single PoP near a specific region. The Basic option does not exist as an ExpressRoute SKU.
The main misconception represented by the distractors is confusing "number of accessible regions" with "interconnection between circuits": Standard can access multiple services in the same geopolitical region, but does not allow routing between circuits from different regions via Microsoft's backbone.
Answer Key — Question 2
Answer: B
Microsoft 365 access via ExpressRoute is not automatically enabled by choosing any SKU. It requires a formal authorization process with Microsoft, as Microsoft has actively discouraged this model for most customers, preferring Microsoft 365 traffic to use the internet. When authorized, Microsoft peering must be explicitly configured and even then, specific routing policies need to be applied.
Alternative A is a plausible distractor because many professionals associate Premium with advanced functionalities, but Microsoft peering is technically available in both Standard and Premium SKUs. Alternative C is incorrect for the same reason. Alternative D is false because the limitation is not geographic.
Choosing alternative A would lead to an unnecessary SKU upgrade without solving the real problem, resulting in additional cost without benefit.
Answer Key — Question 3
Answer: True
The Local SKU was designed specifically for scenarios where the ExpressRoute PoP is in the same metropolitan area or close to a specific Azure region. In exchange for this geographic restriction, Microsoft includes outbound data transfer at no additional cost, which can represent significant savings for workloads with high egress volume. If the Local circuit is used to access regions beyond the one associated with the PoP, the model is no longer applicable and the appropriate SKU would be Standard or Premium.
The non-obvious point here is that the free egress benefit is not a generic ExpressRoute advantage: it is exclusive to the Local SKU and directly conditional on geographic proximity between the PoP and the Azure region.
Answer Key — Question 4
Answer: B
ExpressRoute Global Reach is an exclusive feature of the Premium SKU. It allows two distinct ExpressRoute circuits to exchange traffic directly through Microsoft's backbone network, without packets having to pass through the Azure environment. For Global Reach to work, both circuits involved need to be provisioned with the Premium SKU.
Alternative A is incorrect because Global Reach was designed exactly to connect circuits in different regions; moving circuits does not solve the SKU problem. Alternative C confuses the virtual network gateway requirement (necessary for VNet connectivity) with the Global Reach requirement, which operates at the circuit level, not VNet level. Alternative D is the most dangerous distractor: it suggests that only one upgrade would be sufficient, which is false.
Answer Key — Question 5
Answer: B
The Premium SKU expands two important limits compared to Standard: the maximum number of routes advertised in private peering (from 4,000 to 10,000) and the ability to access Azure services in any geopolitical region worldwide, not just in the circuit's region. This is especially relevant for global companies that need connectivity to regions outside their continent.
Alternative A reverses the logic: the VNet limit per circuit in Standard is 10, not 4, and in Premium it increases to 100. Alternative C reverses the actual SKU capabilities: Global Reach is Premium, not Standard. Alternative D is false because all ExpressRoute circuits require an approved connectivity provider, regardless of SKU.