In Agile development, how are defects typically handled?

They are ignored until the next release

They are reported only at the end of the project

They are added to the product backlog and prioritized for future sprints

They are all fixed immediately in the current sprint

How can defect report data be used for process improvement?

By using the data to assign blame to individual testers

By deleting old defect reports to reduce clutter

By analyzing trends to identify root causes and areas for improvement

By using the data to justify increasing the testing budget

What is a key benefit of using a shared defect tracking tool for communication?

It eliminates the need for meetings

It automatically fixes the defects

It assigns defects to developers automatically

It provides a single source of truth for defect status and history

A company has an in-house test team in Berlin and an outsourced development team in Bangalore. A tester in Berlin logs a defect at 4:00 PM local time. The developer in Bangalore picks it up the next morning and cannot reproduce it because the defect report lacks the exact database state and the specific test data used. What is the most effective way to prevent this situation in the future?

Establish a mandatory defect report template that includes environment details, test data, and steps to reproduce, and enforce it through the defect tracking tool.

Require the tester to include a video recording of the defect occurrence with every defect report.

Have the developer in Bangalore call the tester whenever a defect is not reproducible.

Ask the tester to stay online until the developer in Bangalore starts work so they can discuss the defect live.

In defect management, what is the primary responsibility of the tester?

To report defects with clear, reproducible steps and verify fixes

To assign defects to developers

To decide which defects are fixed in a release

Certified Tester Advanced Level Test Management

Domain 2Objective 3

Defect Management CTAL-TM Practice Questions (Page 5)

Part of the Managing the Product 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 4–6 from this objective — we provide 41 practice questions to prepare you well beyond it. (estimate)

41questions here

9free pages

14concepts

Questions 21–25

21foundation · easy
In Agile development, how are defects typically handled?
Select an answer first
22foundation · easy
How can defect report data be used for process improvement?
Select an answer first
23foundation · easy
What is a key benefit of using a shared defect tracking tool for communication?
Select an answer first
24application · medium
A company has an in-house test team in Berlin and an outsourced development team in Bangalore. A tester in Berlin logs a defect at 4:00 PM local time. The developer in Bangalore picks it up the next morning and cannot reproduce it because the defect report lacks the exact database state and the specific test data used. What is the most effective way to prevent this situation in the future?
Select an answer first
25foundation · easy
In defect management, what is the primary responsibility of the tester?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CTAL-TM

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-TM” is a trademark of its owner, used for identification only.