Question 260
During an operational security assessment at a public-sector technology agency, the team documents this issue: A hotfix package is published without linking its promotion to test evidence. 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. Use Azure Artifacts views to promote reviewed package versions through controlled prerelease and release stages, rather than overwriting packages. The action targets the recorded failure (A hotfix package is published without linking its promotion to test evidence), and is intended to reduce the corresponding risk: An unverified or changed artifact may be consumed as production-approved despite having no promotion evidence.
Correct verification. The promoted package version matches the tested immutable package and is visible through the approved release view. The measurement or controlled test provides evidence for the issue (A hotfix package is published without linking its promotion to test evidence) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
A breaking contract change produces an appropriate major-version promotion and consumers remain pinned until tested. The paired controls concern azure artifacts release views and promotion, not that measure.
Use a documented calendar versioning scheme paired with commit SHA or build run provenance when release timing matters more than API compatibility. It is not the complementary risk control for azure artifacts release views and promotion.
Publish versioned packages to GitHub Packages with repository-scoped workflow permissions and verified consuming-repository access. This does not supply the required azure artifacts release views and promotion action-and-control pair.