Health checks with Route 53 in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of a health check in Route 53?

A health check monitors the health and availability of your resources, like web servers, to ensure traffic is only routed to healthy endpoints.

beginner

Which protocols can Route 53 health checks use to verify endpoint health?

Route 53 health checks can use HTTP, HTTPS, and TCP protocols to check if an endpoint is reachable and responding correctly.

intermediate

How does Route 53 respond when a health check fails?

When a health check fails, Route 53 stops routing traffic to the unhealthy endpoint and can route traffic to healthy alternatives if configured.

intermediate

What is the difference between a health check and a DNS failover in Route 53?

A health check monitors endpoint health, while DNS failover uses health check results to redirect traffic from unhealthy endpoints to healthy ones automatically.

beginner

Can Route 53 health checks monitor endpoints outside AWS?

Yes, Route 53 health checks can monitor any publicly accessible endpoint, including those outside AWS, as long as they respond to the health check protocol.

What happens if a Route 53 health check detects an unhealthy endpoint?

A Route 53 ignores the health check and continues routing traffic.

B Route 53 shuts down the unhealthy endpoint automatically.

C Traffic is routed away from the unhealthy endpoint to healthy ones if configured.

D The endpoint is deleted from DNS records.

Route 53 uses health check results to route traffic away from unhealthy endpoints to healthy alternatives if DNS failover is set up.

Which protocol is NOT supported by Route 53 health checks?

A FTP

B HTTPS

C TCP

D HTTP

Route 53 health checks support HTTP, HTTPS, and TCP protocols, but not FTP.

Can Route 53 health checks monitor endpoints outside of AWS?

A Only endpoints with AWS IAM roles can be monitored.

B No, only AWS resources can be monitored.

C Only endpoints in the same region can be monitored.

D Yes, any publicly accessible endpoint can be monitored.

Route 53 health checks can monitor any publicly accessible endpoint, including those outside AWS.

What is required to enable DNS failover using Route 53 health checks?

A Associate a health check with a DNS record and configure failover routing policy.

B Enable CloudWatch alarms on the endpoint.

C Create an IAM role for Route 53.

D Use a private hosted zone.

DNS failover requires associating a health check with a DNS record and setting the routing policy to failover.

How often does Route 53 perform health checks by default?

A Every 5 minutes

B Every 30 seconds

C Every 1 minute

D Every 10 seconds

By default, Route 53 performs health checks every 30 seconds to monitor endpoint health.

Explain how Route 53 health checks help improve application availability.

Think about how traffic is managed when a server is down.

Describe the steps to set up a health check and DNS failover in Route 53.

Consider the order of creating and linking components.