For which of the following would a static analysis tool be MOST useful?

Question

Options

• ASupporting reviews.
• BValidating models of the software.
• CTesting code executed in a special test harness.
• DEnforcement of coding standards.

• A
  2% (1)
• B
  12% (5)
• C
  5% (2)
• D
  81% (34)

Explanation

Static analysis tools examine source code without executing it, making them ideal for automatically checking code against predefined rules and standards - exactly what option D describes. Tools like ESLint, SonarQube, and Checkstyle were built precisely for this: enforcing naming conventions, formatting rules, complexity limits, and banned patterns at scale across an entire codebase.

Why the distractors are wrong:

• A (Supporting reviews): Static analysis can assist reviews, but human code review is the primary activity; static tools are a supplement, not the main mechanism.
• B (Validating models): Model validation applies to UML diagrams and design artifacts - this is the domain of model checkers and formal methods, not static analyzers working on source code.
• C (Testing code in a test harness): A test harness executes code, which is dynamic analysis by definition - the opposite of static analysis.

Memory tip: Think of "static" as "stationary" - the code never runs. Anything that requires execution (testing, runtime behavior) is dynamic. Standards enforcement is a purely textual/structural check, so it maps perfectly to static analysis.

No community discussion yet for this question.