1 / 5
Fill in: 'A naive resolver can ___ hundreds of extra database queries for a single nested field.'
-
-
-
-
We say a naive resolver will 'trigger' extra queries — the standard collocation for causing the n+1 pattern. The other options aren't idiomatic here.
2 / 5
Fill in: 'We ___ a data loader so identical requests within one tick get batched into a single query.'
-
-
-
-
We 'use a data loader' — the standard, simple collocation for adopting the batching pattern. The other options are less idiomatic here.
3 / 5
Fill in: 'We ___ resolver query counts per request so an n+1 regression shows up before production.'
-
-
-
-
We 'track' query counts — the standard collocation for monitoring a per-request metric. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ related records in a single batched call instead of looping and fetching one at a time.'
-
-
-
-
We 'load' related records — the standard, simple collocation for retrieving associated data. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a query complexity limit so a deeply nested request can't spawn thousands of resolver calls.'
-
-
-
-
We 'enforce a limit' — the standard collocation for applying a hard cap. The other options aren't idiomatic here.