AZ400-Q: generate useful release notes
Release notes are manually written after each deployment and frequently omit fixed bugs. What should the delivery process do?
- A) Stop publishing release notes.
- B) Generate a draft from merged work items, pull requests, tags, and artifact/deployment metadata; review it for audience and accuracy before publishing. ✓
- C) Copy the entire commit history without review.
- D) Use a storage-account tag as the release note.
Answer: B. Automation improves completeness while review keeps the notes useful and safe for the intended audience.
Why not the others: Omitting or dumping raw history fails communication; a tag is insufficient context.
Related
release-notes-templates · docs-as-code · devops-traceability