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

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.

REST (Representational State Transfer)is a widely usedweb service protocolthat enablesclient-server communicationover HTTP. It is commonly used inmodern APIs and web applicationsfor performance testing.

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

Option C (HTTP)is atransport protocol, butRESTis the actual web service architecture built on HTTP.

Option D (RTE)isnot a web service protocolbut may refer toReal-Time Enterprise systems.

When system resources areoversaturated(e.g., CPU, RAM, or network bandwidth),responsetimes will degradebecause the systemstruggles to process requests efficiently. This is akey performance bottleneck indicator.

Option A is incorrectbecause response times do not improve under heavy load; they typically worsen.

Option C is incorrectbecauseerror logging may actually increaserather than decrease under stress.

Option D is incorrectbecause database size is independent of system saturation unless records are actively purged.

Acloud-based environmentis themost cost-effectivesolution for performance testing. It offersscalability, pay-per-use models, and flexibility, allowing testers to simulate large workloadswithout expensive infrastructure investments.

Option A (Isolated lab environment)is costly due tohardware maintenance and infrastructure costs.

Option C (Mainframe environment)isexpensive and impracticalfor performance testing.

Option D (No environment)is not a viable option.

One of the biggest challenges of cloud-based performance testing is the lack of control over test execution timing due to shared cloud resources. Cloud environments dynamically allocate computing power, meaning that test execution may vary due to background processes, VM migrations, or auto-scaling events.

Option B (Inability to generate load) is incorrect because cloud platforms can scale upresources to generate high loads.

Option C (Lack of behavior simulation tools) is incorrect because cloud providers offer robust testing tools.

Option D (Test execution speed being too high) is not a valid performance testing challenge.

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.

Performance monitoring toolscollectreal-time and historicalperformance data, particularly fromserver logs, application metrics, and infrastructure monitoring. This allows testers to analyze performance trends efficiently.

Option A is incorrectbecause monitoring toolsdo not preventmalicious behavior but may detect it.

Option C is incorrectsinceidentifying multi-threading issuesis typically done throughprofiling toolsrather than performance monitors.

Option D is incorrectasDoS attack detectionfalls undersecurity testing.

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.

Nested transactionsallow performance tests to capture bothindividualandaggregatedelements bygrouping multiple related transactionsand measuring their cumulative impact.

Option A (Aggregated metrics)provides summaries but lacks insight into individual elements.

Option B (Process optimization tracking)focuses onbusiness process improvement, not test metrics.

Option C (Measuring underlying transactions)focuses only onindividualtransactions.