A parking-citation API behind one OCI API Gateway deployment is overwhelmed by a noisy public client. Operators want a simple ceiling that protects every back end on that deployment. Per-partner paid tiers will come later. Which control matches that need?
Select an answer to reveal the explanation.
Short Explanation
Think of the deployment as one front door with a single turnstile—rate limiting on API Gateway spins for the whole door, not one hallway. Use a deployment-wide rate-limiting request policy to shield every back end from a noisy client. Per-customer ceilings belong on a usage plan’s entitlement rate and quota, which is a different object.
Full Explanation
OCI API Gateway rate-limiting request policies apply only to the entire deployment, not to an individual route. That makes them suitable for protecting all back ends behind the deployment from excessive traffic. Per-subscriber rate and quota ceilings are modeled with usage-plan entitlements, which are separate from the deployment-global rate-limiting policy. Do not confuse the two mechanisms.