Question

Difficulty: Very hardHybrid and Multi-Account Network Connectivity Design

An enterprise is designing a secure hybrid and multi-account network topology for 4040 spoke VPCs distributed across two AWS Regions: us-east-1 and us-west-2. The spoke VPCs are owned by different AWS accounts within an AWS Organization.

The network requirements are:
- High-throughput, private hybrid connectivity to an on-premises data center.
- Centralized egress to the internet through a dedicated Security VPC in us-east-1 using NAT Gateways.
- Private DNS resolution where all spoke VPCs must resolve internal AWS resources defined in a central Route 53 Private Hosted Zone (PHZ) under a Shared Services account, as well as on-premises domains ending in `.corp`.
- A highly resilient design with no single points of failure.

Which TWO of the following configurations should the Solutions Architect implement to meet these requirements?

  1. Deploy redundant NAT Gateways across multiple Availability Zones in the us-east-1 Security VPC, and configure the us-east-1 Transit Gateway (TGW) route tables to direct outbound internet traffic (0.0.0.0/00.0.0.0/0) to the Security VPC attachment.Answer
  2. Create Route 53 Resolver outbound endpoints in the Shared Services VPC, and use cross-account authorizations to associate the central Private Hosted Zone (PHZ) individually with all 4040 spoke VPCs.Answer
  3. C
    Associate the central Private Hosted Zone (PHZ) with the regional Transit Gateways (TGWs) to allow all attached spoke VPCs to resolve the private hostnames transitively.
  4. D
    Deploy a single NAT Gateway in the us-east-1 Security VPC to minimize running costs, and configure the Transit Gateway (TGW) route table to direct outbound internet traffic (0.0.0.0/00.0.0.0/0) from all Availability Zones to the subnet hosting that NAT Gateway.
  5. E
    Associate the Direct Connect Gateway (DXGW) directly with the Virtual Private Gateways (VGWs) of all 4040 spoke VPCs to route inter-VPC traffic transitively and provide hybrid connectivity.

Answer

Deploy redundant NAT Gateways across multiple Availability Zones in the us-east-1 Security VPC and configure the TGW route tables to direct outbound internet traffic to the Security VPC attachment; and create Route 53 Resolver outbound endpoints in the Shared Services VPC and use cross-account authorizations to associate the central PHZ individually with all spoke VPCs.
Deploying redundant NAT Gateways across multiple Availability Zones in the Security VPC secures high availability for all internet-bound traffic routed through the Transit Gateway. Simultaneously, private DNS resolution requires that the central Private Hosted Zone is associated with each consumer VPC, combined with Route 53 Resolver outbound endpoints to forward queries for `.corp` to the on-premises DNS servers.

Step-by-Step Solution

1
Configure the centralized egress routing architecture.
Deploy redundant NAT Gateways in multiple Availability Zones in the Security VPC to avoid a single point of failure, and point the default route (0.0.0.0/00.0.0.0/0) of the Transit Gateway route table to the Security VPC attachment.
This guarantees that outbound internet traffic is centrally inspected and has high availability.
2
Establish the private DNS resolution topology across accounts.
Create cross-account authorizations and associate the central Private Hosted Zone (PHZ) with each of the 4040 consumer spoke VPCs individually.
Route 53 Private Hosted Zones must be explicitly associated with each VPC in order for resources within those VPCs to resolve the hosted zone's records.
3
Set up hybrid DNS resolution for on-premises domains.
Deploy Route 53 Resolver outbound endpoints in the Shared Services VPC and configure a forwarding rule for the `.corp` domain to point to the on-premises DNS servers.
This allows query forwarding for the on-premises `.corp` domain from AWS VPCs to the customer gateway.

Key Concept

Multi-account hybrid networking requires explicit routing configurations on Transit Gateways, individual VPC associations for Private Hosted Zones, and multi-AZ NAT Gateways to prevent single points of failure.
Estimated Time:3m 0s
Rate this question