Certified Tester Foundation Level (CTFL) v4.0

What to Expect on the CTFL v4.0  Exam

CTFL v4.0 is 40 multiple-choice questions in 60 minutes (75 minutes if you’re sitting it in a non-native language), closed-book, no negative marking, and you need 26 points to pass — that’s 65%. Every question is worth exactly one point, so there’s no partial credit and no reason to leave anything blank. A blank answer and a wrong answer cost you the same.

The question style isn’t uniform difficulty. Roughly a fifth of the exam (8 questions) is straight K1 recall — define a term, name a principle. The bulk, 24 questions, is K2: you’re asked to explain, compare, or classify a short scenario rather than just recite a definition. The remaining 8 are K3 “apply” questions, where you’re handed a short scenario — a requirements snippet, a small state diagram, a set of test conditions — and asked to actually derive something: a test case, a boundary value, a decision table row. Those K3 questions are concentrated almost entirely in chapters 4 and 5, which is also why those two chapters matter more than their raw question count suggests.

Pacing works out to about 90 seconds per question on average, but that average hides the  pattern: K1/K2 questions go fast, K3 questions eat your time budget because you have to work through the scenario before you can even see the answer choices clearly.

Domain Breakdown

Chapters 4 and 5 together make up exactly half the exam. If you only have time to over-prepare two chapters, those are the two.

The Topics Candidates Consistently Underestimate

Chapter 5, specifically. Most self-study plans treat “Managing the Test Activities” as the boring admin chapter — risk registers, estimation, configuration management — and rush it in favor of the more hands-on-feeling test techniques in chapter 4. That’s a mistake: chapter 5 carries 9 questions, nearly as many as chapter 4, and three of them are K3 apply-level, meaning you’ll be asked to actually prioritize test cases or work through a risk-based testing scenario, not just recall what “exit criteria” means.

The difference between equivalence partitioning and boundary value analysis in combined scenarios. Candidates usually learn each technique cleanly in isolation, then get a CTFL question that gives a single input range and asks which values represent both a valid equivalence class member and a boundary value simultaneously. That overlap is where people lose points.

Decision table “don’t care” conditions. The syllabus covers collapsed decision tables, and exam questions sometimes present a table with a dash (don’t care) in one condition column. Candidates who’ve only drilled fully expanded tables misread these.

Static testing’s non-review content. People associate chapter 3 entirely with formal reviews and forget it also covers static analysis tools and what they can and can’t catch (e.g., they find certain defect classes but say nothing about runtime behavior).

Test levels vs. test types, chapter 2. This sounds basic but is a recurring trap: a question describes testing activity (e.g., checking a login screen against usability heuristics) and asks you to classify it by test type, not test level, and candidates who are pattern-matching on keywords rather than reading carefully pick the test level instead.

How to Use Practice Tests Effectively for CTFL v4.0  Exam

Because a third of the  exam is K2/K3 scenario-based rather than definitional recall, a practice test that only quizzes you on definitions (“What is a test oracle?”) is training you for a quarter of what you’ll actually face. Prioritize practice material that mirrors the scenario format — a short paragraph or table followed by “which of the following is correct” — especially for chapters 4 and 5.

Run practice sets under the  60-minute constraint at least twice before your actual exam date. The time pressure changes how you read K3 questions; doing untimed practice lets you get comfortable with concepts but won’t expose whether you can derive a boundary value fast enough under a ticking clock.

Track your wrong answers by chapter, not just as a raw score. A 75% overall score can hide a chapter 4 score of 50% if your chapter 1 and 2 scores are near-perfect — and chapter 4 is the one chapter you can’t afford to be weak on.

Common Mistakes That Cause Retakes

• Treating the exam as pure memorization and skipping technique practice — you can recite the definition of boundary value analysis and still fail to apply it correctly to a given input range.

• Running out of time on chapter 4/5 scenario questions because recall questions elsewhere were answered too slowly.

• Confusing verification and validation, or test basis and test oracle — these term pairs are deliberately close and show up as distractors.

• Skipping chapter 6 entirely because it’s “only 2 questions.” Those 2 points have cost people a 26/40 pass mark before.

• Not reading the full question stem before looking at answer options, especially on K3 items where the scenario detail changes which answer is correct.

CTFL v4.0  Study Timeline by Starting Experience Level

New to software testing: Budget 4–6 weeks. The official syllabus recommends a minimum of 18 hours 55 minutes of instruction, but that’s a training-course floor, not a self-study ceiling — plan for closer to 30–35 hours of combined reading, note-taking, and practice questions if you have no prior testing exposure.

Working QA/test role, no formal certification: 2–3 weeks is usually . You already have the vocabulary and the test-level concepts from chapters 1–2 intuitively; your  work is chapters 4 and 5, where the syllabus’s formal technique names (and their K3 application) may not match how you’ve been doing it informally on the job.

Retaking after a fail: Don’t just redo the same study materials. Get your chapter-by-chapter breakdown from your first attempt’s score report if your exam provider gives one, and concentrate almost entirely on whichever of chapter 4 or 5 pulled your score down — a focused 1-week push on the weak chapter, combined with full timed practice runs, is usually enough for a second attempt.

What Changes Most Often on CTFL v4.0  Exam

The move from the 2018 syllabus to v4.0 (mandatory since May 2024) restructured several chapters and added explicit K3 estimation and prioritization learning objectives to chapter 5 that didn’t carry apply-level weight before. Since then, the governing document has only seen an errata release (v4.0.1, correcting wording and minor learning-objective references) rather than a structural change — so the chapter weightings and question counts above have been stable since the v4.0 rollout. Don’t assume that stability is permanent, though: ISTQB has historically revised Foundation Level every several years, and v3.1 candidates found their syllabus sunset entirely once v4.0 became mandatory, with no extended grace period for the old version Start your EC-Council Certified Incident Handler (ECIH) exam practice today.