AZ400-Q: diagnose slow pipeline delivery
Pipeline duration has not changed, but developers wait much longer before jobs begin. What metric and action should the team consider first?
- A) Storage account capacity; delete build logs.
- B) Git commit message length; require shorter messages.
- C) Queue time/agent utilization; adjust runner capacity, job scheduling, or unnecessary trigger load based on evidence. ✓
- D) VM disk encryption; disable it.
Answer: C. A gap before execution indicates queue/capacity/scheduling pressure, not necessarily slow tasks. Measure the right part of the pipeline before changing it.
Why not the others: The other choices do not address job queueing or runner availability.