AZ400-Q: avoid unvalidated merges
A team wants fast unit tests for every pull request into
main, a full integration suite only after changes merge tomain, and no builds for documentation-only changes. What should the pipeline design use?
- A) Separate PR and branch triggers with path filters/conditions, running the appropriate test stage for each event. ✓
- B) A nightly trigger only.
- C) A production environment approval before unit tests.
- D) A single manual run at the end of each sprint.
Answer: A. Trigger rules and path filters align validation cost and timing with the change and integration risk.
Why not the others: Nightly/manual validation gives late feedback. An environment approval governs deployment, not pull-request test selection.