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

Questions 6–10

1. 6foundation · medium

   Which of the following is a common code smell that static analysis tools can detect?

   • AHigh test coverage
   • BClear naming conventions
   • CLong parameter list
   • DProper exception handling
   Reveal Solution Discussion Select an answer first
2. 7foundation · medium

   Which of the following is a capability of static analysis tools that supports maintainability improvement?

   • AMeasuring runtime performance under load
   • BExecuting unit tests to verify behavior
   • CDetecting duplicated code across the codebase
   • DIdentifying security vulnerabilities in deployed applications
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A static analysis tool flags a 'long parameter list' smell in a method. The team is considering refactoring. Which limitation of static analysis should they keep in mind?

   • AThe tool will automatically refactor the method to use a parameter object.
   • BThe tool cannot detect long parameter lists in dynamically typed languages.
   • CThe tool cannot determine whether the long parameter list is actually a problem in context.
   • DThe tool requires a running application to detect the smell.
   Reveal Solution Discussion Select an answer first
5. 9application · medium

   A static analysis report shows a 'duplicated code' smell in several modules. The team wants to improve maintainability. Which action is most appropriate?

   • AExtract the duplicated code into a shared method or class.
   • BCopy the duplicated code to more places to make it consistent.
   • CUse a macro to replace all duplicated code.
   • DIgnore the duplication because it is not a functional defect.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A team maintains a legacy order-processing module. Static analysis reports a high number of 'feature envy' warnings, where methods in one class heavily use another class's data. The team wants to improve maintainability. Which action best addresses the root cause indicated by these warnings?

   • ARefactor the methods to use global variables instead of accessing another class's data.
   • BAdd more comments to the offending methods to clarify their intent.
   • CIncrease the cyclomatic complexity threshold in the tool configuration to suppress these warnings.
   • DMove the offending methods into the class whose data they use most.
   Reveal Solution Discussion Select an answer first