What regulates API request traffic by limiting the number of messages processed by an API and ensures that the number of messages processed within a specified time, regardless of client, does not exceed the configured limit?

• A. Spike Control policy
• B. Rate limiting policy
• C. Quota policy
• D. Throttle policy

Answer: (A)

The idea being tested is controlling how many requests can flow through a single API during a short time so the backend isn’t overwhelmed by a sudden surge. The Spike Control policy is designed precisely for this: it caps the amount of traffic that can pass in a burst and then enforces a steady rate, effectively preventing the API from processing more messages than the configured limit within that time window, no matter which client is sending them. This makes it well-suited to smoothing out spikes and protecting downstream systems from overload.

While other policies also govern traffic, their focus differs. Rate limiting often targets a allowed rate over time (sometimes per client), quotas set a total cap over a period (global or per consumer), and throttle manages concurrency or sustained throughput. The described requirement—restricting the total messages processed in a given window regardless of client—aligns most closely with Spike Control’s burst-aware stabilization of traffic.