Examkin

Soru

Zorluk: OrtaOptimizing Network Performance and Latency

A global telematics SaaS platform has a multi-account AWS architecture. The core application backend runs on Amazon EC2 instances in private subnets across multiple Availability Zones in a Spoke VPC in `us−east−1us-east-1`. The application is deployed behind an Application Load Balancer (ALB). The Spoke VPC connects to a Shared Services VPC and an on-premises data center via an AWS Transit Gateway.

The application resolves internal endpoints using a Route 53 Private Hosted Zone (PHZ) hosted in the Shared Services VPC.

The platform experiences two recurring issues:
1. Every morning at `9:00 AM9:00\text{ AM}`, a sudden burst of vehicle telemetry data causes immediate connection timeouts and latency spikes for users, which gradually resolve after `10 to 1510\text{ to }15` minutes.
2. Intermittent DNS resolution failures occur when the application attempts to resolve service names in the Shared Services VPC.

The company requires a solution that minimizes latency, prevents dropped connections during traffic spikes, and ensures highly available, private DNS resolution.

Which TWO actions should the Solutions Architect recommend to optimize performance and resolve these issues?

  1. Request AWS Support to pre-warm the Application Load Balancer in the Spoke VPC before the daily peak traffic window to handle the sudden surge in connections without latency or dropouts.Cevap
  2. Associate the Route 53 Private Hosted Zone from the Shared Services VPC with the Spoke VPC to enable direct and low-latency DNS resolution of internal services.Cevap
  3. C
    Direct all outbound traffic from the Spoke VPC to a single NAT Gateway located in one Availability Zone to minimize latency by avoiding cross-AZ routing for outbound internet traffic.
  4. D
    Establish a Direct Connect Gateway to route VPC-to-VPC traffic transitively between multiple Spoke VPCs to bypass the Transit Gateway and reduce latency.
  5. E
    Deploy a Route 53 Resolver outbound endpoint in the Spoke VPC to query the Shared Services VPC DNS endpoints instead of associating the Private Hosted Zone with the Spoke VPC.

Cevap

To optimize network performance and resolve the latency and DNS issues, the architect must request AWS Support to pre-warm the Application Load Balancer before the daily peak traffic window, and associate the Route 53 Private Hosted Zone from the Shared Services VPC with the Spoke VPC.
Pre-warming the Application Load Balancer ensures that sufficient processing capacity is provisioned ahead of the telemetry burst, eliminating the connection timeouts caused by scaling lag. Associating the Route 53 Private Hosted Zone directly with the Spoke VPC ensures that DNS queries for internal services are resolved locally with minimal latency, bypassing any external DNS forwarding overhead.

Adım Adım Çözüm

1
Analyze the telemetry ingest bottleneck at peak times.
Identify that the sudden burst of connection requests causes ALB scaling lag, leading to timeouts.
ALB scaling requires time to provision additional capacity during sharp traffic spikes; pre-warming ensures capacity is ready in advance.
2
Analyze the intermittent DNS resolution failures for shared services.
Identify that the Spoke VPC is not associated with the Private Hosted Zone in the Shared Services VPC.
A Route 53 Private Hosted Zone must be explicitly associated with a VPC to allow instances in that VPC to resolve the private DNS names.

Anahtar Kavram

Optimizing network performance for sudden traffic spikes requires proactive load balancer scaling (pre-warming), while private DNS resolution across multiple VPCs requires correct Private Hosted Zone association.
Bu soruyu puanla

Konular

Optimizing Network Performance and Latency