ITIL4-CDS Create, Deliver and Support Practice Question
Exhibit
CLI Output: $ git commit -m "Fix critical bug" $ ./run-tests.sh [FAILED] Test_DB_Connection_Timeout [ABORTED] Deployment_Pipeline_Stopped
Refer to the exhibit. The CLI output shows a failed test during a deployment cycle. What is the most appropriate action based on the 'Create, Deliver and Support' guidance?
⚠ Common exam trap
Candidates often assume that failed tests should be documented as known errors while deployment continues, ignoring the core CDS rule that a failed test must halt 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
✓
Analyze the failed test, fix the issue, and restart the pipeline.
In a continuous delivery model, a failed test must stop the deployment pipeline immediately. This prevents defective code from reaching production, which is a critical safeguard. The team must treat this as an urgent signal to fix the underlying issue before proceeding. This practice upholds the principle of 'building quality in' and ensures that the production environment remains reliable, which is the primary objective of automated pipeline controls.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Proceed with deployment and fix the test error in the next release.
Why it's wrong here
Deploying code after a failed test is a dangerous practice that increases the risk of production outages. Continuous delivery pipelines are designed specifically to prevent this, ensuring that only validated, high-quality code is deployed, thereby protecting the business from the consequences of deploying faulty software updates.
- ✗
Manually override the test failure to maintain the release schedule.
Why it's wrong here
Overriding failed tests compromises the integrity of the delivery pipeline. The schedule should never take precedence over the quality and stability of the production environment, as manual overrides introduce hidden risks that can lead to significant downtime or data loss, damaging the organization's reputation and customer trust.
- ✓
Analyze the failed test, fix the issue, and restart the pipeline.
Why this is correct
The pipeline acted correctly by stopping. The team must now address the failure—likely a connection configuration issue—before attempting another deployment. This ensures that the code meets quality standards, reinforcing the discipline required to maintain a stable and reliable service delivery process in a high-velocity IT environment.
- ✗
Ignore the test failure as it is likely a transient environmental issue.
Why it's wrong here
Assuming a failure is transient is a common mistake that leads to recurring production issues. All failures must be treated as valid until proven otherwise. Ignoring them skips the critical feedback loop that allows teams to identify and resolve genuine stability problems before they impact the end user.
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.