ITIL4F ITIL Management Practices Practice Question
Which type of change follows a pre-defined, low-risk procedure and is pre-approved?
⚠ Common exam trap
A common mix-up: candidates confuse 'standard change' with 'service request' because both can follow a pre-defined procedure, but ITIL 4 explicitly separates them: a service request is for standard services (e.g., password reset), while a standard change is for low-risk technical changes (e.g., applying a tested patch).
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
A standard change is a pre-defined, low-risk change that follows a specific procedure and is pre-approved by change management. It does not require a new change request each time because its risk profile and implementation steps are already documented and authorized. This aligns with ITIL 4's definition of a standard change as a change that is well-understood, fully documented, and can be implemented without additional approval.
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 standard, such as information, advice, or access to a service. While a service request might *trigger* a standard change, it is not a type of change itself in the context of change enablement. It represents the user's need, which is then fulfilled by an appropriate process, potentially a pre-defined low-risk standard change, but the request itself is distinct from the change classification.
- ✗
Normal change
Why it's wrong here
A normal change is a non-emergency change that requires assessment, authorization, and scheduling according to a defined process. Unlike standard changes, normal changes are not pre-authorized as low-risk; they undergo a full change enablement workflow to evaluate potential impact and risk before approval. This structured approach ensures proper governance for changes that are not routine or pre-approved.
- ✓
Standard change
Why this is correct
A standard change is a pre-authorized change that is low-risk, well-understood, and has a documented procedure for implementation. These changes are typically routine, frequently performed, and do not require additional authorization each time they are executed, as the risk has been assessed and approved beforehand. This classification perfectly aligns with following a pre-defined, low-risk procedure, making it efficient for common modifications.
- ✗
Emergency change
Why it's wrong here
An emergency change is implemented as quickly as possible to resolve an incident or implement a critical security fix, often bypassing some normal assessment and authorization steps. These changes are typically high-risk due to the urgency and reduced scrutiny, rather than being low-risk or following a pre-defined low-risk procedure. The primary driver is the immediate need to restore service or mitigate a severe threat, not routine low-risk execution.
Go deeper
Related to this question
About these practice questions
This ITIL4F question is part of Courseiva's 531-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.