GraphQL Rate Limiting Cost Analysis Language Collocations
Practise the standard verbs for costing and rate limiting GraphQL queries.
0 / 5 completed
1 / 5
Fill in: 'We ___ a cost score to every field in the schema so a deeply nested query can't slip past a naive request-count limit.'
We 'assign a cost' — the standard, established GraphQL collocation for weighting fields by their execution expense. The other options aren't the recognised term here.
2 / 5
Fill in: 'Rate limiting only by request count can ___ a single expensive query costing far more than a hundred cheap ones combined.'
We say naive limiting will 'allow' a costly query through — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the total query cost against a per-client budget before execution so an oversized request is rejected up front.'
We 'check' a cost — the standard, simple collocation for validating a computed value against a limit. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a maximum query cost in the gateway config so no single request can consume an outsized share of backend capacity.'
We 'set a maximum' — the standard, simple collocation for configuring an upper bound. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ rejected high-cost queries in a dedicated log so we can tell a real abuse pattern from a genuinely complex report.'
We 'log' a rejection — the standard, simple collocation for recording an event for later inspection. The other options are less idiomatic here.