ITIL-4-Foundation VCE Exam Download

Error control also regularly re-assesses the status of known errors that have not been resolved, taking account of the overall impact on customers and/or service availability, and the cost of permanent resolutions, and effectiveness of workarounds

In ITIL 4, a service request is defined as a user request for information, advice, or a standard change, or for access to a service.

A user asking, “How do I create a report?” and contacting the service desk is:

Requesting information/advice

A normal, expected interaction with the service

Not reporting a service failure or interruption

Handling such requests is the purpose of the service request management practice, which ensures that:

Service requests are handled efficiently and user-friendly

Users receive help, information, or access according to agreed procedures

Requests follow pre-defined workflows where possible

Therefore, the practice most likely to help in solving this issue is C. Service request management.

Why the other options are incorrect:

A. Incident managementIncident management deals with unplanned interruptions, reductions in service quality, or failures. Here, the service is working; the user just needs guidance, not restoration of service.

B. Service level managementThis focuses on defining, negotiating, and managing service level agreements (SLAs) and overall service performance, not answering “how to” questions.

D. Change enablementThis practice manages changes to services and components, reducing risk. A user asking how to create a report is not requesting a change to the service.

References (Aligned with ITIL 4 Foundation concepts)

ITIL 4 Foundation: Definition of service request and service request management

ITIL 4 Foundation: Distinction between incidents and service requests

Costs are the amount of money spent on a specific activity or resource. From the service consumer’s perspective, there are two types of cost involved in service relationships:

Costs removed from the consumer by the service (a part of the value proposition). For example, for a car sharing service, the customer does not pay for the actual cost of purchasing the car.

The purpose of the service request management practice is to support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner. Service request management is dependent upon well-designed processes and procedures, which are operationalized through tracking and automation tools to maximize the efficiency of the practice. To be handled optimally, service request management should follow these guidelines:

Service requests and their fulfilment should be standardized and automated to the greatest degree possible.

Policies should define which service requests will be fulfilled with limited or even no additional approvals so that fulfilment can be streamlined.

The expectations of users regarding fulfilment times and costs should be clearly set, based on what the organization can realistically deliver.

Opportunities for improvement should be identified and implemented to produce faster fulfilment times and take advantage of automation.