Question 410
The cloud operations team reviews the following risk: A public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources. What governance practice would best prevent the same failure?
Explanation
Correct Answer
This guardrail addresses apim throttling policy for abuse: The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. The prevention measure is: Reassess API throttling limits and correlation identifiers following traffic-pattern changes. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Review client certificate trust and renewal processes for all privileged API consumers” would address that alternative cause, not the condition in this question: the API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.
“Test negative token cases after identity provider and APIM policy changes” responds to this separate finding: aPI Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. This question instead needs “Reassess API throttling limits and correlation identifiers following traffic-pattern changes”, so the alternative does not meet the stated condition.
The API or product does not require the intended APIM subscription key or equivalent authentication control. “Review APIM API and product access configuration when introducing new routes” applies to that separate problem. The observed case is a public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources; choosing this alternative would address the wrong failure mode.