RabbitMQ Message Acknowledgment Language Collocations
Practise the standard verbs for handling RabbitMQ message acknowledgment safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ manual acknowledgment on the consumer, rather than auto-ack that drops a message before it's actually processed.'
We 'enable acknowledgment' — the standard, simple collocation for turning on manual message acks. The other options are less idiomatic here.
2 / 5
Fill in: 'Acking a message before processing finishes can ___ a failed job lost with no actual retry ever attempted.'
We say an early ack will 'leave' a failed job lost — the standard, natural collocation for the resulting data loss. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a dead-letter exchange for nacked messages, rather than discarding a failure nobody's actually able to inspect later.'
We 'attach an exchange' — the standard, simple collocation for routing failed messages to a dead-letter exchange. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every consumer's prefetch count against actual processing time, rather than a default that leaves workers idle or overloaded.'
We 'tune prefetch' — the standard, simple collocation for adjusting how many unacked messages a consumer holds. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ unacked message counts on the queue dashboard, rather than discovering a stuck consumer only once the backlog's actually huge.'
We 'watch counts' — the standard, simple collocation for monitoring unacknowledged messages on a queue. The other options aren't idiomatic here.