Which product risk is best addressed through static testing?

Static testing is a technique that involves reviewing and evaluating the code or documentation without executing the program. It includes activities such as inspections, reviews, and static analysis. Among the options provided, the absence of key requirements in the test cases is best addressed through static testing because it allows testers to analyze the test cases against the requirements before any execution occurs.

When static testing is employed, reviewers can check if all critical requirements are adequately represented in the test cases. This process helps ensure that no essential functionality is overlooked and that the test cases are comprehensive. By validating requirements against test cases in a static environment, teams can identify gaps or omissions early in the development process, which is key to mitigating risks associated with testing.

In contrast, the other options primarily rely on dynamic testing or other forms of evaluation. For instance, verifying whether requirements are implemented correctly or assessing application performance typically necessitates actual execution of the application. Likewise, risks related to project management, such as late delivery, are more tactical and depend on various factors beyond just the testing phase. Therefore, the choice that relates directly to identifying missing requirements through documented reviews aligns well with the strengths of static testing.