ITIL4F Four Dimensions of IT Service Management Practice Question
When a change is low-risk and can be implemented without a formal change request, which type of change is this?
⚠ Common exam trap
Watch out — candidates often confuse a Standard change with a Service request, but a Service request is a user-initiated request for something that is not a change (e.g., password reset), while a Standard change is a pre-approved change to an IT service or infrastructure component.
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-approved, low-risk change that follows a documented procedure and does not require a formal change request or approval from the Change Authority. In ITIL 4, this type of change is typically implemented via a service request or a predefined workflow, such as applying a routine security patch or provisioning a standard virtual machine. The key differentiator is that the risk and impact are well-understood and the procedure is already authorized, making it suitable for implementation without a formal change request.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Standard change
Why this is correct
A Standard change is pre-authorised and follows a defined, low-risk procedure, satisfying the stem’s constraint that no formal change request is needed. This contrasts with a Normal change, which always requires a formal request and approval, and an Emergency change, which demands urgent authorisation. The axis of difference is the pre-approval status: Standard changes are approved in advance by the change authority, enabling implementation without a new request each time.
- ✗
Normal change
Why it's wrong here
Normal changes require a formal change request and assessment before implementation, so this fails the low-risk, no-request condition. It is tempting because normal changes are the standard route for scheduled, assessed work, and would be correct for a routine change needing Change Advisory Board review and authorisation.
- ✗
Emergency change
Why it's wrong here
Emergency changes address incidents or urgent issues requiring expedited handling, typically with a retrospective change request, so they do not match a low-risk change needing no request. It is tempting because emergency changes also bypass normal change-request routing, and would be correct for an urgent fix to a major incident.
- ✗
Service request
Why it's wrong here
A service request is a user-initiated request for something pre-approved, such as a password reset, not a change to a service. It is tempting because service requests bypass formal change requests, but they deliver standard pre-authorised items rather than implementing a low-risk change.
Go deeper
Related to this question
About these practice questions
One of 805 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.