A SysOps Administrator has an AWS Direct Connect connection in place in region us-east-1, between an AWS account and a data center. The Administrator is now required to connect the data to a VPC in…

Question

Options

• ACreate an AWS VPN CloudHub architecture, and use software VPN to connect to the VPC in
• BCreate a new Direct Connect connection between the data center and region us-west-2.
• CCreate a VPC peering connection between the VPC in region us-east-1 and us-west-2, and
• DUse Direct Connect gateway with the existing Direct Connect connection to connect to the Virtual

• A
  6% (2)
• B
  17% (6)
• C
  6% (2)
• D
  72% (26)

Explanation

Option D is correct because AWS Direct Connect Gateway is a globally available resource that lets you leverage an existing Direct Connect connection to reach VPCs in any AWS region - no new physical circuit required, making it both the fastest and most cost-efficient solution while preserving the consistent, low-latency performance of the dedicated connection.

Why the distractors are wrong:

• A (VPN CloudHub): VPN tunnels traverse the public internet, so they cannot guarantee consistent performance or low latency - this directly violates the stated requirement.
• B (New Direct Connect in us-west-2): This would technically work but is the least quick option; provisioning a new Direct Connect circuit involves physical infrastructure and typically takes weeks, making it far from the fastest approach.
• C (VPC Peering): VPC peering connects two VPCs to each other but does not extend on-premises connectivity - the data center would still have no path to the us-west-2 VPC.

Memory tip: Think of Direct Connect Gateway as a "one-to-many bridge" - one Direct Connect connection can reach VPCs across many regions. Any time a question asks how to extend an existing Direct Connect to a new region quickly, Direct Connect Gateway is almost always the answer.

No community discussion yet for this question.