A mobile game company serves game assets from EC2 instances behind an ALB in two Regions. Clients must fetch assets from the geographically closest Region; if assets are unavailable in the nearest Region, clients should fail over to the other Region. How should a solutions architect implement this behavior?

The correct solution uses Route 53 latency-based routing combined with health checks. Latency routing directs users to the AWS Region that provides the lowest latency, which typically means the geographically closest Region. Enabling "Evaluate Target Health" on the alias record ensures that if the primary (lowest latency) ALB becomes unhealthy, Route 53 will automatically fail over to the healthy ALB in the other Region. Using CloudFront with an origin group (option 1) is not ideal because CloudFront's primary purpose is caching and content delivery network (CDN) functionality, not primarily for active-active multi-Region failover based on health checks for origin servers. While it can direct traffic, Route 53 offers more direct control over DNS-based failover. A Route 53 failover routing record (option 2 and 3) is designed for active-passive scenarios, where traffic is directed to a primary resource and only fails over to a secondary if the primary is unhealthy. The requirement is for clients to fetch from the geographically closest Region first, which is best handled by latency-based routing, not simple failover. Creating two CloudFront distributions (option 3) adds unnecessary complexity and cost if the primary goal is just multi-Region failover and latency-based routing.