If the calculated bucket in the rate-limiting code exceeds the rate, what happens?

If the calculated bucket in the rate-limiting code exceeds the rate, what happens?

• A. Bucket is capped at the rate
• B. Bucket is reset to zero
• C. Callback is invoked immediately
• D. An error is raised

Answer: (A)

In token-bucket style rate limiting, the bucket holds tokens that represent how many requests you can make immediately. Tokens accumulate over time at a fixed rate, but the bucket has a maximum capacity. If the calculation would push the bucket past that capacity, you clamp it to the maximum. So when the computed bucket value would exceed the rate, you set the bucket to the rate and continue from there. This keeps the burst within the allowed limit and prevents an overflow of tokens. No error is raised and no automatic callback occurs just because of the overflow—the bucket is simply capped.

In token-bucket style rate limiting, the bucket holds tokens that represent how many requests you can make immediately. Tokens accumulate over time at a fixed rate, but the bucket has a maximum capacity. If the calculation would push the bucket past that capacity, you clamp it to the maximum. So when the computed bucket value would exceed the rate, you set the bucket to the rate and continue from there. This keeps the burst within the allowed limit and prevents an overflow of tokens. No error is raised and no automatic callback occurs just because of the overflow—the bucket is simply capped.