ITIL4-CDS Create, Deliver and Support Practice Question
A service provider is transitioning to a 'DevOps' model. How should they adjust their approach to 'Change Enablement' compared to traditional ITIL approaches?
⚠ Common exam trap
Many candidates incorrectly believe DevOps eliminates change enablement entirely, missing that it actually automates the approval process through policy-driven checks within the pipeline.
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
✓
By replacing manual review boards with automated policy checks.
In a DevOps model, Change Enablement shifts from manual, bureaucratic approvals to automated, policy-driven gates. This allows for higher velocity without compromising quality. By embedding compliance and risk checks directly into the CI/CD pipeline, the organization achieves faster delivery while still maintaining the rigorous standards required for production stability, which is a key shift in ITIL 4 CDS methodology.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
By eliminating all approval steps to increase speed.
Why it's wrong here
DevOps does not mean 'no control.' It means 'automated control.' Eliminating all approvals would be dangerous and irresponsible. The goal is to move from manual, human-centric approval boards to automated, policy-based checks that verify security, performance, and compliance automatically, ensuring that speed does not come at the cost of stability.
- ✓
By replacing manual review boards with automated policy checks.
Why this is correct
Automation is the cornerstone of DevOps change management. By replacing manual Change Advisory Boards (CABs) with automated pipeline gates that verify tests, security scans, and peer reviews, the organization can accelerate the deployment cycle while keeping risk well-managed and within defined organizational parameters, effectively scaling the service delivery process.
- ✗
By requiring that all changes undergo a CAB review.
Why it's wrong here
Requiring a CAB review for every change is the traditional, slow model. DevOps focuses on increasing the frequency of deployments. If every change required manual CAB approval, the system would stall. The modern approach is to automate the approval for low-risk changes and focus human intervention on high-risk, complex changes.
- ✗
By focusing only on security and ignoring performance testing.
Why it's wrong here
DevOps requires a holistic approach to quality. Performance, security, and functionality are all critical. Ignoring one in favor of another would lead to unstable, unreliable services. A robust CI/CD pipeline must include automated checks for all these areas to ensure that every release meets all defined quality and stability standards.
About these practice questions
Courseiva writes every ITIL4-CDS question from scratch — 155 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 →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PeopleCert/AXELOS exam blueprint
This ITIL4-CDS practice question is part of Courseiva's free PeopleCert/AXELOS 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 ITIL4-CDS exam.