ISTQB CT-PT Practice Test - Questions Answers

Resource allocation happens during the test planning phase, where hardware, tools, and personnel are assigned to the project. This ensures that performance tests are adequately supported.

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

Option C (Test evaluation) happens after execution to analyze results.

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

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.

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).

Load testing assesses a system's ability to handle gradually increasing levels of load and ensures that it meets performance expectations under 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 on sudden increases in load rather than gradual scaling.

Option D (Endurance testing) examines how a system performs over an extended period, rather than gradual load increases.

A static performance test is a non-execution-based review that analyzes system architecture, network configurations, and other elements that affect 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.

Crowd-based load generation involves using distributed users (e.g., cloud-based testers or real users). The main challenge is that the load generation can be difficult to reproduce consistently due to variations in network conditions, device types, and user behavior.

Option B is incorrect because load generation methods should adapt to system changes.

Option C is incorrect since mainframe applications typically do not rely on crowd-based testing.

Option D is incorrect because crowd-sourced load testing is generally less precise than scripted load testing.