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

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.

Astatic performance testis anon-execution-based reviewthat analyzes system architecture, network configurations, and other elements thataffect system performance before execution.

Option A (Usability test)is not a static performance test but rather a functional or UX evaluation.

Option B (Evaluation of testers' skills)is unrelated to performance testing.

Option D (Formal signature approval)is an administrative task and not a static test.

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.

Aload management consoleis a tool that helps testersanalyze and visualize test results, providingperformance reports, graphs, and insights. This aids in understandingbottlenecks, response times, and throughput trends.

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

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

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

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.

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.

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.

Performance monitoring mustbegin simultaneously with test executiontocapture system behavior in real-time. This ensures thatbottlenecks and performance issues are identified immediately.

Option A (After testing is concluded)is incorrect becausehistorical monitoring does not help in real-time analysis.

Option B (Before execution)is incorrect because monitoring needsactive system loadto measure performance.

Option C (Immediately after execution)is incorrect because itmisses runtime metrics.

One of thebiggest contributors to unreliable performance projectionsisdifferences between the test and production environments. If test environments do not matchCPU, memory, network configurations, and database setupsin production, the results may not berepresentative of real-world performance.

Option A (Redundancy between test and production environments)isnot 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 butnot the accuracy of projections.