CT-PT ISTQB Certified Tester - Performance Testing Questions and Answers

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 .

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.

Test implementation is the stage where smaller test components are created and assembled into larger test scenarios . This phase includes scripting, test data preparation, and configuring load profiles .

Option A (Test completion) involves analyzing results, not building tests.

Option B (Test planning) focuses on strategies and objectives , not test creation.

Option C (Test design) defines test scenarios and cases , but the actual building happens in implementation .

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 .

When system resources (e.g., CPU, RAM, I/O ) are oversaturated, the system becomes overloaded, leading to increased response times and poor application performance .

Option A (Gradual improvement of response time) is incorrect because performance degrades under heavy load .

Option C (Error logging decreases) is unlikely; in most cases, errors increase when systems reach their limits.

Option D (Database size decreases) is unrelated to performance saturation.

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 .

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.

Performance testing is time-sensitive and must be designed to fit within the constraints of the project timeline. If performance tests take too long to execute, they may not be feasible within a given sprint or development cycle. The results should be reproducible, meaning the same test on an unchanged system should yield the same results ( making option C incorrect ). While stakeholder expectations are important, performance tests should be objective and based on defined benchmarks rather than subjective expectations ( making option D incorrect ).

A key risk in distributed systems is unreliable remote servers , which can lead to latency, timeouts, and failures in performance testing.

Option A (Hard disk de-fragmentation) is not a significant risk in distributed systems.

Option B (Excess memory) is a positive factor , not a risk.

Option D (Bluetooth connectivity) is unrelated to distributed system performance .