Courseiva

ITIL4F Key Concepts of IT Service Management Practice Question

Exhibit

Refer to the exhibit.
```
Change: CHG00123
Type: Normal
Status: Pending Approval
Risk: Medium
```

The exhibit shows a change request. What is the next step in the change enablement process for this change?

⚠ Common exam trap

The trap is that candidates may think the change has already been assessed and authorized, but in ITIL, the change request must be reviewed and approved by the change authority before implementation. The exhibit shows a submitted change request, not yet approved.

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

✓

Submit the change to the change authority for approval

The correct option is A: Submit the change to the change authority for approval. In change enablement, once a change request has been raised and assessed, it must be authorized by the appropriate change authority before any implementation begins, ensuring risk and impact are formally accepted. Options B, C, and D do not fit because rolling back applies only after an implemented change fails, implementing immediately bypasses required authorization, and closing the record can only occur after the change has been approved, implemented, and reviewed.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Submit the change to the change authority for approval

    Why this is correct

    Following the initial logging and categorization of a change request, the next critical step in a structured change management process is to formally submit it to the designated change authority. This authority, often a Change Advisory Board (CAB) or an individual, is responsible for evaluating the proposed change's risks, benefits, and impact on services and stakeholders. Their approval is a mandatory prerequisite, ensuring that the change aligns with organizational objectives and does not introduce undue disruption before any implementation activities can commence. This step prevents unauthorized or poorly assessed modifications to the live environment.

  • ✗

    Roll back the change

    Why it's wrong here

    Rolling back a change is an action typically reserved for situations where an implemented change has failed or introduced unforeseen negative consequences, necessitating a return to the previous stable state. Since the question implies the change request is still in an early stage (awaiting approval, not yet implemented), initiating a rollback at this point is entirely premature and illogical. A rollback plan is usually developed *before* implementation as a contingency, but the execution of the rollback itself only occurs post-implementation if the change proves unsuccessful or harmful.

  • ✗

    Implement the change immediately

    Why it's wrong here

    Implementing a change immediately, without prior assessment and formal approval from the change authority, bypasses critical governance and risk management controls. This approach significantly increases the likelihood of service disruption, security vulnerabilities, or non-compliance, as the change's potential impact has not been adequately evaluated. Proper change management dictates that implementation activities, such as building, testing, and deploying, only proceed once the change has received explicit authorization, confirming its viability and alignment with organizational policies.

  • ✗

    Close the change record

    Why it's wrong here

    Closing a change record signifies the completion of the entire change lifecycle, meaning the change has been successfully implemented, verified, and post-implementation reviews have been conducted. Since the change request is still in an early stage, awaiting approval and certainly not yet implemented, closing the record at this point would be highly premature and indicate a failure to follow the established change management process. The record remains open to track progress through approval, implementation, and review stages.

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 →

How Courseiva writes practice questions · Editorial policy

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.