ITIL4-CDS Create, Deliver and Support Practice Question
A development team is implementing shift-left testing as part of their value stream improvement initiative. The primary objective is to catch defects earlier in the creation phase. However, developers are now complaining about excessive alert fatigue and increased cycle times due to unrefined automated static code analysis tools. How should the service value system address this issue?
⚠ Common exam trap
Candidates often choose to disable the automated tools entirely or increase team size, failing to realize that the core issue is tool misconfiguration rather than a lack of resources or technology.
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
✓
Collaborate with developers and security teams to tune the static analysis rulesets, filtering out low-priority noise and actionable alerts.
Shift-left testing requires careful tuning of tools to prevent negative behavioral impacts such as alert fatigue. By refining the rulesets and prioritizing high-severity findings, the organization can restore developer trust and maintain velocity. This scenario highlights the ITIL 4 principle of 'progress iteratively with feedback' and ensures that tooling supports rather than hinders the value stream.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Revert all shift-left testing practices immediately and return to traditional late-stage testing conducted exclusively by quality assurance specialists.
Why it's wrong here
Reverting to late-stage testing completely abandons the benefits of shift-left practices, such as cost reduction and faster defect resolution. The correct approach is to refine and optimize the existing automated tools rather than discarding the entire improvement initiative.
- ✗
Disable all automated static code analysis tools and rely entirely on manual peer reviews for every code commit.
Why it's wrong here
Relying solely on manual peer reviews introduces significant human bottlenecks and inconsistency, reducing the overall throughput of the value stream. Automation remains essential for scaling development, provided the tools are configured correctly to minimize false positives.
- ✗
Increase the frequency of automated security scans to run on every keystroke in the integrated development environment.
Why it's wrong here
Running scans on every keystroke multiplies the unrefined static analysis output that caused the alert fatigue, further inflating cycle times rather than reducing noise. It is tempting because continuous integration pipelines benefit from frequent scanning, but that suits gated, incremental checks on commits, not per-keystroke execution.
- ✓
Collaborate with developers and security teams to tune the static analysis rulesets, filtering out low-priority noise and actionable alerts.
Why this is correct
Tuning static analysis rulesets with developers and security teams removes low-priority noise while preserving actionable findings, directly reducing alert fatigue and cycle times. This addresses the constraint that unrefined tooling, not shift-left itself, caused the value stream slowdown.
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.