AZ400-Q: optimize pipeline concurrency
A monorepo pipeline launches all integration tests on every documentation-only change. Builds queue for an hour and hosted-agent cost rises. The test team still needs full validation for application changes. What is the best first improvement?
- A) Add path-based triggers/conditions so documentation-only changes run the relevant fast checks, while application changes run the full test matrix. ✓
- B) Disable integration tests permanently.
- C) Give every developer a self-hosted agent.
- D) Increase the timeout for all jobs.
Answer: A. Trigger and path design can reduce unnecessary work while preserving the full validation route when code changes. Measure queue time, duration, failure rate, and cost after the change.
Why not the others: Removing tests loses confidence. More agents may increase cost without addressing waste. A timeout does not reduce queueing or execution.