Practise the standard verbs for using the gRPC reflection service safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ the gRPC reflection service in staging so a tool like grpcurl can discover a service's methods without needing the original .proto file on hand.'
We 'enable a service' — the standard, established gRPC collocation for turning on the reflection API for introspection. The other options aren't the recognised term here.
2 / 5
Fill in: 'Leaving reflection enabled by default in production can ___ every internal method signature discoverable to anyone who can simply reach the server's port.'
We say enabled reflection will 'leave' method signatures discoverable — the standard, natural collocation for the resulting exposure. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ reflection access behind the same authentication as the service's real methods, rather than treating introspection as a harmless, unrestricted feature.'
We 'restrict access' — the standard, simple collocation for limiting who can reach a sensitive feature. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a service's methods through reflection during manual debugging, since it lets us call an endpoint quickly without hunting down its exact .proto definition first.'
We 'query methods' — the standard, simple collocation for asking a service to describe its own interface. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ reflection entirely in production builds via a compile flag, so the feature exists only in the environments where it's actually meant to be used.'
We 'disable a feature' — the standard, established collocation for turning off a capability in environments where it's a liability. The other options aren't the recognised term here.