AWS - API Gateway
For an API with unpredictable traffic spikes, which throttling configuration best ensures backend stability while minimizing user impact?
For an API with unpredictable traffic spikes, which throttling configuration best ensures backend stability while minimizing user impact?
hard📝 Application Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Understand traffic pattern
Unpredictable spikes require flexibility to handle bursts without rejecting requests immediately.Step 2: Evaluate options
Moderate rateLimit with higher burstLimit allows absorbing spikes while protecting backend.Step 3: Exclude other options
Equal rate and burst limits are too rigid; disabling throttling risks overload; very low limits cause excessive throttling.Final Answer:
Set a moderate rateLimit with a higher burstLimit to absorb sudden spikes -> Option CQuick Check:
Use burstLimit > rateLimit for spike tolerance [OK]
Quick Trick: Use burstLimit higher than rateLimit for spikes [OK]
Common Mistakes:
MISTAKES- Setting burstLimit equal to rateLimit, limiting flexibility
- Disabling throttling and risking backend overload
- Setting limits too low causing unnecessary throttling
Master "API Gateway" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes