Practise the standard verbs for building gRPC interceptor middleware.
0 / 5 completed
1 / 5
Fill in: 'We ___ a logging interceptor on the server so every incoming call gets a structured log entry without touching each handler.'
We 'register an interceptor' — the standard, established gRPC collocation for attaching middleware to the call chain. The other options aren't the recognised term here.
2 / 5
Fill in: 'Putting authentication logic in every handler instead of an interceptor can ___ one endpoint accidentally skipping the check.'
We say duplicated logic will 'cause' a missed check somewhere — the standard collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ interceptors in a defined order so authentication always runs before authorization, never the other way round.'
We 'chain interceptors' — the standard, established collocation for composing multiple middleware layers in sequence. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ request metadata inside an interceptor to extract the auth token before it ever reaches the actual handler.'
We 'inspect' metadata — the standard, simple collocation for examining request headers. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a unit test around each interceptor in isolation so its behaviour is verified independently of any specific handler.'
We 'write a test' — the standard, simple collocation for authoring a verification case. The other options are less idiomatic here.