Your company has an on-premises web server. The company wants to implement a health check system to check the health of the on-premises server continuously. If the health degrades for any reason, then a switch-over must be done to a static website hosted in AWS. Which of the following can be implemented to fulfill this requirement?

Answer options:

A.Use an Elastic Load balancer to divert traffic when the on-premises web server has issues.
B.Use Route 53 health checks to failover to the secondary site if the on-premises web server has issues.
C.Use Elastic Beanstalk to check for issues in the on-premises web server and then failover to an environment defines in Elastic Beanstalk.
D.Use AWS Opsworks to check for issues in the on-premises web server and then failover to an environment defines in AWS Opsworks.

Correct Answer: B
The AWS Documentation mentions the following.
Use an active-passive failover configuration when you want a primary resource or group of resources to be available most of the time. You want a secondary resource or group of resources to be on standby if all the primary resources become unavailable. When responding to queries, Route 53 includes only the healthy primary resources. Route 53 begins to include only the healthy secondary resources in response to DNS queries if all the primary resources are unhealthy.
Option A is incorrect because this service cannot be used to divert traffic in such a way.
Options C and D are incorrect since these services don’t have these sorts of features.
For more information on DNS failover types, please refer to the below URLs-
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-types.html
https://aws.amazon.com/blogs/aws/new-amazon-route-53-resolver-for-hybrid-cloud
https://aws.amazon.com/blogs/security/how-to-set-up-dns-resolution-between-on-premises-networks-and-aws-using-aws-directory-service-and-amazon-route-53