A citizen mobile API on API Gateway occasionally sees abusive request spikes that drive expensive downstream scale-out. Which control best caps that cost risk?
Select an answer to reveal the explanation.
Short Explanation
A bouncer at the door is cheaper than rebuilding the gym every time a crowd rushes in. API Gateway throttling caps abusive spikes before backends scale into debt.
Full Explanation
API Gateway throttling and usage plans limit request rates so abusive or accidental spikes do not force unlimited backend scale and cost. Removing throttling increases cost risk. SSH to databases and disabling observability do not provide controlled API protection and create security or operational gaps.