Examkin

Soru

Zorluk: OrtaOptimizing Network Performance and Latency

An enterprise is reviewing the network architecture of its multi-tier application in the us-east-1 region to optimize performance and reduce latency. The application is deployed across multiple private subnets in three Availability Zones. Currently, the instances in all three Availability Zones access external APIs via a single NAT Gateway located in Availability Zone us-east-1a. During peak hours, the application experiences high latency and connection timeouts when communicating with external API endpoints. Additionally, instances need to resolve internal service names hosted in a Route 53 Private Hosted Zone (PHZ) created in a shared services VPC, but internal queries currently resolve to public endpoints over the internet, causing additional latency and security concerns. Which set of actions will resolve the latency issues and optimize network performance?

  1. Deploy a NAT Gateway in each of the three Availability Zones, update the route tables for the private subnets to route outbound traffic through the local NAT Gateway in their respective zones, and associate the shared services Private Hosted Zone with the application VPC.Cevap
  2. B
    Deploy the application instances across all three Availability Zones but configure the route tables in all private subnets to route outbound internet traffic through a single NAT Gateway located in Availability Zone us-east-1a to centralize traffic, and associate the shared services Private Hosted Zone with the application VPC.
  3. C
    Deploy a NAT Gateway in each of the three Availability Zones, update the route tables for the private subnets to route outbound traffic through the local NAT Gateway in their respective zones, but rely on default DNS resolution in the application VPC without associating the shared services Private Hosted Zone to it.
  4. D
    Deploy a NAT Gateway in each of the three Availability Zones, configure an AWS Direct Connect Gateway to establish transitive routing directly between the application VPC and the shared services VPC to bypass Transit Gateway processing overhead, and associate the shared services Private Hosted Zone with the application VPC.

Cevap

Deploy a NAT Gateway in each of the three Availability Zones, update the route tables for the private subnets to route outbound traffic through the local NAT Gateway in their respective zones, and associate the shared services Private Hosted Zone with the application VPC.
Deploying local NAT Gateways in each Availability Zone ensures that outbound traffic does not cross AZ boundaries, eliminating the latency bottleneck and single point of failure. Associating the Private Hosted Zone with the application VPC enables private DNS resolution directly within the VPC, reducing resolution latency and keeping traffic secure.

Adım Adım Çözüm

1
Analyze and eliminate the NAT Gateway bottleneck.
Identify that routing traffic from all three Availability Zones through a single NAT Gateway in us-east-1a causes bottlenecking and latency. Deploying a NAT Gateway in each Availability Zone and updating subnet route tables resolves the bottleneck.
This keeps outbound internet traffic local to each Availability Zone, reducing inter-AZ latency and resolving throughput issues.
2
Resolve the DNS resolution latency issue.
Associate the Route 53 Private Hosted Zone (PHZ) created in the shared services VPC with the application VPC.
This allows internal service names to resolve privately and locally within the application VPC, bypassing public internet DNS lookup latency.
3
Verify transitive routing configuration.
Keep the existing AWS Transit Gateway configuration for VPC-to-VPC routing instead of attempting transitive routing via a Direct Connect Gateway.
Direct Connect Gateway does not support transitive VPC-to-VPC routing, and Transit Gateway is required for this topology.

Anahtar Kavram

Optimizing hybrid and multi-VPC networking through redundant NAT Gateways and Private Hosted Zone associations.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

Optimizing Network Performance and Latency