Soru

Zorluk: OrtaHybrid and Multi-Account Network Connectivity Design

A global logistics provider has a multi-account AWS environment consisting of 2020 spoke VPCs spread across 22 AWS Regions: `us-east-1` and `us-west-2`. The provider must establish a highly available, transitive network topology that connects all VPCs to each other and to an on-premises datacenter over a new AWS Direct Connect connection. The architecture must minimize administrative overhead and scale easily as new VPCs are added. Which of the following actions should the solutions architect take to meet these requirements? (Select TWO.)

  1. Deploy an AWS Transit Gateway in each Region, attach the local spoke VPCs to their respective Transit Gateway, and configure a Transit Gateway peering connection between the two Transit Gateways.Cevap
  2. Create a Direct Connect gateway, associate it with the Transit Gateways in both Regions using transit virtual interfaces (transit VIFs) on the Direct Connect connections, and configure BGP to advertise VPC CIDR blocks to the on-premises datacenter.Cevap
  3. C
    Associate a Direct Connect gateway directly with the virtual private gateways attached to each of the 2020 spoke VPCs to establish transitive routing between the VPCs and the on-premises datacenter.
  4. D
    Configure a single Route 53 Private Hosted Zone in the primary hub account and associate it only with the hub VPC to enable DNS resolution across all spoke VPCs without additional association steps.
  5. E
    Deploy a single NAT Gateway in a centralized transit VPC in `us-east-1` and configure all spoke VPCs in both Regions to route their outbound internet traffic through this NAT Gateway to minimize cost.

Cevap

To meet the requirements, the solutions architect should deploy an AWS Transit Gateway in each Region, attach the local spoke VPCs to their respective Transit Gateway, and configure a Transit Gateway peering connection between them. Additionally, the architect should create a Direct Connect gateway, associate it with the Transit Gateways in both Regions using transit virtual interfaces (transit VIFs) on the Direct Connect connections, and configure BGP to advertise the VPC CIDR blocks.
The correct solution involves deploying an AWS Transit Gateway in each Region to act as a regional hub for the local spoke VPCs and peering them to allow inter-region transitive routing. To connect to the on-premises datacenter, a Direct Connect gateway is associated with the Transit Gateways using transit virtual interfaces (transit VIFs), which allows BGP to advertise routes and enables hybrid connectivity.

Adım Adım Çözüm

1
Design the regional hub-and-spoke VPC connectivity using AWS Transit Gateway.
An AWS Transit Gateway is created in `us-east-1` and `us-west-2`. Local VPCs in each Region are attached to their respective regional Transit Gateway, enabling centralized routing and simplified administration.
Transit Gateway simplifies VPC connectivity at scale and removes the management complexity of a full-mesh VPC peering configuration.
2
Enable inter-region VPC-to-VPC routing.
A Transit Gateway peering connection is established between the `us-east-1` Transit Gateway and the `us-west-2` Transit Gateway, with static routes configured to direct cross-region traffic.
Peering the Transit Gateways enables transitive routing across Regions for the spoke VPCs.
3
Design the hybrid connectivity to the on-premises datacenter.
A Direct Connect gateway is created and associated with the Transit Gateways in both Regions using transit VIFs on the AWS Direct Connect connections.
Transit VIFs are required to connect AWS Direct Connect to an AWS Transit Gateway, and the Direct Connect gateway allows multiple Transit Gateways to share the same hybrid connection.

Anahtar Kavram

AWS Transit Gateway simplifies multi-VPC and multi-account routing, while Transit Gateway Peering and Direct Connect Gateway with transit VIFs enable highly available, scalable inter-region and hybrid connectivity.
Bu soruyu puanla