Free Preparation Discussions
MENU
ISTQB CT-PT Exam Questions
- Topic 1: Types of Performance Testing: This section of the exam measures the skills of Software Test Analysts and covers various approaches such as load, stress, scalability, spike, endurance, concurrency, and capacity testing. It explains how each type evaluates system behavior under different conditions, helping testers and stakeholders understand how the system handles both expected and extreme usage scenarios.
- Topic 2: Testing Types in Performance Testing: This section of the exam introduces the distinction between static and dynamic performance testing. It shows how reviews of requirements, architecture, and code can identify risks before coding is complete, and how runtime checks of resource utilization and response times reveal issues that only appear when the system is in operation.
- Topic 3: The Concept of Load Generation: This section of the exam measures the skills of Software Test Analysts and discusses how representative loads are modeled and produced to simulate user or process behavior. It explores methods such as user interface inputs, crowdsourcing, API-based calls, or protocol capture and playback, emphasizing the need for repeatable loads that accurately reflect real-world conditions.
- Topic 4: Common Failures in Performance Testing and Their Causes: This section of the exam measures the skills of Performance Engineers and outlines frequent failure modes, including slow responses at various load levels, degraded performance over time, and system crashes under peak conditions. It provides examples of underlying causes such as resource leaks, insufficient capacity, and poor handling of spikes or concurrency, illustrating why robust planning and monitoring are crucial for reliable performance.
Free ISTQB CT-PT Exam Actual Questions
Note: Premium Questions for CT-PT were last updated On Feb. 27, 2026 (see below)
You are managing the testing efforts of an existing distributed system that manages inventories of automobile and light truck tires from multiple warehouses across the country. The system is being enhanced to track incoming restocking shipments at the point of entry to the warehouse and outbound sales shipments at the point of shipment from the warehouse, all of which are executed in real-time. System loads traditionally peak on Mondays due to built-up demand from the previous weekend.
You are preparing a presentation to the business stakeholders, outlining your performance testing strategy.
Which of the following is appropriate to present to this audience?
Business stakeholders are most concerned with risks that affect deployment and production stability. The primary risk in performance testing is that the test environment may differ from production, leading to misleading test results.
Option A (HTTP response goals) is too technical for a business stakeholder audience.
Option B (Hardware specifications) is relevant for technical teams, not business stakeholders.
Option C (Support staff details) is a logistical aspect, not a key performance testing risk for business decision-makers.
Which of the following is considered a common database protocol?
ODBC (Open Database Connectivity) is a standard database protocol that enables applications to connect to and interact with databases regardless of vendor specifications.
Option B (JUNIT) is a unit testing framework, not a database protocol.
Option C (SMP - Symmetric Multiprocessing) relates to CPU architecture, not databases.
Option D (MMS - Multimedia Messaging Service) is related to mobile messaging, not database communication.
Which of the following is considered a common database protocol?
ODBC (Open Database Connectivity) is a standard database protocol that enables applications to connect to and interact with databases regardless of vendor specifications.
Option B (JUNIT) is a unit testing framework, not a database protocol.
Option C (SMP - Symmetric Multiprocessing) relates to CPU architecture, not databases.
Option D (MMS - Multimedia Messaging Service) is related to mobile messaging, not database communication.
Which of the following is the best description of spike testing?
Spike testing is a type of performance testing that evaluates how a system responds to sudden, extreme increases or decreases in load. It is designed to simulate unexpected surges in user activity or workload, such as flash sales, viral events, or cyberattacks.
Option A (Gradual load increase testing) describes load testing, not spike testing.
Option B (Handling expected peak load) describes stress testing, which pushes the system to or beyond its limits but does not focus on sudden changes.
Option C (Meeting future efficiency requirements) relates to capacity planning rather than spike testing.
Spike testing helps to identify system bottlenecks, resource allocation issues, and performance degradation when traffic surges unexpectedly.
You have run a load test. When examining the metrics, you see that the virtual users experienced many timeouts and excessive wait times. The system throughput metrics exceeded expected results, even during peak times.
Based on your analysis, what conclusion should you draw?
If timeouts and excessive wait times occur, but throughput is high, this suggests that the system is unable to process requests fast enough. This points to slow processing speed due to CPU bottlenecks, memory limitations, or inefficient database queries.
Option A (Network infrastructure investigation) would be relevant if throughput was low or variable.
Option C (Impatient virtual users) is irrelevant; virtual users follow scripted behaviors.
Option D (New test data) does not address the core issue.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Laurel
2 days agoLeota
14 days agoHaley
21 days agoArthur
28 days agoRosenda
1 month agoNichelle
1 month agoMabel
2 months agoFrederick
2 months agoSteffanie
2 months agoBrigette
2 months agoGenevive
3 months agoBettye
3 months agoMaybelle
3 months agoLennie
4 months agoEdda
4 months agoLigia
4 months agoCorinne
4 months agoHerman
5 months agoJacqueline
5 months agoAlesia
5 months agoPage
5 months agoDelmy
6 months agoLatrice
6 months agoJesusa
6 months agoRobt
6 months agoMelissa
8 months agoIvory
9 months agoRicki
10 months agoDolores
11 months agoQuentin
12 months agoChauncey
1 year agoDong
1 year ago