Backend interview prep

Start

RabbitMQ Publisher Confirms Interview Questions and Answers

Learn RabbitMQ Publisher Confirms with real-world interview questions covering acknowledgements, confirms, transactions, mandatory publishing, returns, Spring Boot integration, and production best practices.

RabbitMQ Publisher Confirms Interview Questions and Answers

Reliable message delivery is one of the biggest concerns in distributed systems.

Imagine a banking application:

Transfer ₹5,00,000

↓

Producer Sends Message

↓

Network Failure

Did RabbitMQ receive the message?

Was the message stored?

Should the producer retry?

RabbitMQ solves this problem using Publisher Confirms.

Publisher Confirms allow producers to know whether RabbitMQ has successfully accepted a published message.

Publisher Confirm Architecture

flowchart LR

Producer --> Exchange

Exchange --> RabbitmqBroker["RabbitMQ Broker"]

RabbitmqBroker["RabbitMQ Broker"] --> ACK

ACK --> Producer

Q1. What are Publisher Confirms?

Answer

Publisher Confirms are a RabbitMQ reliability feature that notifies the producer whether a published message has been accepted by the broker.

RabbitMQ sends one of two responses:

  • ACK (Accepted)
  • NACK (Rejected)

This allows producers to react appropriately by logging, retrying, or handling failures.

Confirm Flow

flowchart LR

Producer --> RabbitMQ

RabbitMQ --> ACK/NACK

ACK/NACK --> Producer

Q2. Why do we need Publisher Confirms?

Answer

Without Publisher Confirms:

Producer

↓

Send Message

↓

Unknown Result

With Publisher Confirms:

Producer

↓

Send Message

↓

Broker ACK

↓

Success

Benefits:

  • Reliable Publishing
  • Failure Detection
  • Retry Support
  • Better Durability

Reliability

flowchart LR

Producer --> Message
Message --> RabbitMQ

RabbitMQ --> Confirmation

Q3. What is the difference between ACK and NACK?

Answer

ACK

RabbitMQ accepted the message.

NACK

RabbitMQ could not process the message.

Producer decisions:

ACK

Continue

NACK

Retry

or

Log Error

ACK vs NACK

flowchart TD

Producer --> RabbitMQ

RabbitMQ --> ACK

RabbitMQ --> NACK

Q4. How do Publisher Confirms work internally?

Answer

Workflow:

  1. Producer publishes a message.
  2. RabbitMQ receives it.
  3. Broker validates the publish.
  4. Broker sends ACK or NACK.
  5. Producer handles the response.

Internal Flow

sequenceDiagram
participant Producer
participant Broker
Producer->>Broker: Publish Message
Broker-->>Producer: ACK/NACK

Q5. What is the difference between Publisher Confirms and Consumer Acknowledgements?

Answer

Publisher Confirm Consumer ACK
Producer → Broker Consumer → Broker
Confirms Publish Confirms Processing
Before Consumer Reads After Consumer Processes
Publisher Reliability Consumer Reliability

Publisher Confirms protect message publishing.

Consumer ACKs protect message processing.

Comparison

flowchart LR

Producer --> Broker

Broker --> Consumer

Broker --> PublisherAck["Publisher ACK"]

Consumer --> ConsumerAck["Consumer ACK"]

Q6. What is the difference between Publisher Confirms and RabbitMQ Transactions?

Answer

RabbitMQ provides two reliability mechanisms.

Publisher Confirms

  • Lightweight
  • High Performance
  • Asynchronous
  • Recommended

Transactions

  • Slower
  • Synchronous
  • Higher Overhead

Production Recommendation:

Use Publisher Confirms instead of transactions unless transactional publishing is specifically required.

Comparison

flowchart LR

Producer --> PublisherConfirm["Publisher Confirm"]

Producer --> Transaction

Q7. What is Mandatory Publishing?

Answer

Mandatory Publishing ensures producers are informed if a message cannot be routed to any queue.

Example

Producer

↓

Exchange

↓

No Queue Match

↓

Return Message

Without the mandatory flag, the message is discarded by default.

Mandatory Publish

flowchart TD

Producer --> Exchange

Exchange --> NoQueue["No Queue"]

NoQueue["No Queue"] --> ReturnProducer["Return Producer"]

Q8. What is a Return Callback?

Answer

A Return Callback is invoked when:

  • The message reaches the exchange.
  • No queue matches the routing rules.
  • Mandatory publishing is enabled.

Producer receives:

  • Original Message
  • Routing Key
  • Exchange
  • Failure Reason

Return Flow

flowchart LR

Producer --> Exchange

Exchange --> NoMatchingQueue["No Matching Queue"]

NoMatchingQueue["No Matching Queue"] --> ReturnCallback["Return Callback"]

Q9. How does Spring Boot support Publisher Confirms?

Answer

Spring Boot supports Publisher Confirms using Spring AMQP.

Typical flow:

REST API

↓

Spring Boot

↓

RabbitTemplate

↓

RabbitMQ

↓

Confirm Callback

Applications can register callbacks to receive publish confirmations asynchronously.

Spring Boot

flowchart TD

RestApi["REST API"] --> RabbitTemplate
RabbitTemplate --> RabbitMQ

RabbitMQ --> ConfirmCallback["Confirm Callback"]

Q10. What are the production best practices?

Answer

Recommended practices:

  • Enable Publisher Confirms.
  • Enable Mandatory Publishing.
  • Configure Return Callbacks.
  • Retry transient failures.
  • Log NACK events.
  • Monitor publish failures.
  • Use Durable Queues.
  • Publish Persistent Messages.
  • Combine with Consumer ACKs.
  • Avoid RabbitMQ Transactions unless necessary.

Enterprise Architecture

flowchart TD

SpringBoot["Spring Boot"] --> RabbitTemplate
RabbitTemplate --> Exchange

Exchange --> Queue

Queue --> Consumer

Exchange --> PublisherConfirm["Publisher Confirm"]

PublisherConfirm["Publisher Confirm"] --> Producer

Publisher Confirm Lifecycle

sequenceDiagram
participant Producer
participant RabbitMQ
participant Queue
Producer->>RabbitMQ: Publish
RabbitMQ->>Queue: Route
RabbitMQ-->>Producer: ACK
Queue->>Consumer: Deliver

Reliable Publishing

mindmap
  root((Reliable Publishing))
    Publisher Confirms
    Mandatory Publish
    Return Callback
    Durable Queue
    Persistent Message
    Consumer ACK

Publisher Confirms vs Transactions

Publisher Confirms RabbitMQ Transactions
Asynchronous Synchronous
High Performance Lower Performance
Lightweight Higher Overhead
Production Recommended Rarely Used
Better Scalability Limited Throughput

Publisher Confirm vs Consumer ACK

Publisher Confirm Consumer ACK
Producer Side Consumer Side
Confirms Delivery to Broker Confirms Successful Processing
Prevents Publish Loss Prevents Processing Loss
Before Queue Consumption After Business Logic

Real Banking Example

A customer transfers ₹7,50,000.

Transfer Service

↓

RabbitTemplate

↓

Transfer Exchange

↓

Transfer Queue

↓

Publisher ACK

↓

Fraud Detection

↓

Ledger Service

↓

Consumer ACK

Flow:

  1. The Transfer Service publishes the transfer event.
  2. RabbitMQ confirms the message has been accepted.
  3. Consumers process the event.
  4. After successful business processing, consumers acknowledge the message.

This provides end-to-end reliability from producer to consumer.

Senior Interview Tips

Interviewers commonly ask:

  • What are Publisher Confirms?
  • Why are Publisher Confirms needed?
  • ACK vs NACK?
  • Publisher Confirm vs Consumer ACK?
  • Publisher Confirm vs Transaction?
  • What is Mandatory Publishing?
  • What is a Return Callback?
  • How does Spring Boot implement Publisher Confirms?
  • When should RabbitMQ Transactions be used?
  • What happens if no queue matches the routing key?
  • What production configurations do you recommend?

Remember:

  • Publisher Confirms ensure RabbitMQ accepted the published message.
  • Consumer ACKs ensure successful message processing.
  • Mandatory Publishing detects unroutable messages.
  • Publisher Confirms are preferred over RabbitMQ Transactions for most production systems.

Quick Revision

  • Publisher Confirms notify producers whether RabbitMQ accepted published messages.
  • RabbitMQ returns ACK for successful publishing and NACK for failures.
  • Publisher Confirms improve reliability and support retry strategies.
  • Consumer ACKs confirm successful message processing, while Publisher Confirms confirm successful publishing.
  • Mandatory Publishing prevents silent loss of unroutable messages.
  • Return Callbacks notify producers when routing fails.
  • Spring Boot supports Publisher Confirms through Spring AMQP and RabbitTemplate.
  • Use Publisher Confirms with durable queues and persistent messages in production.
  • Prefer Publisher Confirms over RabbitMQ Transactions for better performance.
  • Publisher Confirms are essential for building reliable enterprise messaging systems.