A company is designing a new application environment on AWS. The application consists of workloads running in private subnets across two Availability Zones (us-east-1a and us-east-1b) in VPC-A. The workloads in VPC-A must access external updates from the internet securely and also resolve private domain names hosted in a Route 53 Private Hosted Zone in VPC-B. VPC-A and VPC-B are connected using an AWS Transit Gateway. Which two configuration steps should the solutions architect perform to establish secure, redundant internet egress and private DNS resolution? (Select TWO.)
- Deploy a NAT Gateway in a public subnet in us-east-1a and a second NAT Gateway in a public subnet in us-east-1b. Configure the route table of each private subnet to direct outbound 0.0.0.0/0 traffic to the NAT Gateway in its respective Availability Zone.Cevap
- Associate the Route 53 Private Hosted Zone in VPC-B with VPC-A, and verify that DNS resolution and DNS hostnames are enabled for VPC-A.Cevap
- CDeploy a single NAT Gateway in a public subnet in us-east-1a. Configure a single route table shared across both private subnets in us-east-1a and us-east-1b to route outbound 0.0.0.0/0 traffic to this NAT Gateway.
- DConfigure Transit Gateway route tables to route all outbound internet traffic from VPC-A through a Direct Connect Gateway associated with VPC-B.
- ESet up a Route 53 Resolver outbound endpoint in VPC-B and a Route 53 Resolver inbound endpoint in VPC-A to forward and resolve private DNS queries between the VPCs.
Cevap
Deploy a NAT Gateway in each Availability Zone and associate VPC-A's private route tables to their local NAT Gateway, then associate the Route 53 Private Hosted Zone in VPC-B directly with VPC-A.
Deploying a NAT Gateway in each Availability Zone avoids cross-AZ dependencies and ensures egress redundancy. For private DNS resolution within AWS, associating the Route 53 Private Hosted Zone from VPC-B with VPC-A directly resolves queries across the VPC boundaries without extra infrastructure.
Adım Adım Çözüm
Anahtar Kavram
High availability network egress design using multi-AZ NAT Gateways combined with cross-VPC Route 53 Private Hosted Zone association.