Examkin

Soru

Zorluk: OrtaOptimizing Network Performance and Latency

A financial technology firm hosts its transaction processing workload in the us-east-1 Region across two VPCs: VPC-A and VPC-B. VPC-A hosts public-facing Application Load Balancers (ALBs) that receive incoming traffic and route it to containerized microservices in VPC-B via an AWS Transit Gateway. The microservices in VPC-B frequently query a third-party payment gateway over the internet, routing outbound traffic through the Transit Gateway to a single NAT Gateway located in VPC-A. During high-volume trading hours, transaction latency increases, and connection timeouts occur. Network logs indicate that the NAT Gateway in VPC-A is experiencing source port exhaustion. Additionally, microservices in VPC-A occasionally fail to resolve the private DNS names of the resources in VPC-B. Which combination of actions will resolve the latency issues and ensure successful DNS resolution across the VPCs?

  1. Deploy NAT Gateways in each Availability Zone of VPC-B, update the route tables in VPC-B to route outbound internet traffic locally through these NAT Gateways, and associate the Route 53 Private Hosted Zone of VPC-B with VPC-A.Cevap
  2. B
    Request AWS Support to pre-warm the ALBs in VPC-A to handle the peak transaction throughput, and configure a Direct Connect Gateway to route the transitive VPC-to-VPC traffic directly between VPC-A and VPC-B.
  3. C
    Deploy a single NAT Gateway in VPC-B to consolidate outbound traffic, configure the Transit Gateway route tables to forward all egress traffic from VPC-B through this NAT Gateway, and create public DNS records for internal services.
  4. D
    Configure VPC Peering between VPC-A and VPC-B to bypass the Transit Gateway, and configure the services in VPC-A to query the default VPC resolver at 169.254.169.253169.254.169.253 of VPC-B without modifying Private Hosted Zone associations.

Cevap

Deploy NAT Gateways in each Availability Zone of VPC-B, update the route tables in VPC-B to route outbound internet traffic locally through these NAT Gateways, and associate the Route 53 Private Hosted Zone of VPC-B with VPC-A.
The correct option addresses both network latency and DNS resolution. By moving the NAT Gateways directly to VPC-B and deploying them in each Availability Zone, outbound internet traffic avoids the latency of routing through the Transit Gateway to VPC-A, and the multi-AZ deployment increases the source port pool, resolving NAT port exhaustion. Associating the Route 53 Private Hosted Zone of VPC-B with VPC-A ensures that microservices in VPC-A can resolve the private DNS names of VPC-B.

Adım Adım Çözüm

1
Address the NAT Gateway port exhaustion and egress latency.
By deploying a NAT Gateway in each Availability Zone in VPC-B, the outbound traffic to the third-party payment gateway is routed locally and does not traverse the Transit Gateway to VPC-A, eliminating Transit Gateway transit latency. This also scales the source port capacity by distributing the outbound connections across multiple NAT Gateways.
Resolving port exhaustion and reducing transit hops directly targets the root causes of the latency spikes and connection timeouts.
2
Configure the DNS resolution across VPCs.
Associate the Amazon Route 53 Private Hosted Zone (PHZ) created for VPC-B with VPC-A.
This allows resources in VPC-A to query the VPC-B private hosted zone directly, resolving private DNS names without needing public DNS records.

Anahtar Kavram

Optimizing outbound network paths to reduce latency and configuring Route 53 Private Hosted Zone associations for cross-VPC DNS resolution.
Bu soruyu puanla

Konular

Optimizing Network Performance and Latency