Practise the standard verbs for configuring nginx rate limiting zones.
0 / 5 completed
1 / 5
Fill in: 'We ___ a limit_req_zone keyed on client IP so no single caller can flood the upstream with excessive requests.'
We 'define a zone' — the standard, established nginx collocation for declaring a shared memory rate-limit zone. The other options aren't the recognised term here.
2 / 5
Fill in: 'Sizing the shared memory zone too small can ___ nginx evicting rate-limit counters early and letting bursts through.'
We say a small zone will 'cause' early eviction — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a burst allowance on the limit so a brief legitimate spike isn't rejected the instant it crosses the average rate.'
We 'allow' a burst — the standard, established nginx collocation for permitting short traffic spikes above the base rate. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ requests that exceed the zone's limit with a 429 status instead of silently dropping the connection.'
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 ___ rejected-request counts per zone in the access log so we can tell a real attack from an overly strict limit.'
We 'track' counts — the standard collocation for monitoring a metric over time. The other options aren't idiomatic here.