Bird
0
0

Given this HTTP response header:

medium📝 Predict Output Q4 of 15
Rest API - Rate Limiting and Throttling

Given this HTTP response header:

HTTP/1.1 429 Too Many Requests
Retry-After: 30

What should the client do?

ARetry immediately
BWait 30 seconds before retrying
CIgnore the Retry-After header
DSend a new request with a different method
Step-by-Step Solution
Solution:

  1. Step 1: Analyze the HTTP status and Retry-After header

    Status 429 means too many requests; Retry-After: 30 means wait 30 seconds before retrying.

  2. Step 2: Determine correct client behavior

    The client should wait 30 seconds before sending another request to avoid being blocked.

  3. Final Answer:

    Wait 30 seconds before retrying -> Option B

  4. Quick Check:

    429 + Retry-After = wait specified seconds [OK]
Quick Trick: 429 responses usually require waiting Retry-After seconds [OK]
Common Mistakes:
  • Retrying immediately ignoring Retry-After
  • Ignoring Retry-After header
  • Changing HTTP method unnecessarily

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Rest API Quizzes
Authentication and Authorization - API key authentication - Quiz 4medium Authentication and Authorization - Authorization code flow - Quiz 2easy Error Handling - Rate limit error responses - Quiz 7medium Pagination Patterns - Offset-based pagination - Quiz 12easy Pagination Patterns - Page-based pagination - Quiz 8hard Pagination Patterns - Cursor-based pagination - Quiz 1easy Pagination Patterns - Keyset pagination for performance - Quiz 12easy Rate Limiting and Throttling - Token bucket algorithm - Quiz 2easy Rate Limiting and Throttling - Fixed window algorithm - Quiz 1easy Versioning Strategies - Query parameter versioning - Quiz 12easy