Question 290
During an operational security assessment at a public-sector technology agency, the team documents this issue: Multiple branches publish the same date string and overwrite their deployable artifacts. 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 a documented calendar versioning scheme paired with commit SHA or build run provenance when release timing matters more than API compatibility. The action targets the recorded failure (Multiple branches publish the same date string and overwrite their deployable artifacts), and is intended to reduce the corresponding risk: Date-only labels can collide or conceal source differences when multiple builds occur on the same day.
Correct verification. Two same-day builds have unambiguous, traceable versions and each maps to the source revision and pipeline that produced it. The measurement or controlled test provides evidence for the issue (Multiple branches publish the same date string and overwrite their deployable artifacts) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Configure a governed Azure Artifacts feed with intentional upstream sources and feed permissions for producers and consumers. It is not the complementary risk control for calver and artifact provenance.
Publish temporary build outputs as pipeline artifacts and reusable versioned libraries to an appropriate package feed with separate retention policies. This does not supply the required calver and artifact provenance action-and-control pair.
Two isolated builds of the tagged revision resolve identical dependency versions and produce traceable artifact provenance. The two-part calver and artifact provenance control remains unsatisfied.