Practise the standard verbs for propagating deadlines across a gRPC call chain.
0 / 5 completed
1 / 5
Fill in: 'We ___ a deadline on every outbound gRPC call so a slow downstream can't hang the whole chain.'
We 'set a deadline' — the standard, established gRPC collocation for bounding call duration. The other options aren't the recognised term here.
2 / 5
Fill in: 'We ___ the remaining deadline to each downstream call instead of resetting the clock at every hop.'
We 'propagate a deadline' — the standard, established collocation for passing the remaining budget onward. The other options aren't the recognised term here.
3 / 5
Fill in: 'A service that ignores the incoming deadline can ___ work long after the caller has already given up.'
We say ignoring a deadline will 'waste' work — the standard, natural collocation here. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ a deadline-exceeded error clearly so a caller knows the request timed out, not failed outright.'
We 'return an error' — the standard, simple collocation for signalling a specific failure. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ deadline budgets across a call chain so no single hop can claim the entire timeout for itself.'
We 'allocate a budget' — the standard collocation for dividing a limited resource across steps. The other options aren't idiomatic here.