1 / 5
Fill in: 'We ___ persisted queries so the client sends a short hash instead of the full query text on every request.'
-
-
-
-
We 'use' a technique — the standard, simple collocation for adopting an approach. The other options are less idiomatic here.
2 / 5
Fill in: 'An unregistered query hash can ___ the server rejecting a perfectly valid request outright.'
-
-
-
-
We say a missing registration will 'cause' rejection — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ every allowed query hash in a persisted-query manifest at build time, not at request time.'
-
-
-
-
We 'generate a manifest' — the standard, simple collocation for producing a build artifact. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ arbitrary ad-hoc queries in production once persisted queries are enforced, closing off a common attack surface.'
-
-
-
-
We 'block' queries — the standard, simple collocation for refusing a category of request. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the persisted-query allowlist on every deploy so it never drifts out of sync with the actual client code.'
-
-
-
-
We 'update' an allowlist — the standard, simple collocation for keeping a stored list current. The other options are less idiomatic here.