CTFL-v4 Testing Throughout the SDLC Practice Question
Which approach is most appropriate for maintaining quality when a project uses a DevOps culture with continuous deployment?
⚠ Common exam trap
Candidates often select 'manual exploratory testing' as the primary approach, which is too slow and inconsistent for a continuous deployment pipeline requiring rapid, repeatable feedback.
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
✓
Automated regression tests integrated into the pipeline combined with production monitoring.
In continuous deployment, testing must be highly automated and integrated into the CI/CD pipeline. Shifting testing to the left ensures that code quality is verified at every commit, while monitoring provides the final feedback loop. This combination allows for rapid releases without sacrificing quality, which is the primary objective of DevOps and modern continuous testing practices.
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 exploratory testing of every build before it is moved to production.
Why it's wrong here
Manual testing is too slow to support a continuous deployment model. Relying on manual testing creates a bottleneck that slows down the release cycle, preventing the team from achieving continuous delivery. Automated suites are required to handle repetitive tasks quickly and provide immediate feedback on build stability and quality.
- ✓
Automated regression tests integrated into the pipeline combined with production monitoring.
Why this is correct
Automated pipelines provide rapid verification of code changes, while production monitoring acts as a safety net. This dual approach ensures that defects are caught early in the development cycle and that any issues escaping to production are identified and addressed immediately, supporting a stable, high-speed release process.
- ✗
Performing formal, document-heavy system testing cycles after every code merge.
Why it's wrong here
Formal, document-heavy processes are too heavy for DevOps environments. These activities are time-consuming and create friction in the development pipeline, which contradicts the DevOps goal of rapid, iterative delivery. DevOps relies on lightweight, automated, and continuous feedback loops rather than batch-based, document-centric verification cycles.
- ✗
Requiring a separate QA phase where developers are not involved in testing.
Why it's wrong here
Separate QA phases create hand-offs and delays that break the DevOps flow. Collaboration between developers and testers is essential for rapid feedback. Encouraging shared responsibility for quality ensures that code is written with testability in mind, reducing the time required for bug fixes and deployments.
Visual reference
About these practice questions
Courseiva writes every CTFL-v4 question from scratch — 144 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 ISTQB exam blueprint
This CTFL-v4 practice question is part of Courseiva's free ISTQB 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 CTFL-v4 exam.