ISTQB ISTQB Certified Tester - Performance Testing CT-PT Exam Dumps: Updated Questions & Answers (October 2025)

When system resources (e.g.,CPU, RAM, I/O) are oversaturated, the system becomes overloaded, leading toincreased response timesandpoor application performance.

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

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

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

Stress testingis designed to evaluate how a system behavesunder extreme conditions, often exceeding its design limitations. The goal is to identify bottlenecks, memory leaks, and failures that occurbeyond normal operating conditions.

Option A is incorrectbecause it refers toresilience testing, which focuses on recovery rather than stress beyond limits.

Option B is incorrectas it describesload testing, which measures performance under expected loads.

Option C is incorrectsincedetermining the maximum transactionsis a feature ofcapacity testing, not stress testing.

Protocol-level scriptsmeasure theactual response times of network requests, making them ideal foranalyzing network latency, bandwidth issues, and server response times.

Option A (GUI scripts)measure user interactions, not network timing.

Option B (API scripts)measure API interactions but do not providedetailed network response time analysis.

Option C (HTTP scripts)measure web requests but lack low-level network insights.

Load testingassesses a system’s ability to handlegradually increasing levels of loadand ensures that it meets performance expectationsunder normal and peak conditions.

Option B (Elevation testing)is incorrect because this term does not exist in ISTQB performance testing terminology.

Option C (Spike testing)focuses onsuddenincreases in load rather thangradualscaling.

Option D (Endurance testing)examines how a system performsover an extended period, rather thangradual load increases.

Akey risk in distributed systemsisunreliable remote servers, which can lead tolatency, timeouts, and failuresin performance testing.

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

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

Option D (Bluetooth connectivity)is unrelated todistributed system performance.

To ensure anaccurate operational profile, it is crucial tovalidate and adjust it with key stakeholders before executing tests. This step ensures that the workloadrealistically represents actual user behavior.

Option A (Executing the test first and adjusting later)is incorrect becauseadjustments should be made before executionto avoid misleading results.

Option C (Aggregating profiles into a single generic profile)removesimportant distinctions between different user types, reducing test accuracy.

Option D (Creating separate profiles and using equal proportions)does not match the actualpower purchaserbehavior, which requires arealistic representation of their higher-volume transactions.

Forsafety-critical software, performance goalsmust be identified as early as the requirements phase. This ensures thatperformance constraints are well understood and accounted for throughout development.

Option A (After test readiness but before system testing)istoo late, as requirements should be definedbefore coding begins.

Option C (During the concept stage)istoo early, as details may not be concrete.

Option D (During software design)is useful butshould be preceded by a proper definition during the requirements phase.

ODBC (Open Database Connectivity)is astandard database protocolthat enables applications toconnect to and interact with databasesregardless of vendor specifications.

Option B (JUNIT)is aunit testing framework, not a database protocol.

Option C (SMP - Symmetric Multiprocessing)relates toCPU architecture, not databases.

Option D (MMS - Multimedia Messaging Service)is related tomobile messaging, not database communication.

Performance testsprimarily identifyresource bottleneckssuch asCPU saturation, memory leaks, network congestion, and database slowdowns.

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

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

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

Resource allocation happens during the test planning phase, wherehardware, tools, and personnelare assigned to the project. This ensures that performance tests areadequately supported.

Option B (Test execution)is when resources are actually used, not allocated.

Option C (Test evaluation)happensafter executionto analyze results.

Option D (Test completion)focuses on documentation and reporting.