nerdexam
PeopleCert

ITIL-FOUNDATION · Question #84

A known error has been created after diagnosis of a problem was complete but before a workaround has been found. Is this a valid approach?

The correct answer is A. Yes: for information purposes, a known error record can be created at any time it is prudent to do so. ITIL explicitly allows a known error record to be created at any point during problem management when it is prudent to do so, including before a workaround is identified.

Know the purpose of the ITIL practices

Question

A known error has been created after diagnosis of a problem was complete but before a workaround has been found. Is this a valid approach?

Options

  • AYes: for information purposes, a known error record can be created at any time it is prudent to do so
  • BNo: the Known Error should be created before the problem is logged
  • CNo: a known error record is created when the original incident is raised
  • DNo: a known error record should be created with the next release of the service

How the community answered

(32 responses)
  • A
    75% (24)
  • B
    3% (1)
  • C
    16% (5)
  • D
    6% (2)

Why each option

ITIL explicitly allows a known error record to be created at any point during problem management when it is prudent to do so, including before a workaround is identified.

AYes: for information purposes, a known error record can be created at any time it is prudent to do soCorrect

ITIL problem management guidance states that a known error record may be raised at any time it is useful to record the diagnostic information, even if diagnosis is incomplete or no workaround has yet been found. Creating the record early makes the known information available to incident management teams so they can reduce resolution time on future occurrences of the same issue. Waiting for a workaround before creating the record would unnecessarily delay the sharing of partial but valuable diagnostic knowledge.

BNo: the Known Error should be created before the problem is logged

ITIL does not require a known error to exist before the problem is logged; the problem record is always created first, and known errors are identified as a result of subsequent investigation.

CNo: a known error record is created when the original incident is raised

Known error records are a product of problem management investigation and cannot be created at incident logging time, since no root cause analysis has taken place yet when the incident is first raised.

DNo: a known error record should be created with the next release of the service

Known error records are independent of release cycles and should be created as soon as the diagnostic information makes it prudent, not deferred until the next service release.

Concept tested: ITIL known error record creation timing in problem management

Source: https://www.axelos.com/certifications/itil-service-management/itil-4-foundation

Topics

#problem management#known error#known error database#workaround

Community Discussion

No community discussion yet for this question.

Full ITIL-FOUNDATION Practice