Question 790
At fictional Quartzfield Logistics, a software-security team is conducting a security incident follow-up assessment without placing confidential information in build artifacts. The case observation is: A security hotfix is deployed but breaks a business-critical API and cannot be rolled back because database changes are incompatible. The team must select a defensible control or assessment. Which repeatable engineering safeguard would most directly reduce recurrence?
Explanation
Writer-proposed answer: B (UNVERIFIED)
Preliminary individual option explanations — NOT expert validated
Correct Answer
Secure software release engineering balances risk remediation with reliability and reversible change. A canary failure triggers contained recovery without reintroducing known critical exposure or corrupting data.
Incorrect Answers
This response concerns incident root cause to control improvement. Here, a security hotfix is deployed but breaks a business-critical API and cannot be rolled back because database changes are incompatible. The confirming evidence is: A canary failure triggers contained recovery without reintroducing known critical exposure or corrupting data.
Focusing on coordinated vulnerability disclosure would leave this problem unresolved: A security hotfix is deployed but breaks a business-critical API and cannot be rolled back because database changes are incompatible.
Vulnerable package patch prioritization concerns another aspect of the problem. Secure software release engineering balances risk remediation with reliability and reversible change.