A gaming company will deploy its game across multiple AWS Regions. Each Region has an Auto Scaling group of EC2 instances behind an Application Load Balancer. The company wants Route 53 to send players to the nearest Region and to automatically fail over traffic if a Region becomes unhealthy. Which combination of steps should the administrator take? (Choose two.)

The company needs to send players to the nearest Region and automatically fail over if a Region is unhealthy. Geoproximity routing (option 4) is ideal for directing users to the closest AWS Region based on their geographic location. To achieve automatic failover, Route 53 health checks are necessary. While Route 53 can directly monitor endpoints, integrating with CloudWatch alarms (option 1) that track the Application Load Balancer's (ALB) health provides a robust and comprehensive health check for the entire regional application stack. If the ALB, and thus the application in that Region, becomes unhealthy, the CloudWatch alarm triggers the Route 53 health check to mark the Region as unhealthy, initiating failover. Monitoring EC2 instance health directly (option 2) is less effective because individual instance failures might not mean the entire application in the Region is down, especially with Auto Scaling. Probing private IP addresses (option 3) is not feasible for public-facing Route 53 health checks. Simple routing (option 5) does not support failover or proximity-based routing.