ISTQB CT-PT Dumps Questions Answers

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.

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 (e.g.,CPU, RAM, I/O) are oversaturated, the system becomes overloaded, leading toincreased response timesandpoor application performance.

Option A (Gradual improvement of response time)is incorrect becauseperformance degrades under heavy load.

Option C (Error logging decreases)is unlikely; in most cases, errorsincreasewhen systems reach their limits.

Option D (Database size decreases)is unrelated to performance saturation.