Practise the standard verbs for handling Celery task retries safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a retry policy on every Celery task so a transient failure doesn't just vanish silently.'
We 'configure a policy' — the standard collocation for setting up retry behaviour. The other options aren't idiomatic here.
2 / 5
Fill in: 'A task retried without backoff can ___ the same overloaded downstream service every few seconds.'
We say a tight retry loop will 'hammer' a service — the standard, natural collocation for repeated aggressive load. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ exponential backoff between retries so a struggling downstream service gets time to recover.'
We 'apply backoff' — the standard, established collocation for increasing delay between retries. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a maximum retry count so a permanently broken task doesn't retry forever and clog the queue.'
We 'cap' a count — the standard, simple collocation for setting an upper bound on a value. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ an exhausted task to a dead-letter queue instead of letting it disappear once retries run out.'
We 'route a task' — the standard collocation for directing it to a specific destination. The other options are less idiomatic here.