Exactly-once processing strategies in RabbitMQ - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a durable queue in RabbitMQ.

RabbitMQ

channel.queue_declare(queue='task_queue', durable=[1])

Drag options to blanks, or click blank then click option'

AFalse

BNone

CTrue

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using False makes the queue non-durable, risking message loss.

Setting durable=True ensures the queue survives RabbitMQ restarts, which is important for exactly-once processing.

2fill in blank

medium

Complete the code to acknowledge a message after processing it.

RabbitMQ

channel.basic_ack(delivery_tag=[1])

Drag options to blanks, or click blank then click option'

Amethod.delivery_tag

Bmessage

Cchannel

Dbody

Attempts:

3 left

💡 Hint

Common Mistakes

Using the message body or channel instead of delivery tag causes errors.

The method.delivery_tag uniquely identifies the message to acknowledge it properly.

3fill in blank

hard

Fix the error in the code to enable publisher confirms for exactly-once delivery.

RabbitMQ

channel.[1]()

Drag options to blanks, or click blank then click option'

Aconfirm_delivery

Bconfirm_select

Cenable_confirm

Dpublisher_confirm

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect method names causes AttributeError.

The correct method to enable publisher confirms in RabbitMQ is confirm_select().

4fill in blank

hard

Fill both blanks to set message properties for persistent delivery and publish a message.

RabbitMQ

channel.[2]()
channel.basic_publish(exchange='', routing_key='task_queue', body=message, properties=pika.BasicProperties(delivery_mode=[1]))

Drag options to blanks, or click blank then click option'

A2

B1

Cbasic_ack

Dconfirm_select

Attempts:

3 left

💡 Hint

Common Mistakes

Using delivery_mode=1 makes messages transient.

Setting delivery_mode=2 makes messages persistent. Calling confirm_select() enables publisher confirms.

5fill in blank

hard

Fill both blanks to create a consumer that processes messages exactly once with manual acknowledgments and prefetch count.

RabbitMQ

channel.basic_qos(prefetch_count=[1])
channel.basic_consume(queue='task_queue', on_message_callback=callback, auto_ack=[2])
channel.start_consuming()

Drag options to blanks, or click blank then click option'

A1

B0

CFalse

DTrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using auto_ack=True causes messages to be acknowledged before processing.

Setting prefetch_count=1 limits unacknowledged messages to one at a time. auto_ack=False enables manual acknowledgments for exactly-once processing. start_consuming() starts the consumer loop.

Practice

1. What does "exactly-once processing" mean in RabbitMQ?

easy

A. Each message is processed only one time without duplicates

B. Messages are processed at least once, possibly multiple times

C. Messages are processed only if the queue is empty

D. Messages are processed without any acknowledgments

Solution

1. Step 1: Understand message processing guarantees

   Exactly-once means no message is lost or processed more than once.

2. Step 2: Compare options with definition

   Only Each message is processed only one time without duplicates matches the definition of exactly-once processing.

3. Final Answer:

   Each message is processed only one time without duplicates -> Option A

4. Quick Check:

   Exactly-once = single processing [OK]

Hint: Exactly-once means no repeats or losses in processing [OK]

Common Mistakes:

• Confusing exactly-once with at-least-once processing
• Ignoring the role of acknowledgments
• Thinking messages process only when queue is empty

2. Which RabbitMQ feature helps ensure messages are not lost during processing?

easy

A. Automatic message deletion

B. Disabling publisher confirms

C. Unlimited queue length

D. Manual message acknowledgments

Solution

1. Step 1: Identify message loss prevention methods

   Manual acknowledgments let consumers confirm message processing before removal.

2. Step 2: Evaluate options for loss prevention

   Only manual acknowledgments ensure messages aren't lost if consumer fails.

3. Final Answer:

   Manual message acknowledgments -> Option D

4. Quick Check:

   Manual ack = message safe until confirmed [OK]

Hint: Manual ack confirms message processed safely [OK]

Common Mistakes:

• Assuming automatic deletion prevents loss
• Thinking unlimited queue length affects message safety
• Disabling confirms helps reliability (it doesn't)

3. Given this consumer code snippet, what happens if the consumer crashes before ack?

channel.basic_consume(queue='task_queue', on_message_callback=callback)

def callback(ch, method, properties, body):
    process_message(body)
    # no ack sent here

medium

A. Message is lost and not requeued

B. Message remains unacknowledged and will be redelivered

C. Message is acknowledged automatically

D. Queue deletes the message immediately

Solution

1. Step 1: Understand manual ack behavior

   If no ack is sent, RabbitMQ keeps message unacknowledged.

2. Step 2: Effect of consumer crash before ack

   RabbitMQ will redeliver unacknowledged messages to another consumer.

3. Final Answer:

   Message remains unacknowledged and will be redelivered -> Option B

4. Quick Check:

   No ack = redelivery on crash [OK]

Hint: No ack means message redelivery on failure [OK]

Common Mistakes:

• Assuming message is lost without ack
• Thinking messages auto-acknowledge by default
• Believing queue deletes messages immediately

4. You notice duplicate message processing in your RabbitMQ consumer. Which fix helps ensure exactly-once processing?

medium

A. Implement idempotent message handling and manual acks

B. Disable publisher confirms

C. Use automatic acknowledgments

D. Increase queue prefetch count

Solution

1. Step 1: Identify cause of duplicates

   Duplicates often occur if messages are reprocessed after failure or redelivery.

2. Step 2: Apply exactly-once strategies

   Idempotent handling plus manual acknowledgments prevent duplicate side effects.

3. Final Answer:

   Implement idempotent message handling and manual acks -> Option A

4. Quick Check:

   Idempotent + manual ack = exactly-once [OK]

Hint: Idempotent code + manual ack stops duplicates [OK]

Common Mistakes:

• Using automatic ack causes duplicates
• Disabling confirms reduces reliability
• Increasing prefetch doesn't fix duplicates

5. To achieve exactly-once processing in RabbitMQ, which combination is best practice?

hard

A. Automatic acknowledgments with no idempotency

B. Using only transactions without manual acknowledgments

C. Manual acknowledgments, idempotent consumer code, and publisher confirms

D. Disabling transactions and using auto-delete queues

Solution

1. Step 1: Review exactly-once requirements

   Exactly-once needs safe message delivery, no duplicates, and confirmed processing.

2. Step 2: Match features to requirements

   Manual acks confirm processing, idempotent code avoids duplicates, publisher confirms ensure message sent.

3. Step 3: Eliminate incorrect options

   Automatic ack or disabling transactions risk message loss or duplicates.

4. Final Answer:

   Manual acknowledgments, idempotent consumer code, and publisher confirms -> Option C

5. Quick Check:

   Manual ack + idempotent + confirms = exactly-once [OK]

Hint: Combine manual ack, idempotency, and confirms for safety [OK]

Common Mistakes:

• Relying on automatic acknowledgments alone
• Ignoring idempotent consumer design
• Assuming transactions alone guarantee exactly-once