BETAPlatform actively being built — new topics and features added regularly.

ISTQB Foundation Level (CTFL 4.0.1)~11 min read26/26

Practice Question Lab

// ctfl-style multiple choice questions from all 6 chapters with full explanations.

loading...
// content

Reading about testing builds knowledge — practice questions build exam skill

The CTFL exam tests not just what you know but how quickly and accurately you can apply it under time pressure. Many candidates study thoroughly and still fail because they have not practised the specific cognitive task the exam demands: reading a scenario, identifying what is being asked, eliminating distractors, and selecting the most correct answer — in under 90 seconds per question.

This section provides structured practice using exam-style questions that mirror the CTFL 4.0.1 format, difficulty, and distractor patterns. Work through them systematically. Review every explanation, including the correct answer — understanding why a wrong option is wrong is as important as knowing the right answer.

// example: studies on certification exam preparation consistently show that candidates who practise with exam-style questions outperform those who only read study materials — even when the reading group spent more total hours studying. the key variable is active recall under constraint. the ctfl exam has 40 questions and 60 minutes: 90 seconds per question. at that pace, spending 3 minutes on one difficult question forces you to guess on two easier ones. the candidates who pass reliably have practised enough to recognise question types quickly, apply the elimination strategy confidently, and move on without second-guessing. that pattern only develops through deliberate timed practice — not through rereading notes.

Studies on certification exam preparation consistently show that candidates who practise with exam-style questions outperform those who only read study materials — even when the reading group spent more total hours studying. The key variable is active recall under constraint. The CTFL exam has 40 questions and 60 minutes: 90 seconds per question. At that pace, spending 3 minutes on one difficult question forces you to guess on two easier ones. The candidates who pass reliably have practised enough to recognise question types quickly, apply the elimination strategy confidently, and move on without second-guessing. That pattern only develops through deliberate timed practice — not through rereading notes.

CTFL 4.0.1 exam structure and strategy

Exam facts

FactorDetail
Number of questions40 multiple-choice questions
Time allowed60 minutes (75 minutes for non-native speakers)
Pass mark65% — 26 out of 40 correct
Question formatSingle best answer from four options (A, B, C, D)
Bloom's levelsK1 (remember), K2 (understand), K3 (apply)
Negative markingNone — always answer all 40 questions

Chapter weighting (approximate)

ChapterTopicApproximate questions
Chapter 1Fundamentals of Testing8
Chapter 2Testing Throughout SDLC6
Chapter 3Static Testing4
Chapter 4Test Techniques12
Chapter 5Managing Test Activities8
Chapter 6Tool Support2

Chapter 4 (Test Techniques) carries the most weight — 30% of the exam. Prioritise EP, BVA, decision tables, state transitions, and white-box techniques in your revision.

// note:

Common distractor patterns — how the exam tricks candidates

The CTFL exam uses specific distractor patterns that appear across many questions. Recognising them saves time and prevents avoidable errors.

Pattern 1: True but irrelevant

An option is factually correct but does not answer the specific question asked. The question asks "what is the PRIMARY purpose of X?" and the distractor states a secondary benefit of X.

Pattern 2: Role reversal

Activities are assigned to the wrong role. "Developers perform system testing" or "testers perform debugging" — both technically possible but contradicting CTFL norms.

Pattern 3: Scope inflation

An answer is correct in a broader context but exceeds what the question specifically describes. A question about component testing gets an answer about system testing.

Pattern 4: Absolute language trap

Options using "always", "never", "all", or "only" are usually wrong. CTFL language is nuanced — testing "should", "typically", "aims to", not "always" or "guarantees".

Pattern 5: Reversed cause and effect

Options swap the relationship between concepts. "Defects cause errors" is the reverse of CTFL's direction: errors cause defects, defects cause failures.

Warning word in an optionLikely incorrect?
"always", "never", "all", "only", "guarantees"Usually — CTFL rarely makes absolute statements
"the same as", "synonymous with"Often — CTFL distinguishes many similar-sounding terms
"replaces", "eliminates the need for"Usually — testing and automation never fully replace each other

CTFL 4.0.1 — Full Practice Exam

// 40 questions · 60 minutes · 65% to pass · all 6 chapters

40

Questions

60 min

Time limit

65%

Pass mark

1 – 6

Chapters

// Question distribution

8

Ch 1

Fundamentals

6

Ch 2

SDLC

4

Ch 3

Static

12

Ch 4

Techniques

8

Ch 5

Management

2

Ch 6

Tools

// Instructions

Select the single best answer for each of the 40 questions

Flag questions to revisit — use the summary tray to navigate

Timer counts down from 60:00 — exam auto-submits at 00:00

Full explanations for every option shown after submission

High-value topics by chapter — where to focus final revision

ChapterMust-know topicsLikely question type
Ch 1Error/defect/failure distinction; 7 testing principles; testing vs debugging; test process stagesDefinition recognition, scenario classification
Ch 2V-model correspondence (which test level matches which dev phase); shift-left; regression vs confirmation; test levels vs test typesLevel identification, SDLC model comparison
Ch 3Static vs dynamic; formal vs informal reviews; inspection roles; static analysis vs reviewClassify the activity, identify the review type
Ch 4EP partition identification; BVA boundary calculation; decision table condition/action counts; state transition coverage criteria; statement vs branch coverageCalculation, partition identification, coverage comparison
Ch 5Risk level = likelihood × impact; PERT formula (O + 4M + P) ÷ 6; entry/exit criteria; configuration item; defect lifecycle statesCalculation, risk classification, criteria identification
Ch 6Tool categories; when to automate; automation ROI; tools support testing but do not replace itCategory classification, automation suitability

Last 24-hour revision checklist

  • ✅ Error → Defect → Failure chain (direction and definitions)
  • ✅ All 7 testing principles (especially principles 2, 3, and 7)
  • ✅ V-model left/right correspondence table
  • ✅ EP: valid, invalid partitions + BVA values for each partition
  • ✅ Decision table: 2^N conditions rule; action rows
  • ✅ State transition: all-states vs all-transitions vs invalid transitions coverage
  • ✅ PERT formula and when to use it
  • ✅ Risk level = likelihood × impact (low likelihood + critical impact = HIGH)
  • ✅ Inspection vs walkthrough (formal vs informal; moderator vs author-led)
  • ✅ Automation: what can and cannot be automated; ROI calculation

// note:

Exam Practice Questions

// ctfl 4.0.1 style — select an answer to reveal explanation

10Q
Q1.Which of the following BEST describes the purpose of testing according to CTFL 4.0.1?
Q2.A system has three input fields. Field A accepts values 1–10, Field B accepts Y or N, Field C accepts values 100–999. Using equivalence partitioning, how many valid partitions exist in total?
Q3.During a sprint review, the team walks through a test plan document. The author explains each section and collects feedback informally. No formal entry/exit criteria are defined. Which review type is this?
Q4.A tester estimates a task optimistically at 3 days, pessimistically at 15 days, and most likely at 6 days. What is the PERT estimate?
Q5.A test automation suite passes all 800 tests after a release. A critical defect is reported by a customer the following day. What does this MOST likely indicate?
Q6.A risk has LOW likelihood but CRITICAL impact. According to CTFL's risk-based approach, how should this risk be treated?
Q7.Which statement about the V-model is TRUE?
Q8.A team measures that 72 out of 90 branches in their code are exercised by the test suite. What is the branch coverage and what does it mean?
Q9.Which of the following is a characteristic of exploratory testing according to CTFL 4.0.1?
Q10.A tester has designed test cases based on the requirements specification. Before execution, the requirements document is updated significantly. Which CTFL concept explains why the existing test cases must be reviewed?
// end