Practise the standard verbs for handling WebSocket reconnect backoff safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ exponential backoff between reconnect attempts so a flaky network doesn't hammer the server.'
We 'apply backoff' — the standard, established collocation for increasing delay between retries. The other options aren't the recognised term here.
2 / 5
Fill in: 'A client that reconnects instantly on every drop can ___ a thundering herd against the server after an outage.'
We say instant reconnects will 'create' a thundering herd — the standard, simple collocation for the resulting overload. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ jitter into the backoff delay so many clients don't all retry at exactly the same moment.'
We 'add jitter' — the standard, established collocation for introducing randomness into a retry schedule. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a maximum backoff ceiling so retry delays never grow unreasonably long after a short outage.'
We 'cap' a ceiling — the standard, simple collocation for bounding a growing value. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ reconnect attempts closely in the client logs so a persistent connectivity issue gets noticed fast.'
We 'log' attempts — the standard, simple collocation for recording events for later inspection. The other options are less idiomatic here.