Question 590
A team uses a shared issue register but marks recurring defects closed each week without tracking their root cause. The team proposes this response: Trend repeated failures and assign corrective action to underlying causes, not just repeated ticket closure. What observation MOST convincingly validates that the change worked?
Explanation
Correct Answer
This measured result tests the stated action in the present scenario: Trend repeated failures and assign corrective action to underlying causes, not just repeated ticket closure. The evidence is Retest evidence shows failure recurrence falls and ownership remains clear until verification. Without that evidence, the unresolved failure is: High issue-closure counts can disguise a persistent systemic bottleneck.
Incorrect Answers
Sponsors compare revised capacity options against the new demand pattern and select an evidenced alternative. However, this does not establish the required outcome: retest evidence shows failure recurrence falls and ownership remains clear until verification.
Acceptance tests and transition material reflect the encryption change and the validated operating workflow. However, this does not establish the required outcome: retest evidence shows failure recurrence falls and ownership remains clear until verification.
The API constraint is resolved or a tested alternative is implemented before it threatens the committed outcome. However, this does not establish the required outcome: retest evidence shows failure recurrence falls and ownership remains clear until verification.