Practise the standard verbs for handling Postgres connection retries safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ exponential backoff into the connection retry logic so a brief database restart doesn't trigger a thundering herd.'
We 'build' logic — the standard, simple collocation for constructing a piece of retry handling. The other options are less idiomatic here.
2 / 5
Fill in: 'Retrying immediately without any delay can ___ hundreds of app instances overwhelming a database that's still recovering.'
We say immediate retries will 'cause' overload — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a maximum retry count so a permanently unreachable database fails fast instead of retrying forever.'
We 'set a count' — the standard, simple collocation for configuring an upper bound on attempts. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every connection failure with its error code so a DNS issue and an auth failure aren't confused during debugging.'
We 'log' a failure — the standard, simple collocation for recording an event for later inspection. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ retry behaviour in a chaos test by killing the database mid-traffic to confirm the app recovers cleanly.'
We 'verify' behaviour — the standard, established collocation for confirming a system works as intended under test conditions. The other options aren't the recognised term here.