ITIL4-CDS Create, Deliver and Support Practice Question
When designing a new service, which 'Key Consideration' is most critical for ensuring long-term maintainability?
⚠ Common exam trap
Candidates often select 'feature-rich design' or 'low development cost,' ignoring that long-term maintainability is fundamentally dependent on being able to observe and troubleshoot the system once it is live.
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
✓
Including comprehensive logging and monitoring capabilities from the start.
Designing for maintainability involves planning for how a service will be supported, updated, and scaled throughout its lifecycle. By integrating operational requirements early, teams ensure that the service is built to be resilient and easily manageable. This reduces the 'technical debt' that often plagues projects where supportability is an afterthought, ensuring that the service can continue to provide value without becoming an unsustainable burden for the operations team.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Selecting the most cutting-edge technologies available, regardless of team expertise.
Why it's wrong here
Choosing technology purely for its novelty without considering team expertise creates significant long-term support risks. If the team lacks the skills to maintain the service, any incident becomes a crisis, and updates become difficult. Maintainability requires a balance between modern capabilities and the team's ability to actually support the technology.
- ✓
Including comprehensive logging and monitoring capabilities from the start.
Why this is correct
Logging and monitoring are non-negotiable for maintainability. They provide the visibility needed to understand service behavior, troubleshoot issues, and optimize performance. Without these features, supporting the service becomes a 'black box' exercise, leading to high downtime and increased difficulty in managing the service throughout its operational life.
- ✗
Minimizing the number of external dependencies to ensure absolute simplicity.
Why it's wrong here
While simplicity is a goal, some dependencies are inevitable in modern architecture. Rigidly minimizing dependencies can lead to the 'not-invented-here' syndrome, where teams build custom, unmaintained components instead of using reliable, supported standards. The goal is to manage dependencies effectively, not necessarily to reduce them to an absolute minimum.
- ✗
Focusing exclusively on the user interface design to maximize customer adoption.
Why it's wrong here
While UI is important for user experience, focusing on it at the expense of backend maintainability is a recipe for disaster. A service that looks great but is impossible to monitor or update will eventually fail the user when the inevitable operational issues arise, causing long-term damage to the service's reputation.
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.