Question 280
During an operational security assessment at a public-sector technology agency, the team documents this issue: An API adds backward-compatible functionality but the release process incorrectly replaces stable major versions. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Select TWO: one corrective action and one test that confirms its effectiveness. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Apply semantic versioning rules and automated release notes so breaking APIs, additive features and fixes are signaled by appropriate version increments. The action targets the recorded failure (An API adds backward-compatible functionality but the release process incorrectly replaces stable major versions), and is intended to reduce the corresponding risk: Consumers may silently adopt incompatible changes if package versions do not reflect API compatibility.
Correct verification. A breaking contract change produces an appropriate major-version promotion and consumers remain pinned until tested. The measurement or controlled test provides evidence for the issue (An API adds backward-compatible functionality but the release process incorrectly replaces stable major versions) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
A clean pipeline restores the exact approved package through the authorized feed without accessing unapproved sources. The paired controls concern semantic versioning and breaking changes, not that measure.
Use Azure Artifacts views to promote reviewed package versions through controlled prerelease and release stages, rather than overwriting packages. The semantic versioning and breaking changes implementation and safeguard are still missing.
Commit ecosystem lockfiles, authenticate feeds and enforce locked dependency restore in automated builds to control transitive package changes. It is not the complementary risk control for semantic versioning and breaking changes.