ISTQB Defect Management Process 5

Question 1

Which of the following scenarios best illustrates a high-priority, low-severity defect?

Accepted Answer

A misspelled company name on the homepage that causes no functional impact but is publicly visible

Answer

A misspelling on the homepage has low technical severity but high priority because it is publicly visible and reflects poorly on the organization.

Question 2

According to ISTQB, who should have the authority to close a defect report after a fix has been applied?

Accepted Answer

The tester who originally reported the defect or a designated verifier

Answer

The tester or a designated verifier confirms the fix resolves the issue before closing the defect, maintaining independence between fixing and verification.

Question 3

A defect report states: 'The system sometimes crashes.' Why is this description inadequate?

Accepted Answer

It lacks specific, repeatable steps to reproduce the crash and conditions under which it occurs

Answer

Vague defect reports that lack reproducible steps prevent developers from investigating and fixing the issue efficiently.

Question 4

What is the purpose of performing 'root cause analysis' on defects at the end of a project?

Accepted Answer

To identify systemic process or skill weaknesses that can be corrected to prevent similar defects in the future

Answer

Root cause analysis identifies underlying process or knowledge gaps so that the team can improve practices and prevent recurrence in future projects.

Question 5

Which defect lifecycle status indicates that a defect has been verified as fixed and no further action is needed?

Accepted Answer

Closed

Answer

The 'closed' status is the terminal state indicating the defect is confirmed fixed, verified, and requires no further action.

ISTQB - International Software Testing Qualifications Board Practice Test

ISTQB - International Software Testing Qualifications Board Practice Test

ISTQB Defect Management Process 5