Transaction mode vs confirms in RabbitMQ - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Difference between Transaction Mode and Publisher Confirms

Which statement correctly describes the main difference between RabbitMQ's transaction mode and publisher confirms?

A Transaction mode requires manual acknowledgment from consumers, whereas publisher confirms automatically acknowledge messages.

B Transaction mode is asynchronous and faster than publisher confirms, which are synchronous and slow down message publishing.

C Transaction mode batches multiple messages into a single atomic operation, while publisher confirms acknowledge each message individually after it is processed.

D Publisher confirms guarantee message delivery to the consumer, while transaction mode only guarantees message receipt by the broker.

💡 Hint

Think about how each method handles message acknowledgment and atomicity.

Transaction mode groups multiple messages into one atomic commit or rollback, ensuring all messages succeed or fail together. Publisher confirms send acknowledgments for each message individually after the broker processes them, allowing asynchronous confirmation.

💻 Command Output

intermediate

Output of Enabling Publisher Confirms

What is the expected output or effect after running the following RabbitMQ client command to enable publisher confirms?

RabbitMQ

channel.confirmSelect();

A The channel switches to confirm mode, allowing asynchronous acknowledgments for published messages.

B The channel enters transaction mode, requiring commit or rollback for message publishing.

C The command throws an error because confirmSelect() is deprecated.

D The channel disables message acknowledgments from the broker.

💡 Hint

Consider what confirmSelect() does in RabbitMQ client libraries.

confirmSelect() enables publisher confirms on the channel, so the client receives asynchronous acknowledgments for each published message.

🔀 Workflow

advanced

Correct Workflow for Using Transaction Mode

Which sequence correctly represents the workflow when using RabbitMQ transaction mode for publishing messages?

A 2,1,3,4

B 1,2,3,4

C 1,2,4,3

D 2,3,1,4

💡 Hint

Think about the order of starting a transaction, publishing, and committing.

You must begin the transaction first, then publish messages, then commit. If something goes wrong, rollback instead of commit.

❓ Troubleshoot

advanced

Troubleshooting Missing Publisher Confirms

You enabled publisher confirms on your RabbitMQ channel, but your application never receives any confirmations. What is the most likely cause?

A The consumer did not acknowledge the messages.

B The broker does not support publisher confirms and silently ignores the setting.

C The messages were published with the mandatory flag set to false.

D The channel was not set to confirm mode before publishing messages.

💡 Hint

Check when confirm mode is enabled relative to publishing.

Publisher confirms must be enabled on the channel before publishing messages. If enabled after, no confirms are sent for already published messages.

✅ Best Practice

expert

Choosing Between Transaction Mode and Publisher Confirms

In a high-throughput RabbitMQ system, which approach is best to ensure message delivery without significantly slowing down publishing?

A Use publisher confirms because they provide asynchronous acknowledgments and better performance than transactions.

B Use transaction mode because it guarantees atomicity and is faster than publisher confirms.

C Disable both transaction mode and publisher confirms to maximize speed and rely on consumer acknowledgments.

D Use both transaction mode and publisher confirms together for maximum reliability.

💡 Hint

Consider the performance impact of synchronous vs asynchronous confirmation methods.

Publisher confirms are asynchronous and scale better for high throughput. Transaction mode is slower due to synchronous commit overhead.