AWS Certified Solutions Architect Professional SAP-C02 Practice Question
An online travel agency operates identical application stacks behind Application Load Balancers (ALBs) in us-east-1, eu-west-1, and ap-southeast-1. DNS requirements are as follows: users must be routed to an endpoint located in their own country; if that country-level endpoint is unhealthy, traffic must automatically fail over to a healthy endpoint in the same continent; if the continent-level endpoint is also unhealthy, traffic must fail over to a global fallback endpoint. All failover logic must be handled entirely in Amazon Route 53 with minimal operational effort. Which Route 53 configuration satisfies these requirements?
Deploy a Route 53 Traffic Flow policy that uses geoproximity routing with bias; disable health checks so that when an endpoint fails Route 53 returns all remaining endpoints and relies on the client to retry a healthy one.
Create latency-based alias records for each Region, attach health checks to the ALBs, and add an extra weighted record with weight 0 that points to the global fallback. Latency-based routing will direct users to the closest healthy Region and use the weight-0 record if all other Regions fail.
Configure a separate failover routing policy for each Region with the regional endpoint as primary and the global endpoint as secondary; use custom Route 53 Resolver rules so the resolver's IP address determines the user's country.
Create a set of geolocation alias records that share the same name and type: one record for each served country, additional records for each continent, and a Default record. Enable Evaluate Target Health (or attach health checks) for every record so that Route 53 automatically falls back up the geographic hierarchy when an endpoint is unhealthy.