AZ400-Q: preserve delivery traceability
During an incident, a team cannot determine which work item authorized the production change or which build artifact was deployed. What design best prevents this recurring problem?
- A) Link work items, branches, commits, pull requests, pipeline runs, immutable artifact versions, deployments, and release notes through the delivery workflow. ✓
- B) Ask the release manager to keep a private spreadsheet of deployments.
- C) Require developers to remember the build number in a chat message.
- D) Grant every engineer permission to edit the production environment.
Answer: A. Connected delivery evidence lets a team trace a change from intent to production and back during audit or incident response.
Why not the others: A private spreadsheet and chat memory drift from the source of truth. Broad production access does not create traceability.