ITIL4-CDS Create, Deliver and Support Practice Question
A software development team is transitioning to a CI/CD pipeline. They want to ensure that code quality remains high while deployment speed increases. Which practice should the team integrate into their pipeline to best support this objective?
⚠ Common exam trap
Candidates often suggest manual quality checks or post-deployment reviews, failing to recognize that CI/CD pipelines require 'shift-left' automation to maintain speed without sacrificing quality.
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
✓
Shift-left testing and automated validation
Integrating automated testing and continuous integration allows the team to detect defects early in the development lifecycle. This reduces the cost of fixing bugs and ensures that every code commit meets predefined quality standards before moving to deployment. By automating these checks, the team achieves both speed and stability, which is core to the CDS value proposition of creating high-quality services rapidly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manual code review for every single commit
Why it's wrong here
Manual reviews are time-consuming and create bottlenecks in high-velocity pipelines. While peer reviews are valuable, relying solely on manual processes for every commit prevents the continuous flow of value. Automation is required to scale development efforts effectively while maintaining consistent quality standards across the entire delivery lifecycle.
- ✓
Shift-left testing and automated validation
Why this is correct
Shift-left testing involves moving testing activities earlier in the development process to identify issues immediately. Automated validation ensures that code is verified against quality gates automatically, which is essential for CI/CD pipelines. This approach minimizes rework and ensures only stable, validated code proceeds through the deployment stages.
- ✗
Frequent releases to production without testing
Why it's wrong here
Releasing without testing ignores quality assurance and significantly increases the risk of production incidents. ITIL CDS emphasizes the importance of building quality into services. Eliminating testing phases compromises service stability and violates the principle of value co-creation, leading to poor customer experiences and increased operational debt for teams.
- ✗
Post-deployment monitoring as the primary quality gate
Why it's wrong here
Relying on post-deployment monitoring means that defects are only discovered after they impact end-users. While monitoring is a critical CDS activity, it is not a substitute for proactive testing in the CI/CD pipeline. A robust quality strategy requires validating code before it ever reaches the production environment.
About these practice questions
This ITIL4-CDS question is part of Courseiva's 155-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.