Correlation ID for matching replies in RabbitMQ - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set a correlation ID when sending a message.

RabbitMQ

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

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

A'abcde-12345'

B'12345'

C12345

Dcorrelation_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using a number instead of a string for correlation_id

Using an undefined variable instead of a string

The correlation ID should be a unique string to match replies. Here, 'abcde-12345' is a valid string ID.

2fill in blank

medium

Complete the code to check if the reply message has the expected correlation ID.

RabbitMQ

if method.properties.correlation_id == [1]:
    process_reply(body)

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

A'reply_id'

Bmethod.correlation_id

Ccorrelation_id

D'abcde-12345'

Attempts:

3 left

💡 Hint

Common Mistakes

Comparing to a variable name instead of the string

Using wrong property name

We compare the reply's correlation_id to the original string ID to match the response.

3fill in blank

hard

Fix the error in the code to correctly set the correlation ID in the reply message properties.

RabbitMQ

channel.basic_publish(exchange='', routing_key=props.reply_to, body=response, properties=pika.BasicProperties([1]=props.correlation_id))

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

AcorrelationId

Bcorrelation_id

CcorrelationID

Dcorr_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using camelCase instead of snake_case

Using incorrect property names

The correct property name is 'correlation_id' in pika.BasicProperties.

4fill in blank

hard

Fill both blanks to create a reply queue and consume messages with a callback.

RabbitMQ

result = channel.queue_declare(queue='', exclusive=[1])
channel.basic_consume(queue=result.method.queue, on_message_callback=[2], auto_ack=True)

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

ATrue

BFalse

Ccallback

Dhandle_reply

Attempts:

3 left

💡 Hint

Common Mistakes

Setting exclusive to False

Using wrong callback function name

Setting exclusive=True creates a private reply queue. The callback function 'handle_reply' processes incoming messages.

5fill in blank

hard

Fill all three blanks to send a message with a correlation ID, set up a reply queue, and start consuming replies.

RabbitMQ

corr_id = [1]
channel.basic_publish(exchange='', routing_key='rpc_queue', body=request, properties=pika.BasicProperties(reply_to=callback_queue, correlation_id=corr_id))
channel.basic_consume(queue=callback_queue, on_message_callback=[2], auto_ack=[3])

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

A'abcde-12345'

Bhandle_response

CTrue

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using a variable instead of string for corr_id

Setting auto_ack to False without manual ack handling

We assign a unique string to corr_id, use 'handle_response' as the callback, and set auto_ack to True for automatic message acknowledgment.

Practice

1. What is the main purpose of the correlation_id property in RabbitMQ messaging?

easy

A. To specify the message priority in the queue

B. To link a reply message to its original request message

C. To encrypt the message content for security

D. To define the message expiration time

Solution

1. Step 1: Understand message flow in request-reply pattern

   In RabbitMQ, when a client sends a request, it expects a reply. The correlation_id helps identify which reply matches which request.

2. Step 2: Identify the role of correlation_id

   The correlation_id is set in the request message and copied to the reply, so the client can match them correctly.

3. Final Answer:

   To link a reply message to its original request message -> Option B

4. Quick Check:

   Correlation ID = Link request and reply [OK]

Hint: Correlation ID connects request and reply messages [OK]

Common Mistakes:

• Thinking correlation_id encrypts messages
• Confusing correlation_id with message priority
• Assuming correlation_id sets message expiration

2. Which of the following is the correct way to set the correlation_id property when publishing a message in RabbitMQ using Python pika library?

easy

A. channel.send(exchange='', routing_key='queue', body='msg', properties={'correlation': '123'})

B. channel.publish(exchange='', routing_key='queue', body='msg', correlation_id='123')

C. channel.basic_publish(exchange='', routing_key='queue', body='msg', properties=pika.BasicProperties(correlation_id='123'))

D. channel.basic_send(exchange='', routing_key='queue', body='msg', correlation='123')

Solution

1. Step 1: Recall pika syntax for setting message properties

   In pika, message properties are set using pika.BasicProperties with named arguments like correlation_id.

2. Step 2: Identify correct method and property usage

   The correct method is basic_publish and the property is correlation_id inside BasicProperties.

3. Final Answer:

   channel.basic_publish(exchange='', routing_key='queue', body='msg', properties=pika.BasicProperties(correlation_id='123')) -> Option C

4. Quick Check:

   Use basic_publish + BasicProperties(correlation_id) [OK]

Hint: Use BasicProperties with correlation_id in basic_publish [OK]

Common Mistakes:

• Using wrong method like publish or send
• Passing correlation_id outside BasicProperties
• Using incorrect property name like 'correlation'

3. Given the following Python code snippet using pika, what will be printed?

import pika

connection = pika.BlockingConnection(pika.ConnectionParameters('localhost'))
channel = connection.channel()

corr_id = 'abc123'

channel.basic_publish(
    exchange='',
    routing_key='rpc_queue',
    body='Request',
    properties=pika.BasicProperties(correlation_id=corr_id, reply_to='reply_queue')
)

print(corr_id)

medium

A. abc123

B. Request

C. None

D. Error: correlation_id not defined

Solution

1. Step 1: Analyze variable assignment and usage

   The variable corr_id is assigned the string 'abc123' before publishing the message.

2. Step 2: Understand the print statement

   The print statement outputs the value of corr_id, which is 'abc123'. The message publishing does not affect this variable.

3. Final Answer:

   abc123 -> Option A

4. Quick Check:

   Print variable corr_id = abc123 [OK]

Hint: Print variable directly, not message body [OK]

Common Mistakes:

• Confusing printed output with message body
• Expecting None because of message publish
• Assuming error due to correlation_id usage

4. You wrote this code to match replies by correlation ID but it never matches. What is the likely error?

def on_response(ch, method, props, body):
    if props.correlation_id == corr_id:
        print('Reply matched:', body)

channel.basic_consume(queue='reply_queue', on_message_callback=on_response, auto_ack=True)

medium

A. The variable corr_id is not defined in the callback scope

B. The auto_ack parameter should be False

C. The correlation_id property is not set in the reply message

D. The queue name 'reply_queue' is incorrect

Solution

1. Step 1: Check variable scope in callback function

   The callback uses corr_id but it is not passed or declared inside the function, causing a NameError or mismatch.

2. Step 2: Understand variable scope and fix

   To fix, corr_id should be accessible inside on_response, either by passing it or declaring as global or closure variable.

3. Final Answer:

   The variable corr_id is not defined in the callback scope -> Option A

4. Quick Check:

   corr_id must be in callback scope [OK]

Hint: Ensure corr_id is accessible inside callback function [OK]

Common Mistakes:

• Ignoring variable scope issues
• Changing auto_ack unnecessarily
• Assuming queue name is wrong without checking

5. You want to implement a RabbitMQ RPC client that sends multiple requests and matches replies correctly. Which approach best uses correlation_id to handle multiple outstanding requests?

hard

A. Use the same correlation_id for all requests to simplify matching

B. Set correlation_id only on the first request and ignore for others

C. Do not set correlation_id and rely on message order in the queue

D. Generate a unique correlation_id for each request and store a mapping of IDs to callbacks or futures

Solution

1. Step 1: Understand multiple outstanding requests scenario

   When sending many requests, replies can arrive in any order, so each must be uniquely identified.

2. Step 2: Use unique correlation IDs and mapping

   Assign a unique correlation_id per request and keep a map from ID to the request handler (callback or future) to match replies correctly.

3. Final Answer:

   Generate a unique correlation_id for each request and store a mapping of IDs to callbacks or futures -> Option D

4. Quick Check:

   Unique correlation_id + mapping = correct reply matching [OK]

Hint: Use unique correlation_id per request with a map [OK]

Common Mistakes:

• Using same correlation_id for all requests
• Ignoring correlation_id and relying on order
• Setting correlation_id only once