ISTQB CT-PT Exam Practice Test Instant Access

Question 1

Why is it important to specify how failures are handled during test execution?

ATo meet the expectations of the business stakeholders

BTo ensure that new failures are not introduced

CTo ensure all defects are captured

DTo minimize distractions during 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.

Question 2

Which of the following is the best description of spike testing?

AIt focuses on the ability of the system to handle loads that are gradually increased to reach the expected maximum.

BIt focuses on the ability of the system to handle loads that are at or beyond the expected peak load.

CIt focuses on the ability of the system to meet future efficiency requirements.

DIt focuses on the ability of the system to respond to quick and extreme changes in load.

Answer : D

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.

Question 3

Which of the following is a key reason to include ramp-up and ramp-down periods in a performance test?

ATo ensure virtual users complete their transactions within a defined time window

BTo simulate a more realistic user load pattern and avoid sudden system stress

CTo provide a buffer for slow-performing transactions to complete

DTo guarantee that all virtual users remain active throughout the test duration

Answer : B

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.

Question 4

Which of the following is considered a common web service protocol?

ASOAK

BREST

CHTTP

DRTE

Answer : B

REST (Representational State Transfer) is a widely used web service protocol that enables client-server communication over HTTP. It is commonly used in modern APIs and web applications for performance testing.

Option A (SOAK) refers to soak testing, which evaluates performance over an extended period.

Option C (HTTP) is a transport protocol, but REST is the actual web service architecture built on HTTP.

Option D (RTE) is not a web service protocol but may refer to Real-Time Enterprise systems.

Question 5

What is the primary purpose of a load generator?

ACreate a steady and consistent background load on the system

BSimulate user behavior in accordance with the defined operational profile

CRecord and analyze the behavior of the system as it is executing the prescribed tests

DSupport root cause analysis when performance degradation is encountered

Answer : B

A load generator is responsible for simulating virtual users and applying workloads to a system as defined by an operational profile. This allows testers to analyze how the system behaves under different load conditions.

Option A (Background load) is incorrect because load generators create simulated user interactions, not just background noise.

Option C (Record and analyze behavior) is the role of monitoring tools, not a load generator.

Option D (Support root cause analysis) is incorrect because root cause analysis is done after the load test, using monitoring tools.

Question 6

Which of the following is a major contributor to unreliable performance projections?

ARedundancy between the test and production environments

BDisagreement between the technical and business stakeholders during analysis

CDifferences in the hardware between the test and production environments

DBusiness stakeholders setting unrealistic performance goals

Answer : C

One of the biggest contributors to unreliable performance projections is differences between the test and production environments. If test environments do not match CPU, memory, network configurations, and database setups in production, the results may not be representative of real-world performance.

Option A (Redundancy between test and production environments) is not a problem; it's actually beneficial for reliability.

Option B (Disagreement between stakeholders) can affect planning but does not cause unreliable projections.

Option D (Unrealistic stakeholder goals) affects expectations but not the accuracy of projections.

Question 7

During performance testing, in addition to the transaction response time, which of the following is needed to accurately reflect the total time to complete a transaction?

AThink time

BWait time

CAction time

DUser time

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.

ISTQB Certified Tester - Performance Testing CT-PT Exam Practice Test