AWS Route 53 Health Checks | Types for Monitoring

Supported Types for Health Checks by AWS Route 53

Prev Question

Question

Which of the following types can be monitored for health checks by AWS Route 53? Choose 2 correct options.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Answer: A, B.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/health-checks-types.html
Types of Amazon Route 53 Health Checks You can create three types of Amazon Route 53 health checks: Health checks that monitor an endpoint You can configure a health check that monitors an endpoint that you specify either by IP address or by domain name. At regular intervals that you specify, Route 53 submits automated requests over the internet to your application, server, or other resource to verify that it's reachable, available, and functional. Optionally, you can configure the health check to make requests similar to those that your users make, such as requesting a web page from a specific URL. Health checks that monitor other health checks (calculated health checks) You can create a health check that monitors whether Route 53 considers other health checks healthy or unhealthy. One resources that perform the same function, such as multiple web servers, and your chief concern is whether some uation where this might be useful is when you have multiple imum number of your resources are healthy. You can create a health check for each resource without configuring notification for those health checks. Then you can create a health check that monitors the status of the other health checks and that notifies you only when the number of available web resources drops below a specified threshold. Health checks that monitor CloudWatch alarms. You can create CloudWatch alarms that monitor the status of CloudWatch metrics, such as the number of throttled read events for an Amazon DynamoDB database or the number of Elastic Load Balancing hosts that are considered healthy. After you create an alarm, you can create a health check that monitors the same data stream that CloudWatch monitors for the alarm. To improve resiliency and availability, Route 53 doesn't wait for the CloudWatch alarm to go into the ALARM state. The status of a health check changes from healthy to unhealthy based on the data stream and on the criteria in the CloudWatch alarm.

AWS Route 53 is a DNS web service provided by Amazon Web Services. It is used for registering domain names, routing internet traffic to the appropriate resources, and also for monitoring the health of these resources.

Route 53 can perform health checks to determine the availability and status of resources that it is responsible for. These health checks can be used to automate failover and recovery of resources in the event of an outage.

Now, let's discuss the given options:

A. Endpoints: Route 53 can monitor endpoints such as IP addresses, domain names, and URLs, and check their availability and response time. These endpoints can be located anywhere on the internet or within a VPC.

C. EC2 instance health checks: Route 53 can also monitor the health of EC2 instances by performing checks on their status using the Amazon EC2 API. This allows Route 53 to route traffic only to healthy instances, ensuring high availability and reliability of applications running on EC2.

D. DNS service health checks: Route 53 can perform health checks on DNS services, such as checking the availability and response time of DNS servers. This helps to ensure that DNS resolution is fast and reliable.

B. State of CloudWatch alarm: Route 53 does not monitor the state of CloudWatch alarms. CloudWatch is a monitoring service that provides data and insights into AWS resources, but it is not directly related to Route 53's health checking capabilities.

Therefore, the correct answers are A. Endpoints and C. EC2 instance health checks.

Prev Question