CAS-003 · Question #811
An application developer is including third-party background security fixes in an application. The fixes seem to resolve a currently identified security issue. However, when the application is…
The correct answer is A. Peer review. NOTE: The marked answer (A - Peer review) is likely incorrect for this scenario. When a previously fixed vulnerability re-emerges after new code changes are introduced, the root cause is a regression. The process specifically designed to catch regressions is regression testing…
Question
An application developer is including third-party background security fixes in an application. The fixes seem to resolve a currently identified security issue. However, when the application is released to the public, report come In that a previously vulnerability has returned. Which of the following should the developer integrate into the process to BEST prevent this type of behavior?
Options
- APeer review
- BRegression testing
- CUser acceptance
- DDynamic analysis
How the community answered
(40 responses)- A95% (38)
- B3% (1)
- C3% (1)
Explanation
NOTE: The marked answer (A - Peer review) is likely incorrect for this scenario. When a previously fixed vulnerability re-emerges after new code changes are introduced, the root cause is a regression. The process specifically designed to catch regressions is regression testing (B) - a form of testing that re-executes prior test cases against updated code to confirm that previously resolved issues have not resurfaced. Peer review can catch logical errors but does not systematically re-validate prior fixes. Integrating regression testing into the CI/CD pipeline would directly prevent the described behavior. The correct answer should be B.
Topics
Community Discussion
No community discussion yet for this question.