Question 490
At fictional Lakewood Analytics, 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 dashboard combines static analysis warnings and dynamic test results into one severity count without distinguishing their evidence limits. 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
Static and dynamic testing are complementary views and neither alone establishes all exploitable paths. Each high-risk finding has traceable evidence, owner, exploitability rationale, and a validated fix test.
Incorrect Answers
This response concerns threat-based security test design. Here, a security dashboard combines static analysis warnings and dynamic test results into one severity count without distinguishing their evidence limits. The confirming evidence is: Each high-risk finding has traceable evidence, owner, exploitability rationale, and a validated fix test.
Focusing on security unit test assertions would leave this problem unresolved: A security dashboard combines static analysis warnings and dynamic test results into one severity count without distinguishing their evidence limits.
Fuzzing parser boundaries concerns another aspect of the problem. Static and dynamic testing are complementary views and neither alone establishes all exploitable paths.