DOP-C02 Practice Question 67: Route 53 Alarm Based Health Check
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 7 · question 7 of 10
An application's primary Region publishes a custom CloudWatch metric that reflects a downstream dependency's error rate, a signal that a plain HTTP endpoint health check cannot capture. A DevOps engineer needs Route 53 failover routing to treat the primary Region as unhealthy whenever that custom metric crosses a defined threshold, and to fail over to a secondary Region within the usual health check evaluation window. Which health check design meets this requirement?
Show answer and explanation
Answer:
Route 53 supports health checks that monitor the state of a CloudWatch alarm (or, more precisely, the alarm's underlying data stream) instead of polling an endpoint. Pointing the alarm at the custom error rate metric lets Route 53 mark the primary record unhealthy and fail over to the secondary record automatically whenever the metric breaches the threshold, all within Route 53's normal health check evaluation. Option A only checks basic HTTP reachability of the root URL; it cannot see the internal error rate metric of a downstream dependency. Option C is a calculated health check, which aggregates other health checks rather than evaluating a CloudWatch metric directly, and using an unrelated load balancer endpoint check as its only child does not solve the stated problem. Option D requires manual intervention and defeats the goal of automated failover tied to the metric.