An API Gateway throttling rule is not working as expected. You set rateLimit=150 but still see throttling at 100 requests per second. What should you check?

medium📝 Debug Q7 of 15

AWS - API Gateway

AIf the backend service is down

BIf a usage plan or API key has a lower throttling limit

CIf the API Gateway is in a different region

DIf the client IP is blocked

Step-by-Step Solution

Solution:

Step 1: Understand throttling layers
API Gateway throttling can be overridden by usage plans or API keys with lower limits.
Step 2: Verify usage plan limits
Check if usage plan or API key throttling is set below 150, causing earlier throttling.
Final Answer:
If a usage plan or API key has a lower throttling limit -> Option B
Quick Check:
Usage plan limits override API Gateway = A [OK]

Quick Trick: Check usage plan limits if throttling is unexpected [OK]

Common Mistakes:

Ignoring usage plan throttling
Assuming backend issues cause throttling
Confusing region or IP blocking with throttling

Master "API Gateway" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

An API Gateway throttling rule is not working as expected. You set rateLimit=150 but still see throttling at 100 requests per second. What should you check?

Step 1: Understand throttling layers

Step 2: Verify usage plan limits

Final Answer:

Quick Check:

Want More Practice?