A SysOps administrator needs to deploy an application in multiple AWS Regions. The SysOps administrator must implement a solution that routes users to the Region with the lowest latency. In case of…

Question

Options

• ACreate Amazon Route 53 A records that have the same name for each endpoint. Use a latency
• BCreate Amazon Route 53 A records that have the same name for each endpoint. Use a failover
• CCreate an AWS Global Accelerator standard accelerator. Create an endpoint group for each
• DCreate Amazon Route 53 A records that have the same name for each endpoint. Use a

• A
  8% (2)
• B
  4% (1)
• C
  73% (19)
• D
  15% (4)

Explanation

AWS Global Accelerator is correct because it uses static anycast IP addresses and routes traffic over the AWS global backbone network - not the public internet - to the nearest, healthiest endpoint. Unlike DNS-based solutions, failover with Global Accelerator happens at the network layer within seconds, because health checks run at AWS edge locations and traffic is rerouted immediately without waiting for DNS TTL expiration.

Options A, B, and D are all Route 53 solutions, and their fatal flaw is DNS TTL. Even with aggressively low TTL values, DNS propagation and client-side caching introduce failover delays measured in minutes, not seconds - violating the "shortest time to failover" requirement. Option A (latency routing) addresses the latency requirement but fails on failover speed; Option B (failover routing) addresses failover but not latency-optimized routing; Option D (likely weighted or geolocation) addresses neither optimally.

Memory tip: When an AWS exam question emphasizes speed of failover, Global Accelerator almost always wins over Route 53 - remember the phrase "Accelerator = Accelerated failover". Route 53 is DNS (slow to propagate); Global Accelerator is network-layer (instant reroute).

No community discussion yet for this question.