ITIL4F ITIL Management Practices Practice Question
A change request to upgrade an application is classified as 'normal'. What is the correct sequence of activities for this type of change?
⚠ Common exam trap
Watch out — candidates often confuse the normal change sequence with the simpler 'request, authorize, implement' model used for standard changes, forgetting the mandatory assessment, planning, and review steps for normal changes.
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
✓
Request, assess, authorize, plan, implement, review
ITIL 4 defines the normal change sequence as: request, assess, authorize, plan, implement, and review. This ensures that all normal changes are properly evaluated for risk and impact before authorization, then planned and implemented, followed by a review to confirm success and capture lessons learned.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Request, implement, review, close
Why it's wrong here
This sequence is dangerously oversimplified, bypassing critical control points in the change enablement process. It entirely omits the essential "Assess" phase to understand impact and risk, the "Authorize" step to gain approval, and the "Plan" phase for detailed preparation. Directly moving from request to implementation without these safeguards significantly increases the likelihood of failure, service disruption, and unauthorized modifications.
- ✗
Plan, authorize, implement, review, close
Why it's wrong here
This option incorrectly places "Plan" as the initial step, completely omitting the preceding "Request" and "Assess" activities. A change must first be formally requested and then thoroughly assessed for its potential impact, risks, and benefits before any detailed planning or authorization can responsibly take place. Skipping these initial steps can lead to poorly understood or unauthorized changes being planned.
- ✗
Assess, authorize, implement, close
Why it's wrong here
This sequence is incomplete and out of order for a typical change enablement process. It omits the critical initial step of formally requesting the change, which is necessary before any assessment or authorization can occur. Furthermore, it lacks a dedicated planning phase prior to implementation, which is vital for successful execution and risk mitigation, and it skips the post-implementation review to confirm desired outcomes.
- ✓
Request, assess, authorize, plan, implement, review
Why this is correct
This sequence accurately reflects the logical and controlled flow of activities within the ITIL 4 change enablement practice. It begins with a formal "Request," followed by a thorough "Assess" phase to understand impact and risk. "Authorize" grants permission, "Plan" details the execution, "Implement" performs the change, and "Review" confirms success and captures lessons learned, ensuring a structured and effective change process.
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.