Connecting global WAN to data in multiple Regions over Direct Connect Gateway
To abide by industry regulations, a solutions architect must design a solution that will store a company's critical data in multiple public AWS Regions, including in the United States, where the company's headquarters is located. The solutions architect is required to provide access to the data stored in AWS to the company’s global WAN network. The security team mandates that no traffic accessing this data should traverse the public internet. How should the solutions architect design a highly available solution that meets the requirements and is cost-effective?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
A Direct Connect Gateway attaches to DX connections and to VPCs across Regions, so two DX links at one Region can privately reach data in other Regions — more cost-effective than DX to every Region or a transit VPC.
Critical data spans multiple public Regions and must be reachable from a global WAN without traversing the public internet. Two DX connections from HQ to one Region plus a Direct Connect Gateway extend private connectivity to VPCs in other Regions cost-effectively, without per-Region DX circuits.
Using inter-region VPC peering (Option B) over DX does not provide a clean private path across Regions via the WAN, and a transit VPC (Option C) adds cost and operational overhead versus a DXGW.
Community Discussion (10 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D establishes two DX connections from HQ to a single Region (for resilience) and uses a Direct Connect Gateway to associate those connections with VPCs in other Regions. This keeps all traffic on private AWS backbone (no public internet) and avoids provisioning a separate DX circuit to every Region, satisfying the cost-effectiveness requirement.Why the Other Options Are Wrong
Option A requires a DX connection to every Region, which is expensive and not cost-effective. Option B relies on inter-region VPC peering, which does not extend the on-prem WAN path cleanly across Regions. Option C uses a transit VPC, adding operational overhead and cost versus the native DXGW.Community Comment Notes
trungtd (likes 5) succinctly endorses DX + DXGW. sarlos notes that TGW is regional, so D is correct. TomTom prefers B for cost but overlooks that DXGW is the purpose-built multi-Region private reachability mechanism.Official Reference
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →