Soru

Zorluk: KolayHybrid and Multi-Account Network Connectivity Design

An enterprise wants to establish hybrid connectivity between three spoke VPCs in different AWS accounts and their on-premises data center. The design must satisfy the following requirements:
1. The VPCs must be able to communicate with each other (VPC-to-VPC routing).
2. The VPCs must connect to the on-premises data center using a single AWS Direct Connect connection.
3. Private DNS resolution for a shared internal domain must be accessible across all VPCs.

Which architecture meets these requirements with the least operational complexity?

  1. Attach the three spoke VPCs to an AWS Transit Gateway, connect the Transit Gateway to the on-premises data center using an AWS Direct Connect Gateway with a transit virtual interface, and associate the Route 53 Private Hosted Zone with all three spoke VPCs.Cevap
  2. B
    Connect the three spoke VPCs directly to an AWS Direct Connect Gateway using Virtual Private Gateways and private virtual interfaces, and configure a shared Route 53 Private Hosted Zone associated with the Direct Connect Gateway.
  3. C
    Attach the three spoke VPCs to an AWS Transit Gateway, connect the Transit Gateway to the on-premises data center using an AWS Direct Connect Gateway with a transit virtual interface, and create the Route 53 Private Hosted Zone only in the shared services account without associating it with the spoke VPCs.
  4. D
    Attach the three spoke VPCs to an AWS Transit Gateway, connect the Transit Gateway to the on-premises data center using a Direct Connect Gateway, and route all outbound internet traffic from all Availability Zones in the spoke VPCs through a single NAT Gateway deployed in one subnet of a centralized VPC.

Cevap

Attach the three spoke VPCs to an AWS Transit Gateway, connect the Transit Gateway to the on-premises data center using an AWS Direct Connect Gateway with a transit virtual interface, and associate the Route 53 Private Hosted Zone with all three spoke VPCs.
The correct answer combines AWS Transit Gateway for transitive VPC-to-VPC routing, an AWS Direct Connect Gateway with a transit virtual interface for hybrid connectivity, and associates the Route 53 Private Hosted Zone with all three spoke VPCs to allow DNS resolution.

Adım Adım Çözüm

1
Address the multi-VPC transitive routing requirement.
Attach the three spoke VPCs to a central AWS Transit Gateway.
AWS Transit Gateway acts as a cloud router, enabling transitive routing between attached VPCs, which is not supported by Direct Connect Gateway alone.
2
Configure hybrid connectivity to the on-premises data center.
Connect the AWS Transit Gateway to an AWS Direct Connect Gateway using a transit virtual interface (Transit VIF).
Transit VIF is the required interface type to connect a Direct Connect Gateway to an AWS Transit Gateway for hybrid routing.
3
Address the private DNS resolution requirement.
Associate the Route 53 Private Hosted Zone with all three spoke VPCs.
Route 53 Private Hosted Zones must be associated with each VPC requiring DNS resolution for those private records, regardless of network transit paths.

Anahtar Kavram

AWS Transit Gateway is required for multi-VPC transitive routing and hybrid connectivity via Direct Connect Gateway, while Route 53 Private Hosted Zones must be explicitly associated with all consuming VPCs.
Tahmini Süre:2m 0s
Bu soruyu puanla