Why RPC enables request-reply over queues in RabbitMQ - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does RPC use queues for request-reply?

In RabbitMQ RPC, how does the client receive the reply from the server?

A The client sends requests to a shared queue and waits for the server to push replies to the same queue.

B The client listens on a temporary reply queue and matches replies using a correlation ID.

C The server sends replies directly to the client's IP address without using queues.

D The client polls the request queue repeatedly to check for replies.

💡 Hint

Think about how the client knows which reply belongs to its request.

RPC in RabbitMQ uses a temporary reply queue for each client. The client sends a request with a correlation ID and listens on this reply queue. The server sends the response back to this queue with the same correlation ID, allowing the client to match replies to requests.

💻 Command Output

intermediate

Identify the output of a RabbitMQ RPC client waiting for a reply

Given the following simplified Python RabbitMQ RPC client snippet, what will be printed?

RabbitMQ

import pika
import uuid

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

result = channel.queue_declare(queue='', exclusive=True)
callback_queue = result.method.queue

corr_id = str(uuid.uuid4())

print(f"Waiting for reply with correlation ID: {corr_id}")

A RuntimeError because queue_declare is missing parameters

B SyntaxError due to missing parentheses in print

C Waiting for reply with correlation ID: <some-uuid-string>

D Waiting for reply with correlation ID: None

💡 Hint

Look at how the correlation ID is generated and printed.

The code generates a UUID string and prints it with the message. The print statement is correct syntax in Python 3. The queue_declare call is valid and returns a queue name. So the output is the message with a UUID.

❓ Configuration

advanced

Which RabbitMQ queue property is essential for RPC reply queues?

When setting up a reply queue for RPC in RabbitMQ, which queue property ensures the reply queue is deleted when the client disconnects?

A auto_delete=false

B durable=true

C persistent=true

D exclusive=true

💡 Hint

Think about a queue that only the client uses and should disappear after disconnect.

Setting exclusive=true makes the queue accessible only by the connection that declared it and deletes it when the connection closes. This is ideal for temporary reply queues in RPC.

❓ Troubleshoot

advanced

Why does the RPC client never receive a reply?

An RPC client sends requests to a server queue but never receives replies. Which is the most likely cause?

A The server does not set the reply_to property in the response message.

B The client queue is declared with durable=true.

C The client uses a fixed queue name for requests instead of a temporary queue.

D The server uses the same correlation ID for all replies.

💡 Hint

Check how the server sends the reply back to the client.

If the server does not set the reply_to property in the response, the client does not know where to listen for the reply, so it never receives it.

🔀 Workflow

expert

Order the steps in RabbitMQ RPC request-reply communication

Put the following steps in the correct order for a RabbitMQ RPC client-server interaction.

A 1,2,3,4

B 1,3,2,4

C 2,1,3,4

D 2,3,1,4

💡 Hint

Think about what the client must do before sending a request.

The client first creates a temporary reply queue, then sends the request with correlation ID and reply_to set. The server processes and replies to that queue. The client listens and matches replies by correlation ID.