Correlation ID for matching replies in RabbitMQ - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Correlation ID in RabbitMQ

What is the main purpose of using a Correlation ID in RabbitMQ messaging?

A To uniquely identify and match a reply message to its original request message

B To specify the queue where the message should be delivered

C To encrypt the message content for security

D To set the message priority for delivery order

💡 Hint

Think about how a client knows which reply belongs to which request.

The Correlation ID is used to tag request messages so that when a reply comes back, the client can match it to the original request. It acts like a tracking number.

💻 Command Output

intermediate

Output of a RabbitMQ message with Correlation ID

Given a message published with the following properties:

properties = {"correlation_id": "abc123", "reply_to": "response_queue"}

What will be the value of correlation_id in the received message properties?

A "abc123"

B "response_queue"

C null

D "correlation_id"

💡 Hint

The correlation_id is set explicitly in the message properties.

The correlation_id property is set to "abc123" and will be received exactly as sent.

🔀 Workflow

advanced

Correct workflow to handle RPC with Correlation ID

Which of the following workflows correctly uses the Correlation ID to handle RPC (Remote Procedure Call) replies in RabbitMQ?

A Client sends request with Correlation ID; server sends reply without Correlation ID; client matches replies by timestamp.

B Client sends request without Correlation ID; server generates Correlation ID and sends reply; client listens on default queue without matching Correlation ID.

C Client sends request with a unique Correlation ID and reply_to queue; server processes and sends reply with same Correlation ID to reply_to queue; client listens on reply_to queue and matches replies by Correlation ID.

D Client sends request with Correlation ID; server ignores Correlation ID and sends reply to a fixed queue; client matches replies by message content only.

💡 Hint

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

The client must send a unique Correlation ID and specify a reply_to queue. The server must send the reply with the same Correlation ID to that queue. The client listens on that queue and matches replies by Correlation ID.

❓ Troubleshoot

advanced

Troubleshooting missing replies in RPC with Correlation ID

A client sends RPC requests with unique Correlation IDs and a reply_to queue. However, the client never receives replies. Which of the following is the most likely cause?

A The server is sending replies to the default exchange instead of the reply_to queue.

B The client is listening on the wrong queue, not the reply_to queue specified.

C The server is not setting the Correlation ID in the reply message properties.

D The client is not generating unique Correlation IDs for each request.

💡 Hint

Check where the client is listening for replies.

If the client listens on the wrong queue, it will never receive replies even if the server sends them correctly with Correlation IDs.

✅ Best Practice

expert

Best practice for generating Correlation IDs in RabbitMQ RPC

Which of the following is the best practice for generating Correlation IDs for RPC requests in RabbitMQ to ensure reliable reply matching?

A Use the client's IP address as the Correlation ID.

B Use a simple incrementing integer starting from 1 for each request.

C Use the current timestamp in seconds as the Correlation ID.

D Use a UUID (Universally Unique Identifier) for each request's Correlation ID.

💡 Hint

Think about uniqueness and collision risk.

Using a UUID ensures that each Correlation ID is unique across all requests, avoiding collisions and ensuring reliable matching of replies.