Practise the standard verbs for masking sensitive GraphQL errors.
0 / 5 completed
1 / 5
Fill in: 'We ___ internal error details before returning a GraphQL response so a stack trace never leaks to the client.'
We 'mask' an error — the standard, established collocation for hiding sensitive details from a response. The other options aren't the recognised term here.
2 / 5
Fill in: 'Returning raw exception messages in the errors array can ___ internal schema details exposed to an attacker.'
We say raw messages will 'leave' details exposed — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a generic error code to the client while logging the full internal detail server-side for debugging.'
We 'return a code' — the standard, simple collocation for sending back a response value. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every unhandled resolver exception centrally so nothing bypasses the masking layer by accident.'
We 'catch' an exception — the standard, simple collocation for intercepting an error in code. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a correlation ID in the masked error so support can trace it back to the full internal log entry.'
We 'include' a field — the standard, simple collocation for adding useful context to an error. The other options are less idiomatic here.