Question 340
A network team equates a known hardware defect with every user report that mentions it. Which concern should the team recognize before proceeding?
Explanation
Correct Answer
This accounts for the described difficulty: related incidents may have a common cause, but not every incident is itself a documented known error. A direct response is to distinguish problems, underlying errors and recorded known errors from incident reports.
Incorrect Answers
This interpretation explains the observed gap: restoration of degraded service and fulfilment of a predefined request are different kinds of work. That explains why “Restoration of degraded service and fulfilment of a predefined request are different kinds of work” is useful for its own dependency, but the present failure follows a different constraint: This accounts for the described difficulty: related incidents may have a common cause, but not every incident is itself a documented known error. The targeted correction is “Related incidents may have a common cause, but not every incident is itself a documented known error”.
The proposed action focuses on a control governed by: The evidence fits this interpretation: a problem concerns the cause or potential cause of incidents, even if the exact error is not yet known. In this question the binding condition is: This accounts for the described difficulty: related incidents may have a common cause, but not every incident is itself a documented known error. Applying “Related incidents may have a common cause, but not every incident is itself a documented known error” addresses that specific cause instead.
This option would change the part of the system described by: This accounts for the described difficulty: ITIL management practices support a broad value system rather than a single technical discipline. The reported behavior instead arises because this accounts for the described difficulty: related incidents may have a common cause, but not every incident is itself a documented known error. The direct remediation is “Related incidents may have a common cause, but not every incident is itself a documented known error”.