You have an Azure subscription that contains two SAP HANA on Azure (Large Instances) deployments named HLI1 and HLI2. HLI1 is deployed to the East US Azure region. HLI2 is deployed to the West US 2…

Question

Options

• Aa NAT gateway
• BIP routing tables
• CExpressRoute FastPath
• DExpressRoute Global Reach

• A
  3% (1)
• B
  13% (5)
• C
  5% (2)
• D
  79% (30)

Explanation

ExpressRoute Global Reach is the correct choice because SAP HANA Large Instances connect to Azure via ExpressRoute circuits, and Global Reach allows you to link two separate ExpressRoute circuits together - enabling direct, private, low-latency communication between HLI1 in East US and HLI2 in West US 2 without traffic hairpinning through on-premises infrastructure or virtual network gateways.

Why the distractors fail:

• A. NAT gateway - Provides outbound internet connectivity for private subnets; it plays no role in private inter-region routing between ExpressRoute-connected workloads.
• B. IP routing tables - User-defined routes control traffic within a VNet but cannot establish or optimize a direct connection between two geographically separate ExpressRoute environments.
• C. ExpressRoute FastPath - FastPath bypasses the VNet gateway to reduce latency between on-premises and a single Azure VNet; it does not create a path between two distinct ExpressRoute circuits in different regions.

Memory tip: Think of it this way - Global Reach = reaching across the globe between two ExpressRoute circuits. FastPath makes one circuit faster by skipping the gateway; Global Reach connects two circuits together. When the problem involves two separate HLI/ExpressRoute deployments in different regions needing to talk to each other, the answer is always Global Reach.

No community discussion yet for this question.