Why is it important to include the environment details in a defect report?

Because it is required by the defect tracking tool

Because it makes the report look more professional

Because it helps the project manager assign the defect

Because the defect may only occur in a specific environment, such as a particular OS or browser

A test team finds a defect in the login module that causes a crash when a user enters a 256-character password. The defect is reproducible and occurs only in the production-like environment. The product owner wants it fixed immediately, but the development lead argues that the same code path is scheduled for a complete rewrite in the next release. During triage, which action should the team take first?

Defer the defect to the next release because the module will be rewritten, and close it as 'Won't Fix' in the current cycle.

Immediately escalate the defect to the project manager and ask them to approve an emergency fix outside the normal workflow.

Discuss the defect in the cross-functional triage meeting, weigh the crash impact against the upcoming rewrite, and decide whether to fix now, patch temporarily, or defer with a documented risk.

Assign the defect to the developer who owns the login module and mark it as 'Fixed' once the code change is committed.

What is the purpose of an 'escalation path' in a customized defect lifecycle?

To automatically close defects that have been open for a long time

To assign defects to the most junior developer available

To route high-impact defects to higher management when they are not resolved in time

To move defects from one project to another

In Agile, what is the purpose of using a backlog for defect tracking?

To store defects that will never be fixed

To assign defects to developers automatically

To track the time spent on each defect

To prioritize defects alongside features and other work items

What is a recommended practice for managing defects with outsourced teams?

Define clear communication protocols and use a shared defect tracking tool

Require the outsourced team to work the same hours as the home team

Use email for all defect communication

Avoid sharing defect information with the outsourced team

Certified Tester Advanced Level Test Management

Domain 2Objective 3

Defect Management CTAL-TM Practice Questions (Page 4)

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 16–20

16foundation · easy
Why is it important to include the environment details in a defect report?
Select an answer first
17application · medium
A test team finds a defect in the login module that causes a crash when a user enters a 256-character password. The defect is reproducible and occurs only in the production-like environment. The product owner wants it fixed immediately, but the development lead argues that the same code path is scheduled for a complete rewrite in the next release. During triage, which action should the team take first?
Select an answer first
18foundation · easy
What is the purpose of an 'escalation path' in a customized defect lifecycle?
Select an answer first
19foundation · easy
In Agile, what is the purpose of using a backlog for defect tracking?
Select an answer first
20foundation · easy
What is a recommended practice for managing defects with outsourced teams?
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.