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