Which combination of steps should a SysOps administrator take to configure Route 53 to meet these requirements?
(Choose two.)
Create Amazon CloudWatch alarms that monitor the health of the ALB in each Region. Configure Route 53 DNS failover by using a health check that monitors the alarms.
Create Amazon CloudWatch alarms that monitor the health of the EC2 instances in each Region. Configure Route 53 DNS failover by using a health check that monitors the alarms.
Configure Route 53 DNS failover by using a health check that monitors the private IP address of an EC2 instance in each Region.
Configure Route 53 geoproximity routing. Specify the Regions that are used for the infrastructure.
Configure Route 53 simple routing. Specify the continent, country, and state or province that are used for the infrastructure.
Explanations:
CloudWatch alarms monitoring the health of the ALB can be used to trigger DNS failover. These alarms can be linked to Route 53 health checks, ensuring traffic is rerouted when the ALB is unhealthy in a Region.
Monitoring the health of EC2 instances directly would not be ideal for DNS failover, as the issue might be at the load balancer level, not at the instance level. Route 53 should check load balancer health instead.
Monitoring the private IP of an EC2 instance does not provide the necessary health check for a production environment. Load balancer health checks are a more appropriate method to ensure failover works.
Geoproximity routing in Route 53 directs users to the closest Region. This meets the requirement for directing traffic to the closest Region while ensuring failover if a Region becomes unavailable.
Simple routing does not offer the capability for geolocation-based redirection or automated failover. It can only route based on fixed rules without considering proximity or health conditions.