ISTQB Certified Tester - Performance Testing CT-PT Exam Questions

Answer : B

Wait time is the period a transaction spends waiting for resources, database responses, or external services before completing. It is critical for understanding real-world transaction durations.

Option A (Think time) refers to user delays, not system delays.

Option C (Action time) focuses on execution time only.

Option D (User time) is not a standard performance metric.

Answer : A

For batch processing performance metrics, the two most important factors are:

Throughput -- Measures the number of transactions processed over time.

Wait times -- Evaluates delays in processing batches.

Option B (Number of records deleted) is irrelevant unless batch processing specifically involves deletions.

Option C (Network latency percentage) applies to real-time transaction processing, not batch jobs.

Option D (Concurrent virtual users) applies more to load testing rather than batch performance.

Answer : A

Performance tests primarily identify resource bottlenecks such as CPU saturation, memory leaks, network congestion, and database slowdowns.

Option B (Suitability issues) is a functional requirement concern, not a performance issue.

Option C (Learnability concerns) relates to usability testing, not performance.

Option D (Accessibility requirements) falls under compliance and usability testing, not performance testing.

Answer : B

During performance testing, it is crucial to define failure handling procedures to ensure that failures do not introduce additional errors into the test execution process. This helps maintain test accuracy and avoid misleading results.

Option A (Meeting stakeholder expectations) is important but not the primary reason for defining failure handling.

Option C (Capturing all defects) is a general testing principle, not specific to failure handling in performance tests.

Option D (Minimizing distractions) is not a valid reason for defining failure handling.

Answer : A

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.

Answer : C

A load management console is a tool that helps testers analyze and visualize test results, providing performance reports, graphs, and insights. This aids in understanding bottlenecks, response times, and throughput trends.

Option A (Simulating user behavior) is incorrect; load generators handle simulation.

Option B (Senior management monitoring) is not the primary role of a test console.

Option D (Emulating virtual users) is incorrect; that is the job of load injectors.

Answer : D

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.