Implementing Health Check System for On-Premises Server
Question
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?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.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-53The best solution to implement a health check system to check the health of the on-premises server continuously and switch-over to a static website hosted in AWS, is by using Route 53 health checks to failover to the secondary site if the on-premises web server has issues.
Option A: Using an Elastic Load balancer to divert traffic when the on-premises web server has issues is not a suitable solution because the load balancer does not have a way to identify if the on-premises web server is healthy or not.
Option C and D: Using Elastic Beanstalk or AWS Opsworks to check for issues in the on-premises web server and then failover to an environment defines in Elastic Beanstalk or AWS Opsworks is also not a suitable solution because they are more suitable for managing and deploying applications on AWS rather than for monitoring on-premises servers.
Therefore, the best option to implement a health check system to check the health of the on-premises server continuously and switch-over to a static website hosted in AWS is to use Route 53 health checks to failover to the secondary site if the on-premises web server has issues. Route 53 health checks can be configured to monitor the health of the on-premises web server by performing periodic checks on the endpoint that hosts the website. When the health check fails, Route 53 can automatically switch over to a secondary site hosted in AWS.
