ISTQB CT-PT Dumps Questions Answers

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.

Spike testingis a type of performance testing that evaluates how a systemresponds to sudden, extreme increases or decreases in load. It is designed to simulateunexpected surges in user activity or workload, such as flash sales, viral events, or cyberattacks.

Option A (Gradual load increase testing)describesload testing, not spike testing.

Option B (Handling expected peak load)describesstress testing, which pushes the system to or beyond its limits but does not focus on sudden changes.

Option C (Meeting future efficiency requirements)relates tocapacity planningrather than spike testing.

Spike testing helps toidentify system bottlenecks, resource allocation issues, and performance degradationwhen traffic surges unexpectedly.

Iftimeouts and excessive wait times occur, butthroughput is high, this suggests thatthe system is unable to process requests fast enough. This points toslow processing speeddue toCPU bottlenecks, memory limitations, or inefficient database queries.

Option A (Network infrastructure investigation)would be relevant if throughput wasloworvariable.

Option C (Impatient virtual users)is irrelevant; virtual users followscripted behaviors.

Option D (New test data)does not address the core issue.