ITIL4-CDS Create, Deliver and Support Practice Question
An IT team is adopting a 'Continuous Delivery' model. Which activity is critical for ensuring that quality remains high during frequent releases?
⚠ Common exam trap
Candidates often mistakenly believe that manual sign-offs or post-release testing phases are sufficient for Continuous Delivery, overlooking the absolute necessity of automated testing 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
✓
Integrating automated testing into the deployment pipeline.
In Continuous Delivery, the goal is to make releases reliable and low-risk through automation. Automated testing, integrated into the pipeline, ensures that every code change is validated immediately. This reduces human error, provides rapid feedback, and allows the team to maintain high quality despite high deployment frequency. By shifting testing left, the organization ensures that defects are identified and mitigated before they impact the production environment, supporting stable service delivery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Performing manual acceptance tests for every single code commit.
Why it's wrong here
Manual testing for every commit is unsustainable in Continuous Delivery and creates massive bottlenecks. Automated pipelines are essential to handle the volume and frequency of commits, as manual intervention simply cannot scale to meet the demands of modern, rapid release cycles in a competitive market.
- ✓
Integrating automated testing into the deployment pipeline.
Why this is correct
Automated testing is the foundation of high-quality continuous delivery. It ensures that regressions are caught immediately after a commit, allowing developers to address issues quickly. This automation is necessary to support the speed of delivery while maintaining the stability and reliability required by business services.
- ✗
Limiting the number of releases to once per month to allow for testing.
Why it's wrong here
Continuous Delivery aims for high-frequency releases, not monthly intervals. Limiting releases to once a month defeats the purpose of the methodology, which seeks to reduce the feedback loop and provide value to the customer as quickly as possible through small, iterative, and frequent deployments.
- ✗
Relying on the operations team to manually verify all code changes in production.
Why it's wrong here
Manual verification in production is highly risky and violates the principle of automating quality assurance. Testing should occur in a pre-production environment via the pipeline, ensuring that the production environment remains stable and that quality is verified before any changes go live to the end users.
About these practice questions
One of 155 original ITIL4-CDS practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.