A developer has spent three days looking at a system that crashes now and then. The problem was caused by two coding faults:

Question

Options

• AStatic analysis tool
• BCode coverage tool
• CDynamic analysis tool
• DTest execution tool
• IA variable was being used but had not been defined;

• A
  94% (45)
• B
  2% (1)
• C
  4% (2)

Explanation

A static analysis tool (A) examines source code without executing it, making it ideal for catching issues like undefined variables - it would have flagged this fault immediately by inspecting the code structure, saving the developer three days of intermittent crash hunting.

Why the distractors are wrong:

• B (Code coverage): Only tells you which lines were executed during tests, not whether those lines contain faults like undefined variables.
• C (Dynamic analysis): Requires the code to run to detect issues - since the crash was intermittent, the fault might not trigger during analysis, making it unreliable here.
• D (Test execution): Simply runs tests; it has no mechanism to inspect or analyze code for definition errors on its own.

Memory tip: Think of Static = Standing Still - static analysis reads the code as it sits there, without running it, just like a human reviewer would. Any bug visible by reading the code (e.g., an undefined variable) is a static analysis catch.

No community discussion yet for this question.