ITIL4-CDS Create, Deliver and Support Practice Question
A development team is struggling with high levels of 'technical debt' that hinders their ability to deliver new features. Which approach best aligns with CDS guidance to balance flow and quality?
⚠ Common exam trap
Candidates often suggest stopping new feature development entirely to fix debt, ignoring the need to balance ongoing business value delivery with necessary technical maintenance.
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
✓
Allocate a fixed percentage of capacity in every sprint to address technical debt and refactoring.
CDS emphasizes the importance of managing technical debt as part of the value stream. By incorporating refactoring and maintenance tasks into the regular planning cycle rather than treating them as separate projects, teams ensure long-term sustainability. This balance prevents the accumulation of issues that slow down future velocity, ensuring the continuous delivery of value remains viable while maintaining system integrity and service reliability over time.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Pause all feature development for three months to rewrite the entire legacy codebase.
Why it's wrong here
Stopping all feature delivery creates a massive delay in value realization for the business. This radical approach often leads to new bugs and missed market opportunities, failing to address the underlying need for incremental improvement and continuous delivery cycles promoted by the ITIL CDS framework.
- ✗
Prioritize technical debt only when a critical incident occurs in the production environment.
Why it's wrong here
Reactive management of technical debt leads to unstable systems and constant firefighting. ITIL CDS advocates for proactive management where technical debt is prioritized alongside features, allowing teams to maintain a steady flow of value without waiting for catastrophic failures to justify necessary system improvements.
- ✓
Allocate a fixed percentage of capacity in every sprint to address technical debt and refactoring.
Why this is correct
Allocating dedicated capacity ensures that technical debt is addressed consistently. This practice prevents the accumulation of unmanageable code quality issues while allowing the team to continue delivering business value, directly supporting the CDS focus on balancing velocity, quality, and the overall health of the service architecture.
- ✗
Require the product owner to approve all refactoring tasks as individual business projects.
Why it's wrong here
Treating refactoring as separate projects adds unnecessary administrative overhead and slows down the development lifecycle. This bureaucratic approach ignores the reality that code quality is an intrinsic part of service delivery and should be managed as an ongoing operational activity rather than a series of business projects.
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.