CTFL v4.0 · ISTQB · Testing Throughout the Software Development Lifecycle · Bank updated 2026-10-01
CTFL v4.0 practice questions: Testing Throughout the Software Development Lifecycle
5 free questions from 23 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Testing Throughout the Software Development Lifecycle section of our CTFL v4.0 bank (23 questions on this area, which carries 15% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
Free: 6 questions in study mode, no card. All 23 Testing Throughout the Software Development Lifecycle questions and the full CTFL v4.0 bank: $15 one-time.
1/5 · Testing Throughout the Software Development Lifecycle
A team practices DevOps with a CI/CD pipeline. Which practice best exemplifies the shift-left philosophy within this DevOps context?
ADeploying each change straight to production first, then running exploratory tests against the live system to see whether anything broke for users.
BAutomated component and API tests run in the CI pipeline right after each commit, giving developers fast feedback before the change is merged.
CPostponing all automated tests in the CI pipeline to a nightly build, because running them on each commit would slow developers down.
DRunning only manual system tests once per release cycle, shortly before deployment, after the changes have been merged.
2/5 · Testing Throughout the Software Development Lifecycle
According to the ISTQB CTFL syllabus, what is the main purpose of holding a retrospective (e.g., an end-of-sprint retrospective) with respect to testing?
ATo identify what worked well and what could be improved in testing and other project activities, so lessons learned can be applied to future iterations.
BTo assign responsibility to specific team members for the defects found in the previous iteration, so that each person is held accountable for their own mistakes.
CTo formally sign off on the acceptance test results before the software is released to production, so the iteration can be closed with an approved record.
DTo re-execute the full regression test suite one final time before the meeting, so that the team reviews up-to-date results for the current iteration.
3/5 · Testing Throughout the Software Development Lifecycle
Which statement best distinguishes functional testing from non-functional testing as test types in the ISTQB CTFL syllabus?
AFunctional testing evaluates what the system does (its functions), while non-functional testing evaluates how well the system performs, such as its performance, usability, or reliability.
BFunctional testing is performed manually by testers, while non-functional testing is performed with automated tools, so the two test types differ mainly in how the tests are executed.
CNon-functional testing verifies the internal code structure, such as statements and branches, while functional testing verifies the external behavior of the system only.
DFunctional testing is executed exclusively at the system test level, while non-functional testing is executed exclusively at the acceptance test level by business users and system operators.
Answer: A. Functional test types evaluate the functions the system is expected to perform (what it does), based on functional requirements. Non-functional test types evaluate characteristics such as performance efficiency, usability, reliability, and security (how well it does it). Either can be applied at any test level.
Source: ISTQB CTFL Syllabus v4.0.1 — Testing Throughout the Software Development Lifecycle
4/5 · Testing Throughout the Software Development Lifecycle
Which of the following is NOT typically listed in the ISTQB CTFL syllabus as a trigger for maintenance testing?
AMigration of the system to a different hardware or software platform.
BA corrective emergency change (hotfix) applied to a live production system.
CInitial development and first release of a brand-new system that has never previously been deployed to production.
DRetirement or decommissioning of a system, including testing related to data archiving and migration of retained data.
Answer: C. The syllabus lists modification (planned enhancement, corrective or emergency change, or changes of environment such as OS/DB upgrades), migration, and retirement of a system as triggers for maintenance testing. These all presuppose an existing, already-deployed system; the first release of a brand-new system is not maintenance testing.
Source: ISTQB CTFL Syllabus v4.0.1 — Testing Throughout the Software Development Lifecycle
5/5 · Testing Throughout the Software Development Lifecycle
Before a new payroll system goes live, the operations team runs tests covering backup and restore procedures, disaster recovery, and installation on production-equivalent infrastructure under expected load — without re-verifying payroll calculation business rules already covered at earlier levels. Which acceptance test type does this scenario best illustrate?
AOperational acceptance testing
BContractual and regulatory acceptance testing
CAlpha testing
DUser acceptance testing
Other CTFL v4.0 areas
The same kind of free sample for every other section of the CTFL v4.0 bank:
Practise CTFL v4.0 with instant feedback
6 free questions in study mode · no card · full CTFL v4.0 bank with area filters and the error log: $15 one-time · no dumps, no ads.
Start CTFL v4.0 free →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by ISTQB. CTFL v4.0 and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official ISTQB materials (as of October 2026); always confirm current details with the vendor before booking.