A team has a static analysis report with 200 maintainability issues. The product owner wants to reduce technical debt but also requires that no new features be delayed. The team has two sprints before the next release. Which approach best balances these constraints?

Incorporate refactoring of high-risk modules into the feature work for both sprints.

Defer all refactoring until after the release to avoid any risk of delay.

Refactor high-risk modules during the first sprint and add features in the second.

Refactor all 200 issues in the first sprint to clear the backlog.

A team uses static analysis to track maintainability. They notice that the average cyclomatic complexity of the codebase has increased from 5 to 8 over the last release. What is the most appropriate action?

Ignore the increase because the average is still below 10.

Investigate which modules contributed to the increase and review their design.

Refactor all methods with complexity above 5 immediately.

Increase the complexity threshold in the tool to match the new average.

A development team uses a static analysis tool that flags 'god class' and 'long method' smells. The tool also reports a low 'lack of cohesion of methods' (LCOM) value for several classes. The team wants to improve maintainability. Which interpretation is correct?

Low LCOM means the classes are too small and should be merged.

Low LCOM is irrelevant because static analysis cannot measure cohesion accurately.

Low LCOM indicates low cohesion, so these classes should be split into smaller classes.

Low LCOM indicates high cohesion, which is generally desirable for maintainability.

Certified Tester Advanced Level Technical Test Analyst

Domain 3Objective 4

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

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 26–28

26expert · hard
A team has a static analysis report with 200 maintainability issues. The product owner wants to reduce technical debt but also requires that no new features be delayed. The team has two sprints before the next release. Which approach best balances these constraints?
Select an answer first
27application · medium
A team uses static analysis to track maintainability. They notice that the average cyclomatic complexity of the codebase has increased from 5 to 8 over the last release. What is the most appropriate action?
Select an answer first
28application · medium
A development team uses a static analysis tool that flags 'god class' and 'long method' smells. The tool also reports a low 'lack of cohesion of methods' (LCOM) value for several classes. The team wants to improve maintainability. Which interpretation is correct?
Select an answer first

Finished these 3 questions?

Review the revealed explanations, or continue through the curriculum.

No more pagesBack 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.

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

Questions 26–28

A team has a static analysis report with 200 maintainability issues. The product owner wants to reduce technical debt but also requires that no new features be delayed. The team has two sprints before the next release. Which approach best balances these constraints?

A team uses static analysis to track maintainability. They notice that the average cyclomatic complexity of the codebase has increased from 5 to 8 over the last release. What is the most appropriate action?

A development team uses a static analysis tool that flags 'god class' and 'long method' smells. The tool also reports a low 'lack of cohesion of methods' (LCOM) value for several classes. The team wants to improve maintainability. Which interpretation is correct?

Keep studying — Domain 3: Static and Dynamic Analysis