Rest API - HTTP Status Codes
An API server returns 429 Too Many Requests with a Retry-After header set to 10 seconds. Your client uses a fixed 5-second retry delay ignoring this header. What is the likely consequence?
An API server returns 429 Too Many Requests with a Retry-After header set to 10 seconds. Your client uses a fixed 5-second retry delay ignoring this header. What is the likely consequence?
hard📝 Application Q9 of 15
Step-by-Step Solution
Solution:
Step 1: Compare client retry delay with server Retry-After
Client retries too early (5s) before server allows (10s).Step 2: Understand server response to early retries
Server will respond again with 429, causing repeated failures and wasted retries.Final Answer:
Client will likely receive repeated 429 responses causing inefficient retries -> Option BQuick Check:
Ignoring Retry-After causes repeated 429 responses [OK]
Quick Trick: Always respect Retry-After to avoid repeated 429 errors [OK]
Common Mistakes:
- Assuming server adjusts Retry-After automatically
- Thinking early retry succeeds
- Believing client stops after one 429
Master "HTTP Status Codes" in Rest API
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Rest API Quizzes