ITIL · Question #396
When tan a known error record tie raised? (1) At any time when it would be useful to do so (2) After a workaround has been found
The correct answer is C. Neither of the above. In ITIL problem management, neither 'at any time when useful' nor 'only after a workaround is found' precisely captures the correct condition for raising a known error record.
Question
When tan a known error record tie raised? (1) At any time when it would be useful to do so (2) After a workaround has been found
Options
- A2onty
- B1 only
- CNeither of the above
- DBoth of the above
How the community answered
(36 responses)- A3% (1)
- B3% (1)
- C83% (30)
- D11% (4)
Why each option
In ITIL problem management, neither 'at any time when useful' nor 'only after a workaround is found' precisely captures the correct condition for raising a known error record.
Limiting known error records to only after a workaround is found contradicts ITIL guidance, which permits raising them as soon as the root cause is identified regardless of workaround availability.
Saying records can be raised 'at any time when useful' is imprecise because ITIL ties the known error record to a specific condition - root cause identification - not general usefulness.
ITIL defines a known error as a problem with a documented root cause, and the known error record should be raised once the root cause is identified - not simply at any arbitrary time. Statement 1 is too broad because root cause identification is the specific trigger, not general usefulness. Statement 2 is too restrictive because ITIL explicitly allows a known error record to be raised before a workaround exists, as long as the root cause is known.
Both statements are individually inaccurate in capturing the precise ITIL condition for raising a known error record, so selecting both together does not yield a correct answer.
Concept tested: ITIL known error record creation conditions
Source: https://www.axelos.com/certifications/itil-service-management/itil-foundation
Topics
Community Discussion
No community discussion yet for this question.