ITIL 4 Managing Professional ITIL-4-Specialist-Monitor-Support-Fulfil Passing Score

In ITIL 4, incidents are categorized based on their impact and urgency, and the way they are managed depends on their classification. Let’s break down the various types of incidents mentioned in the question:

Recurring Incidents (Answer A):These are incidents that have been identified and occur frequently, often with well-documented resolutions (e.g., through a known error or workaround). Due to their recurring nature and the availability of established solutions, these incidents typically do not require an individual review upon resolution. Instead, they may be reviewed in bulk periodically or handled through predefined processes. According to theITIL Service Operationpractice, recurring incidents are often managed throughProblem Management, where known errors or workarounds can be applied without requiring a detailed review every time. This makes recurring incidents the correct answer.

Major Incidents (Answer B):Major incidents are high-impact, urgent incidents that require immediate attention and ofteninvolve significant resources. ITIL 4 specifies that major incidents should always undergo an individual review to assess the incident's cause, resolution time, and how the incident was handled to avoid future recurrences. This is part of thePost-Incident Reviewprocess outlined in theIncident Managementpractice, ensuring lessons are learned and improvements are made.

New Types of Incidents (Answer C):New types of incidents are unfamiliar and do not have a predefined resolution or known error in place. These incidents typically require careful investigation and review upon resolution to ensure they were handled appropriately and to determine if any preventive measures need to be taken. ITIL 4 promotes continuous learning from such incidents to improveKnowledge Managementand prevent future occurrences.

Incidents Not Resolved in Time (Answer D):Incidents that are not resolved within the agreed time frame (Service Level Agreement breaches) are typically reviewed to understand why the service level was not met. Such incidents are important forService Level Managementto ensure that corrective actions are taken and similar delays do not occur in the future.

ITIL 4 References:

Incident Management Practice:ITIL emphasizes efficient handling of incidents to restore service operation quickly. Recurring incidents often have aknown errorand are resolved using documented procedures, hence not requiring detailed individual review each time.

Problem Management Practice:This deals with analyzing recurring incidents, identifying their root cause, and either resolving them permanently or establishing a workaround.

Service Level Management Practice:Incidents breaching the SLA (Answer D) are usually reviewed to improve performance and ensure compliance in future instances.

Theevent handlingprocess is triggered by events that indicate deviations from normal performance.Service performance thresholdsare predefined levels of acceptable performance, and they act as inputs to the event handling process, helping to determine whether an event should trigger an alert or require further action.

Service Performance Thresholds: These thresholds define the boundaries of acceptable performance. When exceeded, they trigger events that are handled by the event management process.

Option D ("Service performance thresholds")is the correct answer because these thresholds are key inputs that trigger events when breached​​.

Incorrect Options:

Option A (Service health criteria): This focuses on broader health monitoring but isn't directly linked to event triggers.

Option B (Service catalogue): This outlines available services but doesn’t trigger events.

Option C (Monitoring plan): This guides monitoring activities but isn’t an input to event handling itself.

The service desk practice in ITIL 4 is the single point of contact between the service provider and the users, focusing on incident resolution and service request management. Partners and suppliers can support this practice by providingtrained resourcesto work in service desk teams. This aligns with the“Partners and Suppliers” dimensionof service management, which emphasizes that external organizations can supply expertise, resources, or technology that help the service provider meet its objectives​​.

ITIL encourages collaboration with external partners when the internal organization lacks the necessary resources or expertise. Providing trained resources enhances the service desk's ability to efficiently resolve incidents and handle requests, ensuring continuity and service quality​.

Other options, such as providing change enablement tools or outsourcing IT services, do not directly support the service desk in its role of handling incidents and requests.

Theservice request managementpractice in ITIL 4 is responsible for handling all pre-defined, user-initiated service requests. These are typically requests for something that is already part of an agreed-upon service offering (for example, password resets or access to software).

Agreed Service Actions: This refers to standard service actions that are defined and documented, such as software access or user account creation. Service request management ensures that such requests are handled efficiently and in line with agreed service levels.

Option A ("Requests that initiate an agreed service action")is the correct answer, as it aligns with the purpose of service request management, which is to handle routine requests for agreed service actions​​.

Incorrect Options:

Option B: Requesting the design of a new service falls under service design, not service request management.

Option C: Requests to resolve an interruption to a service are incidents, not service requests.

Option D: Determining the root cause of an incident relates to problem management, not service request management.