A Route 53 health check should report unhealthy only when a specific CloudWatch alarm is in the ALARM state. Which health check type should be created?
Show answer and explanation
Answer: A
Route 53 offers a health check type whose status is driven by a CloudWatch alarm rather than by its own network probe. This is useful when the failure signal is computed from metrics, such as an error rate or a queue depth, that a simple TCP or HTTP check cannot observe. The alarm has to belong to the same AWS account as the health check.
Why the other options are wrong
- B. A TCP check only tests whether a port accepts a connection. It cannot see an arbitrary CloudWatch metric.
- C. A calculated health check combines the results of other Route 53 health checks; it cannot read an alarm directly.
- D. DNSSEC signs DNS responses to prevent spoofing. It is not a health check type.
Exam tip. Metric-driven health is a CloudWatch alarm health check.