A static analysis report shows that a critical validation class has a cyclomatic complexity of 45 and a coupling between objects (CBO) value of 28. The team wants to prioritize maintainability improvements. Which metric should be addressed first and why?

Cyclomatic complexity, because high complexity makes the class difficult to test and modify.

Coupling between objects, because high coupling directly causes runtime performance problems.

Neither, because static analysis metrics are only useful for new code, not legacy code.

Both equally, because both metrics are independent and have no impact on each other.

A static analysis report lists 500 maintainability issues. The team has limited refactoring capacity. Which prioritization strategy is most effective for improving maintainability?

Fix all issues in files that have the highest change frequency and complexity.

Disable all maintainability rules except cyclomatic complexity.

Fix issues alphabetically by file name to ensure complete coverage.

Fix only the easiest issues to quickly reduce the total count.

A static analysis report shows a high number of warnings in a module that is rarely changed. What is the most appropriate action?

Assess the severity and impact of the warnings before deciding on action

Ignore the warnings entirely because the module is rarely changed

Delete the module to eliminate the warnings

Prioritize fixing all warnings immediately regardless of impact

A team has a static analysis tool that flags maintainability issues, but developers often ignore the reports because they are too long and contain many false positives. The team wants to improve the effectiveness of static analysis for maintainability. Which approach is most effective?

Disable all maintainability rules to avoid false positives.

Require developers to fix every finding, including false positives.

Run the tool only once per release to avoid overwhelming developers.

Configure the tool to focus on a small set of high-impact rules and review findings in code review.

Certified Tester Advanced Level Technical Test Analyst

Domain 3Objective 4

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

Part of the Domain 3: Static and Dynamic Analysis domain, which makes up ~21% of our current practice bank. ISTQB does not publish an official question count, but from its 120-minute exam (~50–80 total, ~11–17 in this domain), expect 1–2 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

5concepts

Questions 1–5

1application · medium
A static analysis report shows that a critical validation class has a cyclomatic complexity of 45 and a coupling between objects (CBO) value of 28. The team wants to prioritize maintainability improvements. Which metric should be addressed first and why?
Select an answer first
2foundation · medium
Which anti-pattern is characterized by a class that has too many responsibilities, making it difficult to maintain?
Select an answer first
3application · medium
A static analysis report lists 500 maintainability issues. The team has limited refactoring capacity. Which prioritization strategy is most effective for improving maintainability?
Select an answer first
4foundation · medium
A static analysis report shows a high number of warnings in a module that is rarely changed. What is the most appropriate action?
Select an answer first
5expert · hard
A team has a static analysis tool that flags maintainability issues, but developers often ignore the reports because they are too long and contain many false positives. The team wants to improve the effectiveness of static analysis for maintainability. Which approach is most effective?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-TTA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CTAL-TTA” is a trademark of its owner, used for identification only.