Practise the standard verbs for throttling API usage across tiered pricing plans.
0 / 5 completed
1 / 5
Fill in: 'We ___ a request quota per pricing tier so a free-tier caller can't consume the same capacity as a paying enterprise customer.'
We 'assign a quota' — the standard, established collocation for allocating a request limit to a plan. The other options aren't the recognised term here.
2 / 5
Fill in: 'Applying the same rate limit to every plan can ___ a free-tier script starving paying customers of shared gateway capacity.'
We say a flat limit will 'leave' paying customers starved — the standard, natural collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the tier's quota at the gateway itself so a caller can't bypass it by hitting the backend service directly.'
We 'enforce a quota' — the standard, established collocation for applying a limit at the point requests enter the system. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ the remaining quota in a response header on every call so a client can back off gracefully before actually hitting the limit.'
We 'surface' a value — the standard, simple collocation for exposing internal state to a caller. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ tier limits quarterly against real usage data, so a plan that was generous at launch doesn't become a bottleneck as usage grows.'
We 'review' limits — the standard, simple collocation for periodically reassessing a configured value. The other options are less idiomatic here.