Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Which of the following is a key challenge when testing applications in a cloud environment?
One of the biggest challenges of cloud-based performance testing is the lack of control over test execution timing due to shared cloud resources. Cloud environments dynamically allocate computing power, meaning that test execution may vary due to background processes, VM migrations, or auto-scaling events.
Option B (Inability to generate load) is incorrect because cloud platforms can scale up resources to generate high loads.
Option C (Lack of behavior simulation tools) is incorrect because cloud providers offer robust testing tools.
Option D (Test execution speed being too high) is not a valid performance testing challenge.
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.
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.
At what point during performance testing does monitoring with the load testing tool begin?
Performance monitoring must begin simultaneously with test execution to capture system behavior in real-time. This ensures that bottlenecks and performance issues are identified immediately.
Option A (After testing is concluded) is incorrect because historical monitoring does not help in real-time analysis.
Option B (Before execution) is incorrect because monitoring needs active system load to measure performance.
Option C (Immediately after execution) is incorrect because it misses runtime metrics.
Which of the following is a key reason to include ramp-up and ramp-down periods in a performance test?
A ramp-up period in a performance test gradually increases load over time, and a ramp-down period does the opposite. This prevents sudden surges in system load, making test results more realistic.
Option A (Ensuring transactions complete in a time window) is incorrect because ramp-up/down periods do not control transaction timing.
Option C (Providing a buffer for slow transactions) is incorrect because ramp-up/down is about load balancing, not transaction timing.
Option D (Keeping all virtual users active throughout the test) is incorrect because ramp-down periods reduce users gradually.
40 questions covering all exam domains, starting from $20
Exam domains verified against: Official ISTQB CT-PT exam guide, last checked September 2026.
Covers principles and types of performance testing, load generation concepts, and common failure modes. You'll learn to distinguish between different performance testing approaches and understand what causes performance issues in real systems.
Focuses on collecting, aggregating and interpreting performance metrics from various sources. You'll understand what metrics matter, how to combine results from multiple test runs, and what a typical performance test report looks like.
Sample question from this domain above: Q2
Examines how performance testing activities integrate across development phases and different system architectures. You'll learn to identify performance risks early and plan testing that fits each project stage.
The most practical domain covering planning, design, implementation, execution and analysis. You'll work through real scenarios designing load profiles, building test scripts, running tests and reporting results to stakeholders.
Addresses how tools support performance testing and how to choose the right tool for your project. You'll understand tool capabilities and limitations rather than memorize specific product features.
Common questions about the exam itself
