Using Static Analysis for Improving Maintainability CTAL-TTA Practice Questions (Page 4)

Questions 16–20

1. 16foundation · medium

   In the context of maintainability metrics, what does high cohesion within a module indicate?

   • AThe module is large in terms of lines of code
   • BThe module's elements are closely related and focused on a single purpose
   • CThe module has many dependencies on other modules
   • DThe module is difficult to understand and change
   Reveal Solution Discussion Select an answer first
2. 17foundation · medium

   Which of the following best describes the primary purpose of using static analysis tools to improve code maintainability?

   • ATo analyze code without executing it, detecting issues that affect readability and future changes
   • BTo automatically refactor code to improve its performance
   • CTo replace the need for code reviews by providing automated fixes
   • DTo execute the code and identify runtime errors
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   A static analysis tool reports a 'middle man' smell: a class that mostly delegates to another class. The team wants to improve maintainability. Which refactoring is most appropriate?

   • AAdd more delegation methods to make the middle man more useful.
   • BRemove the middle man and have clients call the real class directly.
   • CConvert the middle man into an abstract class.
   • DIgnore the smell because delegation is always good design.
   Reveal Solution Discussion Select an answer first
5. 19foundation · medium

   Which metric measures the number of independent paths through a program's source code, indicating the complexity of testing and understanding?

   • ACoupling
   • BCyclomatic complexity
   • CLines of code (LOC)
   • DCohesion
   Reveal Solution Discussion Select an answer first
6. 20application · medium

   A static analysis report shows that a payment module has high cyclomatic complexity and a 'switch statement' smell. The module is rarely modified. The team has limited refactoring budget. What is the most appropriate decision?

   • ARefactor the switch statement but leave the complexity unchanged.
   • BIncrease the complexity threshold to hide the issue.
   • CDefer refactoring and document the technical debt, since the module is rarely changed.
   • DRefactor immediately because high complexity always requires immediate action.
   Reveal Solution Discussion Select an answer first