A company deploys a web app into two AWS Regions. Each Region has one VPC with three EC2 web servers behind an Application Load Balancer (ALB). The company already has a Route 53 hosted zone for example.com. Users will use app.example.com. The DNS solution must route global users to the Region with the lowest response time and fail over to the next-lowest-region if the primary Region is unavailable. Which Route 53 configuration meets these requirements?

The correct solution uses latency-based routing to direct users to the Region with the lowest response time. Creating an A record for each ALB as an alias record allows Route 53 to automatically resolve to the ALB's DNS name. Setting "Evaluate Target Health" to Yes ensures that Route 53 checks the health of the underlying ALB and its registered targets (the EC2 instances). If an ALB or its targets in the primary Region become unhealthy, Route 53 will automatically fail over to the next healthiest Region based on latency. Incorrect options: Geolocation routing is based on the user's geographic location, not latency. Directly routing to IP addresses for ALBs is not recommended as ALB IP addresses can change. Manually configuring HTTP or TCP health checks for ALBs is less efficient than using alias records with "Evaluate Target Health," which leverages the ALB's built-in health checks.