Examkin

Question

Difficulty: HardOptimizing Network Performance and Latency

A gaming company hosts its multiplayer matchmaking engine on Amazon EC2 instances in a shared services VPC in the us−east−1us-east-1 Region. Multiple client-facing game VPCs in separate AWS accounts in the same Region need to establish low-latency, high-throughput connections to the matchmaking engine, which is accessible via an internal Network Load Balancer (NLB) with a private DNS name registered in an Amazon Route 53 Private Hosted Zone (PHZ). The company currently connects the game VPCs to the shared services VPC using AWS Transit Gateway. During peak gaming hours, players experience high latency and packet delivery delays, and game servers in the client VPCs intermittently fail to resolve the matchmaking engine's DNS name. The solutions architect must optimize the network to achieve the lowest possible latency and maximum throughput for game traffic, while ensuring reliable DNS resolution and minimizing data transfer costs. Which network optimization strategy should the solutions architect implement?

  1. Establish direct VPC Peering connections between each client-facing game VPC and the shared services VPC, and authorize and accept the Route 53 Private Hosted Zone association for the game VPCs across the accounts.Answer
  2. B
    Replace Transit Gateway with direct VPC Peering connections between the client VPCs and the shared services VPC, and configure a public Route 53 Hosted Zone for the matchmaking engine to allow client VPCs to resolve the name over the public internet.
  3. C
    Configure AWS Direct Connect Gateway to establish transitive routing directly between the game VPCs and the shared services VPC, and configure Route 53 Resolver outbound endpoints to forward queries.
  4. D
    Replace the internal NLB with an Application Load Balancer (ALB), request AWS Support to pre-warm the ALB to handle peak traffic bursts, and associate the Private Hosted Zone with the Transit Gateway route table.

Answer

Establish direct VPC Peering connections between each client-facing game VPC and the shared services VPC, and authorize and accept the Route 53 Private Hosted Zone association for the game VPCs across the accounts.
Establishing VPC Peering connections between the client-facing game VPCs and the shared services VPC eliminates the processing overhead and latency hop introduced by AWS Transit Gateway, providing sub-millisecond latency. Furthermore, authorizing and accepting the Route 53 Private Hosted Zone association allows game servers in the client VPCs to natively and securely resolve the private DNS name of the internal matchmaking load balancer.

Step-by-Step Solution

1
Analyze latency requirements and network path options between VPCs in the same Region.
Determine that AWS Transit Gateway introduces an additional hop adding 1 ms1\text{ ms} to 2 ms2\text{ ms} of latency and data processing costs, whereas VPC Peering provides direct, sub-millisecond routing with no data processing fees.
VPC Peering is the most optimal choice for high-throughput, latency-sensitive intra-region VPC-to-VPC traffic.
2
Resolve private DNS resolution issues across different AWS accounts in the same Region.
Identify that the Route 53 Private Hosted Zone must be associated with the client VPCs by authorizing the association from the shared services account and accepting it in each client account.
This allows the client VPCs to natively resolve the private DNS record of the matchmaking load balancer without exposing it to the public internet.
3
Compare alternative solutions against the constraints of cost, performance, and complexity.
Eliminate Direct Connect Gateway (which does not support transitive routing), NAT Gateways (which add latency and costs), and public DNS zones (which compromise security).
Ensures all non-functional requirements are met while selecting the correct architecture.

Key Concept

VPC Peering vs Transit Gateway latency and cross-account Route 53 Private Hosted Zone association
Estimated Time:3m 0s
Rate this question

Topics

Optimizing Network Performance and Latency