Practise the standard verbs for configuring API rate limit quotas reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ a per-client rate limit quota on the public API, rather than one shared cap that any single client can actually exhaust.'
We 'set a quota' — the standard, simple collocation for configuring per-client API rate limits. The other options are less idiomatic here.
2 / 5
Fill in: 'A shared quota across all API keys can ___ one noisy client throttling every other tenant that's actually behaving well.'
We say a shared quota will 'leave' well-behaved tenants throttled — the standard, natural collocation for the resulting unfairness. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ quota limits clearly in the API documentation, rather than a 429 error nobody can actually explain to a confused developer.'
We 'document limits' — the standard, simple collocation for publishing rate limit rules for API consumers. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every quota tier against actual usage patterns before rollout, rather than picking a number nobody's actually validated.'
We 'test a tier' — the standard, simple collocation for validating a rate limit setting against real usage. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ 429 response rates per client continuously, rather than learning about an over-tight quota only from an angry support ticket.'
We 'monitor rates' — the standard, simple collocation for watching throttling behavior over time. The other options aren't idiomatic here.