ITIL4-CDS Create, Deliver and Support Practice Question
A software development team is transitioning to a Value Stream approach. They want to ensure that 'Shift Left' practices are effectively integrated into their CI/CD pipeline. Which action best supports this objective?
⚠ Common exam trap
Candidates frequently select reactive testing phases as 'Shift Left', missing the core concept that shifting left means moving quality and security tasks earlier into development.
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
✓
Automating static analysis and security scanning tasks within the developer's local environment.
Integrating testing, security, and quality assurance earlier in the development lifecycle reduces the cost of fixing defects and accelerates value delivery. Shifting left is a core CDS concept that promotes proactive quality management over reactive testing. By addressing potential issues during the design and coding phases, teams minimize rework, prevent production bottlenecks, and ensure that the final output aligns more closely with the defined value requirements from the start.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Moving all manual regression testing to occur only after the final release candidate is generated.
Why it's wrong here
Delaying regression testing until the end contradicts the shift left philosophy. This approach increases the likelihood of finding critical defects late, forcing expensive rework. It creates a bottleneck at the final deployment stage, which hampers the team's ability to maintain a rapid and reliable continuous delivery flow.
- ✗
Removing the need for developer peer reviews to increase the raw velocity of feature commits.
Why it's wrong here
Reducing peer reviews to boost speed often results in lower code quality and technical debt. While velocity is important, the shift left approach requires maintaining high quality through early collaboration. Eliminating critical review steps ignores the preventative benefits of identifying errors during the initial code drafting process.
- ✓
Automating static analysis and security scanning tasks within the developer's local environment.
Why this is correct
Automating analysis tools directly in the developer's workflow allows for immediate feedback on code quality and security vulnerabilities before the code is even committed. This shift left practice ensures that issues are resolved during the development phase, significantly reducing the downstream impact and improving overall production stability.
- ✗
Assigning more operations staff to monitor the production environment to identify bugs faster.
Why it's wrong here
Increasing operations monitoring is a reactive measure rather than a shift left practice. While useful for incident management, it does not prevent defects from reaching production. Shift left focuses on building quality into the product early, whereas this option focuses on detecting failures after they occur.
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.