Question 110
During an operational security assessment at a public-sector technology agency, the team documents this issue: The team cannot explain why the release note lists changes from a different build. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which TWO responses form a sound implementation-and-verification pair for this issue? (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Generate release notes from tagged commits and linked pull requests, with curated customer-impact and migration sections before publication. The action targets the recorded failure (The team cannot explain why the release note lists changes from a different build), and is intended to reduce the corresponding risk: Manual release summaries omit changes and cannot prove which reviewed revision reached users.
Correct verification. A release notes draft reconciles to the deployed tag's commit range and includes a verified breaking-change announcement. The measurement or controlled test provides evidence for the issue (The team cannot explain why the release note lists changes from a different build) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
A signed matching event reaches the intended Teams channel once; irrelevant or spoofed requests do not trigger the workflow. It is not the complementary risk control for automated release notes from git history.
Store Mermaid diagrams with the repository and review them alongside affected workflow changes so diagrams remain reproducible. This does not supply the required automated release notes from git history action-and-control pair.
Maintain Markdown engineering runbooks and architecture documentation in reviewed source control with visible links from service ownership records. The paired controls concern automated release notes from git history, not that measure.