Practice Free CT-PT ISTQB Certified Tester - Performance Testing Exam Questions Answers With Explanation

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.

Before running the next set of performance tests, it is crucial tounderstand the differences (delta) between the previous test results and the expected improvements. This ensures that:

The changes made by developers are properly validated.

Performance objectives are aligned with measurable improvements.

Option B (Adjust stakeholder expectations)is incorrect, as performance testing should focus on real data rather than adjusting expectations.

Option C and D (Realign objectives for milestones or time-to-market goals)are incorrect becausetest objectives should focus on technical accuracy rather than schedule constraints.

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.

Forbatch 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 toreal-time transaction processing, not batch jobs.

Option D (Concurrent virtual users)applies more toload testingrather than batch performance.

Wait timeis the period a transaction spendswaiting for resources, database responses, or external servicesbefore completing. It is critical for understandingreal-world transaction durations.

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

Option C (Action time)focuses onexecution time only.

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

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.

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.