Configuring Health Checks with Amazon Route 53

Correct Answer: D.

The client is looking for several healthy resources from all the web servers.

For this, health checks can be created to monitor other health checks which can notify when the resource count falls below a threshold value.

During configuration, health checks are configured for individual resources without creating any notification.

Health checks monitoring status of these health checks are configured which will notify count of healthy resource count.

Option A is incorrect as these health checks will provide insights into the application & will not be useful for the above case.

Option B is incorrect as this health check will monitor the data streams which CloudWatch alarms also monitor.

These health checks will not be useful in the above case.

Option C is incorrect as these health checks will monitor individual endpoints.

In the above case, the client is looking for consolidated health checks & a count of healthy resources among all the web servers.

Health Check monitoring other health checks is a better option for this requirement.

For more information on health checks with Amazon Route 53, refer to the following URL,

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/health-checks-types.html

The correct answer for the question is C. Health Checks monitoring endpoint.

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service that provides a reliable and cost-effective way to route Internet traffic to AWS resources. It can be used to route traffic to various types of AWS resources, such as EC2 instances, Elastic Load Balancers, S3 buckets, and more.

In this scenario, the IT firm has deployed multiple web servers in the AWS cloud for its client, and all these web servers perform the same functionality. Amazon Route 53 is being used to route Internet traffic to these servers. To ensure that these web servers are healthy and can handle the incoming traffic, health checks need to be configured.

Health checks in Amazon Route 53 allow you to monitor the health and performance of your resources, such as web servers, and automatically route traffic to healthy resources. To configure health checks for the web servers in this scenario, an endpoint health check can be created.

An endpoint health check monitors the health of an endpoint by periodically sending a request to a specified endpoint, such as a web server, and checking the response. The response can be checked for specific strings or patterns to determine if the endpoint is healthy. If the endpoint fails the health check, Route 53 can route traffic to other healthy resources.

To monitor the health of all the web servers deployed by the IT firm, an endpoint health check can be created for each web server. Each health check will periodically send a request to the endpoint, i.e., the web server, and check the response. If the response indicates that the web server is healthy, the health check status will be marked as "passing." If the response indicates that the web server is unhealthy, the health check status will be marked as "failing."

Once the health checks are created, the client can be notified when the number of healthy web servers count is below three. This can be achieved by creating a CloudWatch alarm that monitors the health check status of all the web servers. If the number of passing health checks falls below three, the CloudWatch alarm can trigger a notification to the client.

Option A, Route 53 Application Recovery Controller health checks, is incorrect because it is a different type of health check that is used to monitor the health of applications that run on AWS resources. Option B, Health Check monitoring CloudWatch Alarms, is incorrect because it is not a type of health check, but rather a way to monitor the health check status of resources using CloudWatch alarms. Option D, Health Checks monitoring other health checks, is incorrect because it is not a valid option for configuring health checks in Amazon Route 53.