Salesforce-MuleSoft-Platform-Architect Practice Test
Salesforce Spring 25 Release 152 Questions
A Rate Limiting policy is applied to an API implementation to protect the back-end system. Recently, there have been surges in demand that cause some API client
POST requests to the API implementation to be rejected with policy-related errors, causing delays and complications to the API clients.
How should the API policies that are applied to the API implementation be changed to reduce the frequency of errors returned to API clients, while still protecting the back-end
system?
A. Keep the Rate Limiting policy and add 9 Client ID Enforcement policy
B. Remove the Rate Limiting policy and add an HTTP Caching policy
C. Remove the Rate Limiting policy and add a Spike Control policy
D. Keep the Rate Limiting policy and add an SLA-based Spike Control policy
C. Remove the Rate Limiting policy and add a Spike Control policy
Explanation:
The Rate Limiting policy enforces a hard cap on requests per time window, immediately rejecting any excess with 429 errors. In contrast, the Spike Control policy protects the backend by queuing excess requests (up to a configured limit) and retrying them within the same window. This “buffering” approach smooths out sudden surges—allowing legitimate traffic to flow to the backend—while still guarding against overload. Thus, replacing Rate Limiting with Spike Control will reduce client-side rejections during demand spikes while preserving backend protection.