CTFL v4.0 · ISTQB · Updated September 2026
CTFL v4.0 practice questions
Original & expert-reviewed · explanation for every option · no dumps
Practise CTFL v4.0 with original, expert-reviewed questions — each with an explanation for every option, linked to the source, across the full exam blueprint. No dumps, no ads, 6 free to start.
Free: 6 questions in study mode, no card. Full CTFL v4.0 bank with mock exams and the error log: $15 one-time, or every exam with All-Access for $19/mo or $119/yr.
What makes these different from dumps
📚 An explanation for every option
Not just the right answer — why each wrong option is wrong, linked to the source. Wrong answers teach the most.
⏱️ Real-format timed mocks
Sit full 40-question, 60-minute exams and get a readiness report by area — know when you're ready.
↻ Spaced-repetition error log
Every miss comes back on a 1 → 3 → 7 → 16-day schedule, so the fixes actually stick.
🔖 Original & reviewed
Every question is written to test the concepts and reviewed before it ships — never copied or leaked “dumps”.
Try 10 real CTFL v4.0 questions — free, no sign-up
A representative slice of the bank: every syllabus chapters, mixed difficulty (hard ones included). Answers are one tap away — no email wall.
1/10 · Fundamentals of Testing
According to the ISTQB CTFL Syllabus, which of the following is a typical objective of testing during the software development lifecycle?
ATo provide information for decision-making, especially regarding the quality of the test object
BTo prove that the software contains no defects whatsoever before it is released to its users
CTo replace debugging, so that developers no longer need to locate and fix the causes of failures
DTo eliminate the need for static testing techniques such as reviews and static analysis of code
Show answer & explanation
A is correct. ISTQB CTFL v4.0 lists several objectives of testing, including finding defects, gaining confidence about quality levels, preventing defects, and providing information for decision-making. It explicitly warns against the fallacy that testing can prove the absence of defects.
↗ ISTQB CTFL Syllabus v4.0.1 — Fundamentals of Testing
2/10 · Testing Throughout the Software Development Lifecycle
Which statement correctly contrasts testing in a sequential development model (e.g., V-model) with testing in an iterative development model (e.g., Scrum)?
AIn a sequential model, regression testing is not needed because each development phase is fully validated and signed off by the stakeholders before the next phase begins.
BIn an iterative model, all test levels are deferred until the last iteration is finished, so that testing is concentrated at the very end of the whole project, just before the release.
CAn iterative model prohibits formal test levels such as system and acceptance testing and relies on component testing alone within each iteration, leaving system behavior to the users.
DIn a sequential model, each test level is typically performed once, after its development phase; in an iterative model, the same test levels may be repeated in each iteration.
Show answer & explanation
D is correct. The CTFL syllabus notes that in sequential (linear/V-shaped) models, test levels are typically each performed once, tied to a corresponding development phase. In iterative models, test levels may be repeated as the system grows with each iteration, and testing activities are integrated throughout rather than concentrated at the end.
↗ ISTQB CTFL Syllabus v4.0.1 — Testing Throughout the Software Development Lifecycle
3/10 · Static Testing
Which statement best describes a key characteristic of static testing that distinguishes it from dynamic testing?
AStatic testing is performed only after dynamic testing has finished, as a final confirmation that no defects remain.
BStatic testing produces the same defect-detection results as dynamic testing, so a well-run project only needs one of the two.
CStatic testing can only be performed using fully automated tools, with no manual human review activity involved.
DStatic testing examines a work product without executing it, so it can be applied even to work products that are not yet executable, such as requirements documents or models.
Show answer & explanation
D is correct. Static testing evaluates a work product by examination rather than execution, allowing it to be applied to non-executable artifacts (requirements, designs, models) as well as code. This lets defects be found earlier and more cheaply than dynamic testing, which requires running the software. The two approaches are complementary, not redundant.
↗ ISTQB CTFL Syllabus v4.0.1 — Static Testing
4/10 · Test Analysis and Design
What is the primary purpose of equivalence partitioning as a black-box test design technique?
ATo divide inputs or outputs into partitions whose values are expected to be processed the same way, so one value per partition is tested, reducing the test cases.
BTo combine multiple logical conditions and their resulting actions in a tabular format, so that each combination of conditions is covered by at least one test case.
CTo model the states a system can be in and the events that cause transitions between them, so that valid and invalid transitions can be covered by tests.
DTo identify the boundaries between valid and invalid inputs and test the minimum and maximum values of each range, since defects are more likely to occur at these edges.
Show answer & explanation
A is correct. Equivalence partitioning reduces the number of test cases needed by grouping inputs/outputs into partitions that the system is expected to treat identically, then testing one representative value per partition. Boundary value analysis, state transition testing, and decision table testing are separate black-box techniques with different focuses.
↗ ISTQB CTFL Syllabus v4.0.1 — Test Analysis and Design
5/10 · Managing the Test Activities
According to the ISTQB CTFL syllabus, what is the primary purpose of a test plan?
ATo record the defects found during test execution, with their severity and status, so that each one can be tracked to closure.
BTo document the detailed steps, test data, and expected results for each test case, so that different testers can execute them consistently in each run.
CTo describe the test objectives and the approach for meeting them within the constraints of the context, such as budget, schedule, and resources.
DTo provide a live dashboard showing the pass/fail status of automated tests as they run, so stakeholders can follow test progress during execution.
Show answer & explanation
C is correct. A test plan documents the test objectives and the approach chosen to achieve them, taking into account the context, constraints, and risks of the project. It is created and updated before and during test planning, distinct from test case specifications, defect reports, or monitoring dashboards.
↗ ISTQB CTFL Syllabus v4.0.1 — Managing the Test Activities
6/10 · Test Tools
Which of the following BEST describes the primary purpose of a static analysis tool within tool-supported testing?
ATo simulate the runtime behavior of components that are not yet available, e.g. by providing stubs and drivers, so that integration testing of the other components can proceed.
BTo detect defects in code or models by analyzing their structure or content without executing the code, e.g. checking against coding standards or calculating metrics.
CTo execute predefined test cases automatically and compare the actual results against the expected results, e.g. in regression test runs after each code change.
DTo manage test cases, test data, and traceability links between requirements and tests throughout the project, e.g. to report test progress and requirements coverage.
Show answer & explanation
B is correct. The CTFL v4.0 syllabus classifies static analysis tools under tools that support static testing: they examine code or models without executing them, helping find defects early (shift-left) by checking coding standards, complexity, and structural properties. This is distinct from tools that support dynamic test execution or test management.
↗ ISTQB CTFL Syllabus v4.0.1 — Test Tools
7/10 · Fundamentals of Testing
A test run on a newly implemented feature results in a failure. Which statement correctly distinguishes the subsequent activity of debugging from testing, per the ISTQB CTFL Syllabus?
ADebugging and testing are the same activity, only the name changes depending on the project phase
BDebugging is the development activity that finds, analyzes, and removes the cause of a failure, while testing shows that failures occur and provides quality information
CDebugging is the dynamic execution of software to reveal failures, while testing is the analysis performed to find the failure's root cause
DDebugging always precedes testing, since defects must be found by developers before test cases can be written
Show answer & explanation
B is correct. ISTQB CTFL v4.0 clearly separates testing (executing software to find failures and provide information) from debugging (a development activity to locate, analyze, and remove the defect causing a failure). Confirmation testing is later performed by testers to verify the fix worked.
↗ ISTQB CTFL Syllabus v4.0.1 — Fundamentals of Testing
8/10 · Testing Throughout the Software Development Lifecycle
What is the primary goal of the 'shift-left' approach to testing, as described in the ISTQB CTFL syllabus?
ATo replace manual testers with automated regression suites that are executed immediately before release, so that the lifecycle no longer needs manual test activities.
BTo move testing and test-related activities as early as possible in the software development lifecycle, so that defects are detected and can be fixed sooner and more cheaply.
CTo relocate the testing team so that it sits physically to the left of the development team in the office, shortening the path between testers and developers when failures are reported.
DTo postpone test design activities until the code is fully complete, so that test cases are written once against the final build and are not reworked when requirements change.
Show answer & explanation
9/10 · Fundamentals of Testing · hard
A company decides that the same developers who wrote a module will also be the only people who test it, with no other tester or reviewer involved at any stage. Which drawback of this particular degree of test independence is most directly highlighted by the ISTQB CTFL Syllabus?
AThis approach violates the whole-team approach, because developers cannot participate in testing at all under that approach
BIndependent testers external to the organization always find more usability defects than developers do
CThis is the highest level of test independence, so no drawback exists
DDevelopers testing their own code may exhibit author bias and overlook their own mistakes, reducing the likelihood of finding certain defects
Show answer & explanation
D is correct. The syllabus describes several degrees of test independence, from no independent testers (developers test their own code) up to testers external to the organization. A key drawback of the lowest degree is author bias — being blind to one's own errors — while a benefit is fast feedback without handover delay.
↗ ISTQB CTFL Syllabus v4.0.1 — Fundamentals of Testing
10/10 · Fundamentals of Testing · hard
On a project, one person is responsible for reporting test progress and risks to stakeholders, adapting the test plan, and choosing test approaches and metrics, while another person analyzes, designs, implements, and executes tests and reports on results and observed problems. Per the two generic roles defined in the ISTQB CTFL v4.0 Syllabus, these responsibilities belong respectively to:
AQuality assurance manager and Developer
BTest analyst and Test architect
CTest manager and Tester
DProduct owner and Scrum master
Show answer & explanation
C is correct. ISTQB CTFL v4.0 simplified test roles to two generic ones: the test manager, who owns test leadership and management activities, and the tester, who performs analysis, design, implementation, execution, and results reporting; these activities may be distributed across various team members in practice.
↗ ISTQB CTFL Syllabus v4.0.1 — Fundamentals of Testing
Practice by knowledge area
Five more free questions for each section of the CTFL v4.0 bank, drawn from that area only, with the answer explained and linked to the source:
Covering every syllabus chapters
The bank spans the whole CTFL v4.0 blueprint, weighted toward what the exam tests most:
Start practising CTFL v4.0 free
6 free questions in study mode · no card · full CTFL v4.0 bank: $15 one-time · no dumps, no ads.
Start CTFL v4.0 free →
CTFL v4.0 practice — FAQ
How hard is the CTFL v4.0 exam really?
It is an entry-level exam, but most content sits at K2 (understand) and K3 (apply) rather than pure recall — Test Analysis and Design plus Managing the Test Activities alone carry half the exam. Practising applied questions matters more than memorizing terms.
What changed in CTFL v4.0 vs the older 2018 syllabus?
v4.0 restructured the six chapters, folded test management into 'Managing the Test Activities', and added Agile/DevOps concepts like shift-left, ATDD and collaborative user-story writing. The format — 40 questions, 60 minutes, 65% pass mark — is unchanged.
Is CTFL v4.0 useful for business analysts or developers, not just testers?
Yes — ISTQB explicitly lists project managers, product owners, business analysts and IT managers in the Foundation Level audience. It gives non-testers a working vocabulary of testing.
How many questions is the CTFL v4.0 exam and how long is it?
40 multiple-choice questions worth one point each, no negative marking, in 60 minutes (75 minutes for candidates sitting the exam in a non-native language).
What is the passing score for CTFL v4.0?
The passing score is 65% — 26 out of 40 points. Aim for a consistent 80–85% on realistic practice exams before booking.
What is the CTFL v4.0 pass rate?
ISTQB does not publish official pass rates, so any exact percentage quoted online is unverified. The readiness signal that actually predicts passing: consistently holding 80–85% on realistic, full-length practice exams before you book.
What are the CTFL v4.0 eligibility requirements?
No prerequisites — open to anyone. Aimed at testers, test analysts and developers, but ISTQB explicitly includes project managers, product owners, business analysts and quality managers in the target audience.
How much does CTFL v4.0 cost?
ISTQB does not set a global price - fees are set by the local member board: $229 in the US (AT*SQA, same price online-proctored or at a Kryterion test centre) and £200 in the UK (BCS, including the £35 remote-proctoring fee, VAT added at checkout - about £240 all-in), and much less in some countries (both verified 14 Sep 2026). The certificate is identical regardless of which board you buy from - verify with your local board.
How long should I study for CTFL v4.0?
For most candidates, accredited courses run ~19 hours of instruction; 20–40 hours of self-study is commonly reported. What matters most is practising questions and analysing why each option is right or wrong — not just reading.
Does the CTFL v4.0 certification need recertification?
None — CTFL does not expire and needs no renewal (certificates from any past syllabus stay valid).
Are ExamDeck's CTFL v4.0 questions exam dumps?
No — every question is original, written to test the concepts and reviewed before it ships, with an explanation linked to the source for every option. Dumps are stale, often wrong, and against ISTQB's policies.
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.