CTAL-TAE v2.0 sample exams

Official sample questions and answer explanations

Use the question file before opening the answers. These downloads belong to ISTQB and remain on its official site. The walkthrough below is our preparation guidance. The sample-file revision can differ from the syllabus version.

• ISTQB CTAL-TAE Sample Exam Questions v2.4 (PDF)
• ISTQB CTAL-TAE Sample Exam Answers v2.4 (PDF)

One question-and-answer pair is linked here. Once you have studied its explanations, later repeats are useful revision but no longer an unseen test of readiness.

The CTAL-TAE sample exam and the current exam format

Questions	Total points	Pass mark	Standard duration
40	66	43 points	90 minutes

The pass mark is a points threshold, not a simple count of correct answers. Follow the question and answer instructions for selection rules and scoring. Use a sample’s own point allocation to mark that file. Do not silently replace it with the current live-exam total.

Additional time requires the provider’s approval under the applicable rules. Use your confirmed duration for realistic timing practice. A sample is an illustration of the style and objectives, not a guarantee of the questions you will receive.

Use the sample in three passes

1. First attempt: hide the answer file, follow the sample instructions and work without notes. Record your confidence as well as your selected answer. If you use a timer, note unanswered questions and time pressure.
2. Diagnosis: read the official explanations, identify the objective behind each wrong or guessed response, and explain why each rejected alternative does not fit. Keep calculation or scenario-reading mistakes separate from knowledge gaps.
3. Targeted practice: return to the relevant syllabus section, create a changed example and attempt it later. Reuse the original sample only after the learning gap has been addressed.

For a first timed attempt, distribute your time across the paper and leave a deliberate review margin. If a scenario stalls you, record it for later review and continue. The useful skill is recognizing the relevant constraints and showing correct reasoning, not solving every question in the same number of seconds.

Review what the result actually tells you

Record	Why it matters
First-attempt points	Shows how you handled this sample before seeing its answers.
Wrong and guessed objectives	Identifies what to study next, even where a guess gained points.
Time or reading mistakes	Shows whether the problem was knowledge, execution or an overlooked constraint.
Repeat score	Shows revision progress. It is affected by familiarity with the answers.

For each difficult item, write a one-sentence explanation of the decisive constraint, then a short reason each tempting alternative fails. If you cannot do that without reading the answer again, the objective needs more work.

Practice beyond the official sample

Independent practice prompt, not an ISTQB exam question: An automated checkout suite intermittently fails when a shared account already contains a saved basket. The team proposes retrying every failed test three times so the pipeline passes more often. What evidence would you collect, and what would you change first?

Suggested reasoning

Compare the starting account state and test execution order across passing and failing runs. Check whether tests share mutable data and whether cleanup actually restores the required state. A controlled run with independent accounts can help isolate the cause. Improve isolation or state management when the evidence supports it, while retaining useful logs. Retries can hide symptoms. A higher pass rate alone does not demonstrate more trustworthy feedback.

Try a fresh version: Now the account state is correct, but a third-party service occasionally times out. Reconsider dependency handling, diagnostic logging and which checks belong in which environment rather than applying the same fix automatically.

This exercise has no official point allocation. Judge it by the assumptions you identify, the evidence you use and the explanation of your choice. Use the official objective list to decide which further examples you need.

• Avoid treating a favorite framework as the answer to every architecture problem.
• Avoid improving runtime while overlooking unreliable results or diagnostic evidence.
• Avoid confusing a product defect with a test, data or environment failure.
• Avoid studying the old 2016 automation syllabus as the complete v2.0 scope.

Next steps

Use the syllabus guide to identify missing objectives and the study plan to schedule repairs. Check eligibility, booking options and source-linked exam facts in the overview. Fees belong in the country guides.