HomeCTFL v4.0Practice questionsTesting Throughout the Software Development Lifecycle
CTFL v4.0 · ISTQB · Testing Throughout the Software Development Lifecycle · Bank updated 2026-07-03

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.

Start 6 free in study mode → All CTFL v4.0 sample questions
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 the change to production first, then running exploratory tests to see whether anything broke.
BAutomated component and API-level tests run in the CI pipeline immediately after each commit, giving developers fast feedback before the change is merged to the main branch.
CWaiting until a nightly build to run any automated tests because immediate feedback would slow down developers.
DRunning only manual system tests once per release cycle, shortly before deployment.
Show answer & explanation
B is correct. DevOps combines development and operations with an emphasis on continuous, automated feedback loops. Running automated tests as soon as code is committed—rather than waiting for a later stage—is a direct application of shift-left within a CI/CD pipeline, catching defects when they are cheapest to fix.
↗ ISTQB CTFL Syllabus v4.0.1 — Testing Throughout the Software Development Lifecycle
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 defects found in the previous iteration.
CTo formally sign off on acceptance test results before releasing the software to production.
DTo re-execute all regression tests one final time immediately before the retrospective meeting.
Show answer & explanation
A is correct. Retrospectives (common in iterative/Agile lifecycles) give the whole team an opportunity to reflect on the completed iteration, identifying successes and improvement opportunities across testing, development, and collaboration practices, which feeds continuous process improvement.
↗ ISTQB CTFL Syllabus v4.0.1 — Testing Throughout the Software Development Lifecycle
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 can only be performed manually, while non-functional testing can only be automated.
CNon-functional testing verifies the internal code structure, while functional testing verifies external behavior only.
DFunctional testing is executed exclusively at the system test level, while non-functional testing is executed exclusively at the acceptance test level.
Show answer & explanation
A is correct. 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.
↗ 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.
Show answer & explanation
C is correct. 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.
↗ 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
Show answer & explanation
A is correct. The syllabus describes operational acceptance testing as the acceptance test type focused on operational aspects — backup/restore, disaster recovery, installability, and non-functional characteristics — usually run by operations or IT staff before a system goes live, distinct from user, contractual/regulatory, alpha, or beta acceptance testing.
↗ the ISTQB Certified Tester Foundation Level (CTFL) Syllabus v4.0 — Testing Throughout the Software Development Lifecycle
Practise all 23 Testing Throughout the Software Development Lifecycle questions - start free → See the whole CTFL v4.0 bank

Other CTFL v4.0 areas

The same kind of free sample for every other section of the CTFL v4.0 bank:

Fundamentals of Testing29 qStatic Testing16 qTest Analysis and Design36 qManaging the Test Activities29 qTest Tools12 q

Study Testing Throughout the Software Development Lifecycle with instant feedback

6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.

Create your free account →
Read next
CTFL (ISTQB) Study Plan: 4 Weeks to Pass Without a Bootcamp ISTQB CTFL: 40 questions, 60 minutes, 26 to pass, no course required. A four-week self-study plan sized to the syllabus hours. Verified 14 Sep 2026.
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 September 2026); always confirm current details with the vendor before booking.