GraphQL Directive Authorization Language Collocations
Practise the standard verbs for enforcing authorization with GraphQL directives.
0 / 5 completed
1 / 5
Fill in: 'We ___ an @auth directive on sensitive fields so authorization is declared right in the schema instead of scattered across resolvers.'
We 'attach a directive' — the standard, established GraphQL collocation for annotating a schema field with custom behaviour. The other options aren't the recognised term here.
2 / 5
Fill in: 'Checking permissions only in the top-level resolver can ___ a nested field returning data the caller was never meant to see.'
We say a top-level-only check will 'leave' a nested field exposed — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the directive's logic once in a schema transformer so every field it's attached to gets consistent enforcement.'
We 'implement' logic — the standard, simple collocation for writing the behaviour behind a reusable directive. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ unauthorized field access with a partial response and an error, rather than failing the entire query outright.'
We 'handle' a case — the standard, simple collocation for defining how an edge case is dealt with. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ every directive-protected field with a test for both an authorized and an unauthorized caller before it ships.'
We 'cover' a field with tests — the standard, established collocation for ensuring a case is exercised by automated tests. The other options aren't the recognised term here.