Practise the standard verbs for handling database connection timeouts safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a connection timeout so a hung database call never blocks a request thread forever.'
We 'set a timeout' — the standard, simple collocation for bounding how long a call can wait. The other options are less idiomatic here.
2 / 5
Fill in: 'An exhausted connection pool can ___ every new request waiting indefinitely for a free slot.'
We say an exhausted pool will 'leave' requests waiting — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a timeout error clearly instead of letting a caller assume the database just silently vanished.'
We 'surface an error' — the standard collocation for making a failure visible to a caller. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ slow queries proactively so they never accumulate and eat up the whole connection pool.'
We 'kill a query' — the standard, established database collocation for forcibly terminating a running statement. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ timeout and retry values together so a retry never fires before the original call has even given up.'
We 'tune' values — the standard collocation for calibrating related timing parameters. The other options are less idiomatic here.