Question 270
A development team ships production code without any security-design review for high-risk changes. What should testing demonstrate before the design is approved?
Explanation
Correct Answer
The acceptance result is a sensitive authentication change cannot ship without recorded risk review. It validates the design principle that Secure development lifecycle integrates risk controls before code is merged.
Incorrect Answers
The proposed evidence relates to another situation: A CI pipeline reports vulnerabilities but still releases images with known critical flaws. Finding vulnerabilities without an enforceable release decision is insufficient. The architect needs verification that a sensitive authentication change cannot ship without recorded risk review.
That test would support a different case: A company performs pen testing once every three years while releasing new API routes weekly. Secure lifecycle assurance must match the rate of application change. The present control must instead show that a sensitive authentication change cannot ship without recorded risk review.
It verifies another security outcome rather than the current risk: An application release has security tests but their reports are ignored by deployment approval automation. Security test value depends on enforceable downstream gates. Here the expected evidence is a sensitive authentication change cannot ship without recorded risk review.