Question 140
During an operational security assessment at a public-sector technology agency, the team documents this issue: A release branch accepts new features while compliance believes it is under stabilization. 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. Define a documented release-branch strategy with controlled hotfix propagation back to main and automated divergence checks. The action targets the recorded failure (A release branch accepts new features while compliance believes it is under stabilization), and is intended to reduce the corresponding risk: Fixes applied only to release branches reappear as defects in subsequent releases and complicate auditing.
Correct verification. A production hotfix is tagged, reviewed, merged into the release branch and reconciled back to main without losing the original fix. The measurement or controlled test provides evidence for the issue (A release branch accepts new features while compliance believes it is under stabilization) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
A targeted PR cannot complete until reviewer and build policies pass and an associated work item is linked. The release branch and hotfix merging implementation and safeguard are still missing.
Use trunk-based development with small, short-lived feature branches and automated validation, employing feature flags for unfinished behavior. It is not the complementary risk control for release branch and hotfix merging.
Require pull-request review, current required status checks and ruleset protections for the protected default branch, limiting bypass authority. The two-part release branch and hotfix merging control remains unsatisfied.