Question 760
A public REST endpoint is vulnerable to credential stuffing due to unlimited attempts. Which acceptance-test observation confirms the required control?
Explanation
Correct Answer
Request throttling reduces automated abuse and resource exhaustion. The outcome directly confirms the requirement: a scripted excessive request burst is throttled while normal client use continues.
Incorrect Answers
The proposed evidence relates to another situation: A business exposes legacy APIs but cannot prevent unauthorized methods or parameter values. API validation should enforce intended contracts before backend execution. The architect needs verification that a scripted excessive request burst is throttled while normal client use continues.
This observation evaluates An API requires different partner subscriptions to have independent usage quotas. Per-consumer API policies prevent cross-client resource exhaustion. It does not establish the required result: a scripted excessive request burst is throttled while normal client use continues.
It verifies another security outcome rather than the current risk: An application uses HTTP APIs to issue payment transfers without recording idempotency keys. API security includes protection against unintended transaction replay. Here the expected evidence is a scripted excessive request burst is throttled while normal client use continues.