Exam guide

How to pass ISTQB Foundation on your first attempt

Real strategy for the people who keep getting close but missing — what to watch for, how to budget time, and the terminology traps the exam loves to set.

The ISTQB.app team·~9 min read

Terminology traps the exam loves

Most failures aren't conceptual — they're terminology. ISTQB writes options that are 95% correct with one wrong word. Memorize the right side of each row below.

Validation vs Verification
WrongTreating them as synonymsRightVerification = "Did we build it right?" (matches specs). Validation = "Did we build the right thing?" (meets user needs). If an answer says "validation of requirements" or "verification of user needs" — it's wrong.
Static testing finds defects, not failures
WrongSaying a "failure" was found during a reviewRightStatic testing (reviews, static analysis) finds defects in work products. Failures only happen during dynamic execution. If an answer mentions "failure" during static analysis — it's wrong.
Error → Defect → Failure
WrongMixing up the causal chainRightA person makes an error (mistake) → which creates a defect (bug in code/docs) → which may cause a failure (wrong behavior at runtime). The exam loves testing this sequence.
White-box ≠ requirements
WrongSaying white-box tests derive from requirementsRightWhite-box testing derives from code structure (statements, branches). Black-box derives from requirements and specs. If an answer links white-box to requirements — it's wrong.
Absence-of-defects fallacy
WrongThinking "no bugs = good software"RightFinding and fixing all defects does NOT guarantee the software meets user needs. A bug-free product that solves the wrong problem is still a failure. This is one of the seven testing principles.
Testing quadrants are a communication tool
WrongSaying quadrants "ensure comprehensive test coverage"RightAgile testing quadrants help stakeholders understand different types of testing. They don't guarantee or ensure coverage — they're a classification and communication framework.

Six strategy moves

Tactics from people who've passed. None of these are clever; all of them are easy to forget under time pressure.

Skip hard questions, come back later

Every question is worth 1 point. A wall-of-text scenario question is worth the same as a quick recall question. If you need more than 90 seconds, flag it and move on. Come back with fresh eyes after you've banked the easy points.

Watch for one wrong word

ISTQB loves answers that are 95% correct with one word that invalidates them. An option might perfectly describe a concept but swap "verification" for "validation" or say "failure" instead of "defect." Read every word in the answer, not just the gist.

"MOST accurate" and "BEST describes"

When a question asks for the MOST accurate or BEST answer, multiple options may be partially correct. Don't pick the first one that seems right — read all four. The correct answer is the one that's most precisely aligned with ISTQB terminology.

K3 questions need a method, not intuition

Application-level (K3) questions on equivalence partitioning, boundary values, decision tables, and state transitions require you to follow the technique step by step. Don't rely on "common sense" — follow the formal ISTQB method even if you'd do it differently in practice.

The syllabus is always right (even when it isn't)

Your 10 years of testing experience may disagree with an answer. On this exam, the ISTQB syllabus is the source of truth. If the syllabus says reviews need specific roles, that's the correct answer — even if your team does it differently.

Eliminate obviously wrong answers first

Most questions have 1-2 options that are clearly wrong if you know the terminology. Cross those out, then compare the remaining 2. You just went from a 25% guess to a coin flip, and usually the right answer is obvious once the noise is gone.

On exam day

Six things to remember the morning of:

  • 1Arrive 15 minutes early. Getting flustered before the exam costs you points.
  • 2Read the question stem twice before looking at the options.
  • 3Budget 90 seconds per question. That leaves 10+ minutes for flagged questions.
  • 4If two answers seem equally correct, pick the one that uses official ISTQB glossary terms.
  • 5Don't change answers unless you find a clear reason. Your first instinct is usually right.
  • 6The pass mark is 65% (26/40). You can get 14 questions wrong and still pass. Don't panic.

Ready to start?

Try Chapter Quizzes and 5 AI tutor messages free. No credit card.

Start practicing free