GraphQL Query Depth Limiting Language Collocations
Practise the standard verbs for limiting GraphQL query depth and complexity.
0 / 5 completed
1 / 5
Fill in: 'We ___ a maximum query depth so a deeply nested request can't recursively explode server-side work.'
We 'enforce a limit' — the standard, established GraphQL collocation for requiring a safety boundary. The other options aren't the recognised term here.
2 / 5
Fill in: 'An unbounded nested query can ___ the resolver chain into thousands of downstream calls.'
We say deep nesting will 'drive' the resolver chain into excess calls — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ query complexity scores alongside depth so a wide-but-shallow query gets caught too.'
We 'calculate' a score — the standard, simple collocation for computing a numeric metric. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ an offending query with a clear error instead of letting it silently time out the whole server.'
We 'reject a query' — the standard, established collocation for refusing to execute an invalid request. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ depth limits per client type since an internal admin tool may legitimately need deeper queries.'
We 'tune' limits — the standard collocation for calibrating a configuration value per context. The other options are less idiomatic here.