Question 30
During a risk oversight challenge, consider: A scrum team closes a sprint when code merges even though high-risk authorization defects remain. Which risk is most likely to be overlooked by a superficial assessment?
Explanation
Correct Answer
Velocity metrics may reward shipping software before essential controls work. This is the most relevant misleading shortcut for the scenario. Investigate by doing the following: Compare definition of done, acceptance tests and security risk thresholds. A safe treatment is: Make security-critical acceptance criteria part of the release gate and remediation workflow.
Incorrect Answers
Ignoring transitive packages leaves unknown risk in the software supply chain. That would matter when a project uses open-source components but has no process for tracking transitive dependencies and vulnerability notices. The relevant distinction in this case is: Velocity metrics may reward shipping software before essential controls work.
A late penetration test cannot fully compensate for missing design-stage risk analysis. That would matter when a fintech product launches an API before conducting threat modeling or assigning security acceptance criteria. It does not address this case's requirement: A scrum team closes a sprint when code merges even though high-risk authorization defects remain.
A successful pipeline run does not prove all security requirements were fulfilled. That would matter when a continuous delivery system has no traceability between a business requirement and deployed security rules. That separate mechanism does not verify the needed risk management outcome in this case.