[Solved] Given this snippet of server-side pseudocode handling API requests:if request_count > limit: return 429, {"Retry-After": "30"}, "Too many requests" else:... | Rest API

Rest API - HTTP Status Codes

Given this snippet of server-side pseudocode handling API requests:

if request_count > limit:
    return 429, {"Retry-After": "30"}, "Too many requests"
else:
    process_request()

What is a likely bug if clients keep getting 429 responses even after waiting 30 seconds?

AThe server is processing requests without any limit.

BThe <code>Retry-After</code> header is missing from the response.

CThe server is not checking <code>request_count</code> at all.

DThe server does not reset <code>request_count</code> after the wait period.

Step-by-Step Solution

Solution:

Step 1: Understand rate limiting logic
The server limits requests by counting them and returning 429 if over limit.
Step 2: Identify why 429 repeats after wait
If request_count never resets, the server always thinks limit is exceeded.
Step 3: Confirm bug cause
Not resetting request_count after wait causes repeated 429 responses.
Final Answer:
The server does not reset request_count after the wait period. -> Option D
Quick Check:
Persistent 429 means counter not reset [OK]

Quick Trick: Reset request count after wait to avoid repeated 429 [OK]

Common Mistakes:

Master "HTTP Status Codes" in Rest API

9 interactive learning modes - each teaches the same concept differently

More Rest API Quizzes

Given this snippet of server-side pseudocode handling API requests: