AZ400-Q: retain useful test evidence
A pipeline runs unit and integration tests. A release manager needs to see failures and coverage trends without opening raw console logs. What should the pipeline do?
- A) Print a final
tests passedmessage only. - B) Upload the source code as a text artifact.
- C) Publish structured test results and coverage reports, then use them in the quality/release decision. ✓
- D) Delete failed runs immediately to reduce noise.
Answer: C. Structured results and coverage reports support diagnosis, trend analysis, and gates in a way raw logs alone do not.
Why not the others: A message is not evidence. Source upload is not test reporting. Deleting failures removes diagnostic history.
Related
pipeline-integration-tests · test-coverage · pipeline-evaluation-and-quality-gates