ITIL4F ITIL Management Practices Practice Question
Which type of change is pre-approved and follows a low-risk, well-defined procedure?
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
✓
Standard change
Standard changes are pre-approved with a defined procedure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Service request
Why it's wrong here
A service request is a formal request from a user for something that is a normal part of service delivery, such as providing information, a standard change, or access to a service. While some service requests might trigger a pre-approved standard change, the service request itself is a request for a service action, not a change type in the context of change enablement. It follows a defined, repeatable workflow for fulfillment, distinct from the change control process for modifying services.
- ✗
Normal change
Why it's wrong here
A normal change is a non-standard change that needs to be scheduled, assessed, and authorized following a full change enablement process. These changes typically involve significant risk, cost, or impact, requiring formal approval from a change authority, such as a Change Advisory Board (CAB), before implementation. Therefore, they are explicitly not pre-approved and do not inherently follow a low-risk profile, making them unsuitable for the description.
- ✓
Standard change
Why this is correct
A standard change is a pre-authorized change that is low-risk, relatively common, and follows a documented procedure or work instruction. These changes are typically well-understood, have a proven implementation plan, and are often initiated as service requests. Because their risk is assessed and approved in advance, they do not require additional authorization each time they are implemented, aligning perfectly with the description of being pre-approved and low-risk.
- ✗
Emergency change
Why it's wrong here
An emergency change is a change that must be implemented as soon as possible, typically to resolve an incident or implement a critical security patch, to restore service or prevent a major impact. While they are expedited, they are not pre-approved in the same manner as standard changes; instead, they often undergo a separate, rapid assessment and authorization process, sometimes with retrospective approval. Their inherent urgency and often high impact mean they are certainly not considered low-risk.
Go deeper
Related to this question
About these practice questions
One of 531 original ITIL4F practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.