Examkin

Question

Difficulty: HardOptimizing Network Performance and Latency

An enterprise financial platform operates its core transaction processing engine in a private subnet within the us-east-1 region. The application exposes HTTPS endpoints via an internet-facing Application Load Balancer (ALB). The platform is experiencing latency issues for clients connecting from London and Singapore, with average round-trip times (RTT) exceeding 450 ms450\text{ ms}. The database layer in us-east-1 must maintain strict immediate consistency, preventing multi-region database replication. Security compliance dictates that client source IP addresses must be preserved at the application layer for audit logging, and connections must benefit from TCP optimization by entering the AWS network as close to the users as possible. Which architecture optimization should the Solutions Architect implement to minimize latency for international clients while adhering to all constraints?

  1. Deploy AWS Global Accelerator and associate the existing ALB in us-east-1 as the endpoint. Configure the accelerator to preserve the client IP address, and route client traffic using the provided Anycast IP addresses.Answer
  2. B
    Deploy regional ALBs in eu-west-2 and ap-southeast-1, routing client traffic via Amazon Route 53 latency-based routing. Connect the regional VPCs using AWS Transit Gateway peering to forward database queries back to the core database in us-east-1.
  3. C
    Create an Amazon CloudFront distribution with the us-east-1 ALB as the origin. Associate Route 53 Private Hosted Zones for the application's domain name with VPCs in the remote regions to optimize DNS resolution.
  4. D
    Deploy a single NAT Gateway in a public subnet in us-east-1 to route all inbound client traffic from the international regions through an AWS Site-to-Site VPN.

Answer

Deploy AWS Global Accelerator and associate the existing ALB in us-east-1 as the endpoint. Configure the accelerator to preserve the client IP address, and route client traffic using the provided Anycast IP addresses.
Deploying AWS Global Accelerator optimizes the network path by terminating the TCP connection at the nearest edge location via Anycast IP routing, and then forwarding the payload over the congestion-free AWS backbone to the ALB in us-east-1. It fully satisfies the compliance constraint of client IP preservation for ALB targets, and does not require cross-region database queries.

Step-by-Step Solution

1
Analyze client connectivity entry points and identify where TCP handshakes occur.
Using public internet direct to the ALB requires TCP handshakes to traverse the global internet, increasing RTT.
Establishing TCP connections closer to the user reduces the connection setup time.
2
Evaluate options for routing over the private AWS backbone vs. the public internet.
AWS Global Accelerator routes traffic over the private global backbone network from the nearest edge location, bypassing public internet congestion.
The private AWS backbone provides lower jitter and latency compared to the public internet.
3
Verify compliance with the audit logging (client IP preservation) and database constraints.
AWS Global Accelerator supports client IP preservation for ALB endpoints, and keeping the application processing in us-east-1 prevents cross-region database queries.
This keeps data processing local to the single-region database to meet consistency requirements without introducing SQL RTT latency.

Key Concept

AWS Global Accelerator optimizes global client performance by onboarding traffic at edge locations and routing it over the AWS global network backbone, while natively supporting client IP preservation for Application Load Balancers.
Rate this question

Topics

Optimizing Network Performance and Latency