CT-PT Exam Dumps : ISTQB Certified Tester - Performance Testing

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.

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.

To ensure anaccurate operational profile, it is crucial tovalidate and adjust it with key stakeholders before executing tests. This step ensures that the workloadrealistically represents actual user behavior.

Option A (Executing the test first and adjusting later)is incorrect becauseadjustments should be made before executionto avoid misleading results.

Option C (Aggregating profiles into a single generic profile)removesimportant distinctions between different user types, reducing test accuracy.

Option D (Creating separate profiles and using equal proportions)does not match the actualpower purchaserbehavior, which requires arealistic representation of their higher-volume transactions.