AZ400-Q: keep an architecture diagram current
A team’s architecture diagram becomes stale after every release because it is stored in a separate presentation. What practice best makes changes reviewable with the implementation?
- A) Ask one architect to update the presentation quarterly.
- B) Store the diagram only in a chat message.
- C) Forbid diagram changes during feature work.
- D) Maintain Markdown/Mermaid documentation in the repository and require it through pull-request review when the architecture changes. ✓
Answer: D. Docs as code puts documentation in the same change/review flow as the system it describes.
Why not the others: Separate/manual documentation drifts; chat is not an auditable maintained source.