Your company runs an application for the US market in the us-east-1 AWS region. This application uses proprietary TCP and UDP protocols on Amazon Elastic Compute Cloud (EC2) instances. End users run…

Question

Options

• ARegister the IP addresses of the service hosts as "A" records with latency-based routing policy in
• BSet the Elastic Load Balancing (ELB) load balancer in front of the hosts of the service, and
• CSet Amazon CloudFront in front of the host of the service, and register the CloudFront name of
• DSet the Amazon API gateway in front of the service, and register the API gateway name of the

• A
  75% (30)
• B
  15% (6)
• C
  3% (1)
• D
  8% (3)

Explanation

Option A is correct because Route 53 latency-based routing with "A" records works at the DNS level and is protocol-agnostic - it routes end users to whichever AWS region has the lowest latency for them, regardless of whether the application uses HTTP, proprietary TCP, or UDP. As you expand globally, you deploy EC2 instances in new regions and register their IPs; Route 53 handles the rest automatically.

Option B (ELB) is wrong because Elastic Load Balancing is a regional service - it balances traffic within a region but provides no mechanism for routing global users to the geographically closest region.

Option C (CloudFront) is wrong because CloudFront is an HTTP/HTTPS CDN; it does not support arbitrary proprietary TCP or UDP protocols, making it fundamentally incompatible with this application.

Option D (API Gateway) is wrong for the same protocol reason - API Gateway only supports HTTP/REST and WebSocket traffic, not custom TCP/UDP protocols.

Memory tip: Whenever an exam question mentions non-HTTP protocols (TCP, UDP, proprietary) combined with global low latency, think Route 53 latency-based routing - it's the only AWS global routing mechanism that is truly protocol-agnostic because it operates purely at the DNS layer.

No community discussion yet for this question.