ITIL4-CDS Create, Deliver and Support Practice Question
A team is adopting a 'User Story' format for their requirements gathering. How does this practice contribute to the 'Create, Deliver and Support' value stream?
⚠ Common exam trap
Candidates often confuse user stories with technical task lists or functional requirements documents, incorrectly assuming the primary purpose is to capture detailed system specifications rather than focusing on user-centric value outcomes.
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
✓
It forces teams to focus on the value provided to the user rather than just technical features.
User Stories focus on the 'who, what, and why' of a requirement, centering development around the value delivered to the user. This shift helps align development teams with actual business outcomes rather than just technical specifications. By keeping requirements concise and user-centric, teams can prioritize work more effectively and ensure that the delivered output remains relevant to the needs of the customer.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It eliminates the need for any technical documentation or architecture planning.
Why it's wrong here
User stories do not replace technical documentation; they serve as placeholders for conversation. Technical architecture is still necessary for scalable and secure systems. Expecting user stories to handle all technical depth leads to poor design choices and significant long-term maintenance difficulties for the engineering team.
- ✓
It forces teams to focus on the value provided to the user rather than just technical features.
Why this is correct
By centering requirements on user value, the team ensures that their development efforts directly support business goals. This approach prevents feature creep, as every story must be justified by the value it provides, leading to a more efficient and customer-oriented delivery process.
- ✗
It guarantees that all requirements are fully defined before the development begins.
Why it's wrong here
User stories are intentionally light on detail to encourage collaboration during the development cycle. Expecting them to be 'fully defined' beforehand is a waterfall mindset that stifles the iterative flexibility needed for agile service delivery. True value is discovered through ongoing dialogue and refinement.
- ✗
It automatically ensures that the code developed will be free of any security vulnerabilities.
Why it's wrong here
User stories describe functionality, not security implementations. While they provide context, they do not replace secure coding practices, static analysis, or penetration testing. Security must be integrated into the development process through specific acceptance criteria and testing, regardless of how the requirement is formatted.
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.