[Solved] The code snippet:if requests >= limit: reject request else: process request requests += 1 if time_passed >= reset_time: requests = 0What is the likely bug? | Rest API

Rest API - Rate Limiting and Throttling

In a rate limiting system, a developer notices clients are blocked even after waiting the reset time. The code snippet:

if requests >= limit:
  reject request
else:
  process request
requests += 1
if time_passed >= reset_time:
  requests = 0

What is the likely bug?

AThe requests counter resets after increment, causing off-by-one errors.

BThe reset condition is checked after increment, so requests may exceed limit before reset.

CThe limit variable is not defined.

DThe reject request line is inside the else block.

Step-by-Step Solution

Solution:

Step 1: Review order of operations
Requests increment before reset check, so requests can exceed limit before reset.
Step 2: Identify fix
Reset check should happen before increment to avoid blocking after reset time.
Final Answer:
The reset condition is checked after increment, so requests may exceed limit before reset. -> Option B
Quick Check:
Reset after increment causes blocking = B [OK]

Quick Trick: Check reset before incrementing requests to avoid blocking [OK]

Common Mistakes:

MISTAKES

Master "Rate Limiting and Throttling" in Rest API

9 interactive learning modes - each teaches the same concept differently

More Rest API Quizzes

In a rate limiting system, a developer notices clients are blocked even after waiting the reset time. The code snippet: