RPC vs direct API calls in RabbitMQ - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding RPC vs Direct API Calls

Which statement best describes the main difference between RPC (Remote Procedure Call) over RabbitMQ and direct API calls?

A RPC and direct API calls are identical in communication style and protocol.

B RPC requires a web server, but direct API calls do not.

C Direct API calls always use message queues, but RPC uses HTTP protocols.

D RPC uses message queues to communicate asynchronously, while direct API calls are synchronous HTTP requests.

💡 Hint

Think about how messages are sent and received in each method.

RPC over RabbitMQ sends messages asynchronously through queues, allowing decoupled communication. Direct API calls typically use synchronous HTTP requests where the client waits for the server response immediately.

💻 Command Output

intermediate

Output of RPC Client Request in RabbitMQ

Given a RabbitMQ RPC client sends a request and waits for a response, what will be the output if the server replies with the message 'Success'?

RabbitMQ

client.send('request_data')
response = client.wait_for_response()
print(response)

A TimeoutError

B None

C Success

D request_data

💡 Hint

The client waits for the server's reply message.

The client sends a request and waits for the server to respond. When the server replies with 'Success', the client prints that message.

🔀 Workflow

advanced

Correct RPC Workflow Sequence

What is the correct order of steps in a RabbitMQ RPC communication?

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 1,2,4,3

💡 Hint

Think about the message flow from client to server and back.

The client first sends a request to the RPC queue. The server receives and processes it, then sends a response to the reply queue. Finally, the client receives the response.

❓ Troubleshoot

advanced

Troubleshooting Missing RPC Response

A RabbitMQ RPC client sends a request but never receives a response. Which is the most likely cause?

A The client is using HTTP instead of RabbitMQ.

B The server is not consuming messages from the RPC queue.

C The RabbitMQ server is down and no messages are sent.

D The client did not send the request message.

💡 Hint

Consider what happens if the server does not process incoming requests.

If the server is not consuming messages from the RPC queue, requests pile up and no responses are sent back, causing the client to wait indefinitely.

✅ Best Practice

expert

Best Practice for Timeout Handling in RabbitMQ RPC

What is the best practice to handle timeouts in a RabbitMQ RPC client to avoid waiting forever for a response?

A Set a timeout on the client wait call and handle timeout exceptions gracefully.

B Keep retrying the request infinitely until a response arrives.

C Ignore timeouts and assume the server will always respond eventually.

D Use a blocking call without timeout to simplify code.

💡 Hint

Think about how to avoid hanging the client indefinitely.

Setting a timeout prevents the client from waiting forever. Handling timeout exceptions allows the client to retry or fail gracefully.