The ISTQB CT-PT exam format is 40 multiple-choice questions in 90 minutes, worth one point each, and you pass with 26 points (65%). Half of the questions, 20 of 40, come from a single chapter of the syllabus, Performance Testing Tasks. Non-native speakers get 25% extra time, which brings the exam to 113 minutes.
That one fact about chapter 4 should shape how you study. This entry goes through the format the way ISTQB publishes it: the question count per chapter, the K-level of each question, how long ISTQB expects each type to take, and where candidates tend to drop points. Then it turns those numbers into a five-week plan. Every exam figure here was read on ISTQB's own pages and PDFs on 26 October 2026.
What is the CT-PT exam format, in short?
CT-PT is the ISTQB Certified Tester Performance Testing exam, a Specialist module that sits on top of the Foundation Level. The CT-PT certification page lists the exam structure in four lines, and the rest comes from ISTQB's exam rules.
- Questions: 40, multiple choice. ISTQB's rules define each exam question as multiple choice, where you select the best answer (or answers) according to the syllabus.
- Points: 40 in total, one per question.
- Passing score: 26 points, which is 65%.
- Time: 90 minutes, plus 25% (113 minutes) if the exam is not in your native language.
- Prerequisite: you must hold the Certified Tester Foundation Level (CTFL) certificate.
- Syllabus: version 1.0 of 2018, still the current one on the ISTQB page.
- Fee: ISTQB does not list one. The price is set by the exam provider in your country.
Because every question is worth one point, there is no hard question that counts double. A quick recall question about test types earns the same point as a long scenario about load profiles. That matters for timing, as you will see below.
How are the 40 CT-PT questions split across the five chapters?
ISTQB publishes the exact split in its exam structure tables (v1.19), dated 19 August 2026. The CT-PT sheet gives a fixed number of questions per chapter:
- Chapter 1, Basic Concepts: 6 questions (15%)
- Chapter 2, Performance Measurement Fundamentals: 4 questions (10%)
- Chapter 3, Performance Testing in the Software Lifecycle: 7 questions (17.5%)
- Chapter 4, Performance Testing Tasks: 20 questions (50%)
- Chapter 5, Tools: 3 questions (7.5%)
The CT-PT syllabus (v1.0, 2018) agrees with this weighting in its own way. It sets a minimum training time for each chapter, and chapter 4 gets 475 of the 875 minutes, or 54%. Chapters 1, 2 and 5 together give you 13 questions. Chapter 4 alone gives you 20.
Here is the practical reading. The pass mark is 26. If you score well on chapter 4, say 16 of 20, you need only 10 of the other 20 questions. If you are weak on chapter 4 and get 8 of 20, you need 18 of the remaining 20, which leaves almost no room for error. Chapter 4 decides most results.
What do K1, K2, K3 and K4 mean on the CT-PT exam?
Each ISTQB question is written to a K-level, a cognitive level from the learning objective it tests. The CT-PT table gives this split:
- K1, remember: 2 questions. Recall a term or a fact.
- K2, understand: 25 questions. Explain, compare or classify, for example the difference between load testing and stress testing.
- K3, apply: 4 questions. Use a technique on a small scenario.
- K4, analyze: 9 questions. Read a scenario, pull out what matters, and choose the best plan, profile or conclusion.
So 27 of the 40 questions (K1 and K2) test knowledge and understanding, and 13 (K3 and K4) ask you to apply or analyze. Ten of those 13 harder questions sit in chapter 4. The other three are in chapter 3 (two K4 questions on performance risks and on testing activities across the lifecycle) and chapter 5 (one K4 question on choosing a suitable tool).
A K2 question usually takes one careful read. A K4 question often has a short story, a few numbers and four answers that all sound reasonable. Those are the questions that eat your time.
Is 90 minutes enough for 40 CT-PT questions?
Yes, but only with a plan. ISTQB's table gives a suggested time per question type: 1 minute for K1, 2 for K2, 3 for K3 and 4 for K4. Add them up and you get about 100 minutes:
- K1: 2 questions x 1 minute = 2 minutes
- K2: 25 x 2 = 50 minutes
- K3: 4 x 3 = 12 minutes
- K4: 9 x 4 = 36 minutes
That is 10 minutes more than the 90 you have (non-native speakers, with 113 minutes, have room to spare). The gap is our reading of ISTQB's own figures, and it tells you where to save time. The K1 and K2 questions are where you can move faster. If you answer the 27 knowledge questions in about 45 minutes, you keep about 45 minutes for the 13 scenario questions, which is close to the 48 minutes ISTQB suggests for them.
A simple routine works well. Do a first pass and answer every question you are sure of. Flag the long scenarios and come back to them. Before the timer ends, make sure every question has an answer.
Which chapter 4 topics carry the most CT-PT marks?
Chapter 4 has 13 learning objectives, and the exam table names the number of questions for each. Most of them give one or two questions. The ones to know cold:
- Planning (4.1): deriving performance test objectives and outlining a test plan (one K4 question each), and presenting the rationale behind the plan to stakeholders (two questions).
- Transactions (4.2.2): two questions. The syllabus defines elapsed time as the transaction response time plus the think time.
- Operational and load profiles (4.2.3, 4.2.4): one K4 question each. Operational profiles describe what users do; load profiles describe how many virtual users do it, and when, with ramp-ups, steps and ramp-downs.
- Throughput and concurrency (4.2.5): one K4 question. Know the syllabus formula: system throughput = number of virtual users / (processing time + think time).
- Scripts (4.2.6, 4.2.7): two K2 questions on script structure and two K3 questions on implementing scripts. Correlation and parameterization live here.
- Execution and analysis (4.3, 4.4): two K2 questions on execution and one K4 question on analyzing and reporting results.
The rest of chapter 4, on protocols and on preparing for execution, gives two K2 questions each. Read them, but spend your practice time on the profiles, the throughput formula and the analysis of results.
Where do candidates lose marks on the CT-PT exam?
Most lost points come from a few habits. Each of these is avoidable.
- Studying the chapters by page count instead of by question count. Chapter 3 is long and interesting, but it gives 7 questions. Chapter 4 gives 20.
- Mixing up users and load. The syllabus warns that the number of concurrent users is often used to describe load when throughput should be. Its own example: 500 users running a query every minute make 30,000 queries an hour, while the same 500 users running one query an hour make 500. Same users, a 60x difference in load.
- Forgetting think time. In throughput questions, the think time is part of every pass through the script. Leave it out and every answer is wrong.
- Trusting the average response time. The syllabus says the average can be skewed by outliers, and that the 90th percentile is often used as a goal. It also says requiring 100% compliance with a goal is not recommended.
- Missing what correlation means. The syllabus calls incorrect or missing correlation the main reason recorded scripts fail to play back. If a scenario says a recorded script fails on the second run, think of correlation first.
- Ignoring open and closed systems. In a closed system, new users cannot arrive while all users wait for a response. Many public systems are open: new users keep arriving.
- Reading K4 questions too fast. The best answer usually depends on one detail in the scenario, such as the stated objective or the architecture.
What does a CT-PT analysis question look like?
This is a practice question written for this entry. It is not from any real exam and only shows the style of a chapter 4 throughput question.
A checkout session has three transactions. Each takes 2 seconds of processing, and the user thinks for 8 seconds after each one. A test runs 150 virtual users. Under heavy load, processing time doubles to 4 seconds per transaction. What happens to system throughput?
- A. It stays at 18,000 sessions an hour, because the number of virtual users has not changed.
- B. It falls from 18,000 to 15,000 sessions an hour.
- C. It falls by half, because processing time doubled.
- D. It rises, because the users spend more time waiting.
The answer is B. Before the slowdown, one pass takes 6 seconds of processing plus 24 seconds of think time, 30 seconds in all. 150 users / 30 seconds = 5 sessions a second, or 18,000 an hour. After it, a pass takes 12 + 24 = 36 seconds, so 150 / 36 = about 4.17 a second, or 15,000 an hour. That is about 17% fewer sessions with the same users.
Answer A is the "users equal load" trap. Answer C forgets that think time did not change. This is the kind of reasoning the K4 questions on throughput and on result analysis reward.
How should you plan the five weeks before the CT-PT exam?
Five weeks of about 5 hours each gives you 25 hours, comfortably above the syllabus's minimum training time of 14 hours 35 minutes. Weight the weeks by the question count, not by the page count.
- Week 1: chapters 1 and 2 (10 questions). Types of performance testing, load generation, failure modes, typical metrics and how results are aggregated. Make a one-page glossary of the keywords in each chapter.
- Week 2: chapter 4 planning and profiles. Objectives, test plan, transactions, operational profiles and load profiles. Draw two load profiles by hand from a short description.
- Week 3: chapter 4 throughput, scripts and analysis. Work at least ten throughput sums with think time. Write out the parts of a test script, and what correlation and parameterization fix.
- Week 4: chapters 3 and 5 (10 questions). Performance risks by architecture and across the lifecycle, the testing activities in each phase, and the criteria for choosing a tool.
- Week 5: timed practice. Take ISTQB's official Sample Exam A under a 90-minute timer. Mark it, then trace each mistake back to its learning objective in the syllabus.
When you review, keep the syllabus open. Each learning objective has a code, such as PTFL-4.2.5, and the exam table uses the same codes, so you can see exactly how many questions each part of your review is worth.
Is there a short video on CT-PT exam tips?
Yes. The ProcessExam team has a short video with tips for the ISTQB Performance Testing exam. It is a good review before your timed practice in week 5.
How do you book the CT-PT exam?
ISTQB does not sell the exam itself. Exams are run by member boards and exam providers, and the price depends on the provider and the country. ISTQB's exam provider directory for Performance Testing lists the providers that offer CT-PT. Check that you hold the Foundation Level certificate before you book, because CT-PT requires it.
Frequently asked questions
1. How many questions are on the CT-PT exam?
The CT-PT exam has 40 multiple-choice questions worth one point each, 40 points in total. Twenty of them come from chapter 4, Performance Testing Tasks.
2. What is the CT-PT passing score?
You need 26 of the 40 points, which is 65%.
3. How long is the CT-PT exam?
The exam lasts 90 minutes. Candidates who take it in a language that is not their native language get 25% more time, 113 minutes in all.
4. Do I need the Foundation Level before CT-PT?
Yes. ISTQB states that candidates must hold the Certified Tester Foundation Level certificate to gain the CT-PT certification.
5. Which CT-PT chapter should I study first?
Start with chapters 1 and 2 for the vocabulary, then spend the most time on chapter 4, which carries 20 of the 40 questions and 10 of the 13 apply and analyze questions.