Practise the standard verbs for building a Redis rate limiter correctly.
0 / 5 completed
1 / 5
Fill in: 'We ___ a sliding-window counter in Redis so bursty traffic still gets throttled fairly across the whole window.'
We 'implement a counter' — the standard, simple collocation for building a rate-limiting mechanism. The other options are less idiomatic here.
2 / 5
Fill in: 'A fixed-window counter reset on the clock boundary can ___ double the intended rate through right at the edge.'
We say a fixed window will 'allow' a burst through — the standard, natural collocation for the resulting edge-case flaw. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a TTL on each rate-limit key so old counters expire automatically instead of accumulating in Redis forever.'
We 'set a TTL' — the standard, established Redis collocation for configuring a key's expiry. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a client's request the moment their counter exceeds the configured limit, returning a 429 immediately.'
We 'reject a request' — the standard, simple collocation for refusing an over-limit call. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the limiter's atomic increment as a Lua script so a race between concurrent requests can never undercount.'
We 'run a script' — the standard, simple collocation for executing a piece of Redis-side logic. The other options are less idiomatic here.