AZ400-Q: define pipeline health
A platform team says a pipeline is “healthy” because it has not failed today. What broader evidence should it track?
- A) Failure rate, duration, queue time, flaky-test rate, retry behavior, cost/concurrency, and whether deployments meet their operational outcomes. ✓
- B) Only number of YAML lines.
- C) Only agent hostnames.
- D) Only number of developers.
Answer: A. Pipeline health is operational: reliability, performance, cost, and delivery outcomes all matter.
Why not the others: The remaining metrics are narrow activity/inventory measures, not health.