REST (Representational State Transfer) is a widely used web service protocol that enables client-server communication over HTTP. It is commonly used in modern APIs and web applications for performance testing.
Option A (SOAK) refers to soak testing, which evaluates performance over an extended period.
Option C (HTTP) is a transport protocol, but REST is the actual web service architecture built on HTTP.
Option D (RTE) is not a web service protocol but may refer to Real-Time Enterprise systems.

When system resources (e.g., CPU, RAM, I/O) are oversaturated, the system becomes overloaded, leading to increased response times and poor application performance.
Option A (Gradual improvement of response time) is incorrect because performance degrades under heavy load.
Option C (Error logging decreases) is unlikely; in most cases, errors increase when systems reach their limits.
Option D (Database size decreases) is unrelated to performance saturation.

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.

Spike testing is a type of performance testing that evaluates how a system responds to sudden, extreme increases or decreases in load. It is designed to simulate unexpected surges in user activity or workload, such as flash sales, viral events, or cyberattacks.
Option A (Gradual load increase testing) describes load testing, not spike testing.
Option B (Handling expected peak load) describes stress testing, which pushes the system to or beyond its limits but does not focus on sudden changes.
Option C (Meeting future efficiency requirements) relates to capacity planning rather than spike testing.
Spike testing helps to identify system bottlenecks, resource allocation issues, and performance degradation when traffic surges unexpectedly.

ODBC (Open Database Connectivity) is a standard database protocol that enables applications to connect to and interact with databases regardless of vendor specifications.
Option B (JUNIT) is a unit testing framework, not a database protocol.
Option C (SMP - Symmetric Multiprocessing) relates to CPU architecture, not databases.
Option D (MMS - Multimedia Messaging Service) is related to mobile messaging, not database communication.