ITIL4F ITIL Management Practices Practice Question
Which TWO of the following are characteristics of a service request compared to an incident?
⚠ Common exam trap
ITIL4F often tests the confusion between service requests and incidents, where candidates incorrectly assume any user-reported issue is an incident rather than recognizing that pre-approved, low-risk actions are service requests.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
They are typically low-risk
Option C is correct because service requests are routine, low-risk interactions such as password resets or software installations, unlike incidents which may involve significant risk and disruption. Option D is correct because service requests follow pre-approved, standardized processes (often defined in a service catalog) with established workflows and approvals, whereas incidents require diagnosis and may need change management. Options A, B, and E are incorrect: root cause analysis is characteristic of problem management (not service requests), unplanned service interruption defines an incident, and urgency is not an inherent trait of service requests—they are handled by priority/SLA, not by being always urgent.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
They require root cause analysis
Why it's wrong here
Service requests are standard, pre-defined requests for information, advice, or access to a service component, representing normal service operation rather than a deviation. Root cause analysis (RCA) is a technique primarily employed within problem management to identify the underlying causes of incidents, aiming to prevent their recurrence. Therefore, service requests, by their very nature as routine fulfillments, do not necessitate RCA.
- ✗
They cause unplanned service interruption
Why it's wrong here
Service requests are structured, agreed-upon requests for service delivery or information, designed to be fulfilled without causing disruption to existing services. In contrast, unplanned service interruptions are the defining characteristic of an incident, which ITIL 4 defines as an unplanned interruption to a service or a reduction in the quality of a service. Fulfilling a service request is a planned activity, not a disruptive event.
- ✓
They are typically low-risk
Why this is correct
Service requests are inherently low-risk because they involve standard, well-understood procedures for providing information, access, or minor, pre-approved changes within established service parameters. Their pre-defined nature and often automated fulfillment minimize the potential for adverse impact on services or users. This characteristic ensures predictable outcomes and contributes to efficient service delivery without significant operational uncertainty.
- ✓
They are pre-approved processes
Why this is correct
A key characteristic of service requests is that they are managed through pre-approved processes, meaning the necessary authorization, resources, and steps for their fulfillment have already been established and documented. This pre-approval eliminates the need for individual approval for each request, enabling efficient, standardized handling, often through automation. This streamlines service delivery and ensures consistency in meeting user needs.
- ✗
They are always urgent
Why it's wrong here
Service requests are not inherently urgent; their priority is typically determined by business impact and agreed service level targets, not by the nature of being a request. While some service requests might be prioritized higher, they are fundamentally routine fulfillments. Urgency is more commonly associated with incidents, which demand immediate attention to restore service, whereas service requests are managed according to established timelines.
Go deeper
Related to this question
About these practice questions
Courseiva writes every ITIL4F question from scratch — 805 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PeopleCert exam blueprint
This ITIL4F practice question is part of Courseiva's free PeopleCert certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ITIL4F exam.