Health checks with Route 53 in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Route 53 respond when a health check fails?

If you configure a Route 53 health check for a web server and the health check fails continuously, what will Route 53 do with DNS queries for that server's domain?

A Route 53 stops routing traffic to the unhealthy endpoint and routes to healthy alternatives if configured.

B Route 53 continues to respond with the IP address but adds a warning in the DNS response.

C Route 53 stops responding to DNS queries for the domain.

D Route 53 automatically deletes the DNS record associated with the unhealthy endpoint.

💡 Hint

Think about how DNS routing adapts to endpoint health.

Route 53 health checks monitor endpoints and when an endpoint is unhealthy, Route 53 stops routing traffic to it if failover or routing policies are configured. It does not delete records or stop DNS responses entirely.

❓ Configuration

intermediate

Which configuration enables Route 53 health checks to monitor an HTTP endpoint?

You want Route 53 to check if your web server is responding correctly on port 80 using HTTP. Which health check configuration is correct?

A Specify IP address, port 80, protocol TCP.

B Specify IP address, port 443, protocol HTTPS.

C Specify domain name, port 80, protocol HTTP, and a path like '/health'.

D Specify domain name, port 22, protocol SSH.

💡 Hint

HTTP health checks require protocol and path details.

To monitor a web server with Route 53 health checks, you specify the domain or IP, port 80, protocol HTTP, and optionally a path that returns a success status.

❓ Architecture

advanced

Designing a fault-tolerant DNS setup with Route 53 health checks

You have two web servers in different regions behind Route 53. You want DNS to route traffic only to healthy servers automatically. Which setup achieves this?

A Create two A records with failover routing and health checks on each server.

B Create two A records with latency routing and health checks on each server.

C Create one A record pointing to both servers without health checks.

D Create two A records with weighted routing and no health checks.

💡 Hint

Latency routing combined with health checks improves fault tolerance across regions.

Latency routing directs users to the lowest latency region. Adding health checks ensures traffic is only routed to healthy endpoints, providing fault tolerance.

❓ security

advanced

Security considerations for Route 53 health checks

Which security practice is important when configuring Route 53 health checks for your private web servers?

A Restrict health check requests to Route 53 health check IP ranges using firewall rules.

B Disable authentication on the health check endpoint to avoid failures.

C Allow all IP addresses to access the health check endpoint.

D Use HTTP instead of HTTPS to simplify health check configuration.

💡 Hint

Think about limiting who can reach your health check endpoint.

Restricting access to only Route 53 health check IPs prevents unauthorized access and protects your private servers.

✅ Best Practice

expert

Optimizing Route 53 health check intervals and failure thresholds

You want Route 53 to detect unhealthy endpoints quickly but avoid false positives from brief outages. Which combination of health check settings balances this best?

A Set interval to 60 seconds and failure threshold to 1.

B Set interval to 10 seconds and failure threshold to 1.

C Set interval to 5 seconds and failure threshold to 5.

D Set interval to 30 seconds and failure threshold to 3.

💡 Hint

Consider how often checks run and how many failures trigger unhealthy status.

A 30-second interval with 3 failures balances quick detection and reduces false alarms from transient issues.