Message brokers (Kafka, RabbitMQ) in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Message Broker Roles

Which of the following best describes the primary role of a message broker like Kafka or RabbitMQ in a microservices architecture?

A It facilitates asynchronous communication by routing messages between services.

B It directly processes user requests and returns responses synchronously.

C It stores large files and serves them to clients on demand.

D It manages database transactions and ensures ACID compliance.

💡 Hint

Think about how services talk to each other without waiting for immediate replies.

Message brokers enable services to send messages asynchronously, decoupling the sender and receiver. This improves scalability and fault tolerance.

❓ Architecture

intermediate

Choosing Between Kafka and RabbitMQ

You need to design a system that processes a high volume of streaming data with strict ordering guarantees. Which message broker is more suitable and why?

A Kafka, because it is optimized for high-throughput, ordered, and durable event streaming.

B Kafka, because it uses push-based delivery to consumers for low latency.

C RabbitMQ, because it stores messages on disk for long-term archival.

D RabbitMQ, because it supports complex routing and flexible message patterns.

💡 Hint

Consider which broker is designed for streaming large volumes of ordered data efficiently.

Kafka is designed for high-throughput, ordered event streaming with durable storage, making it ideal for streaming data pipelines.

❓ scaling

advanced

Scaling Message Brokers for High Availability

Which approach best ensures high availability and fault tolerance in a Kafka cluster?

A Use RabbitMQ instead because Kafka cannot replicate data.

B Use multiple Kafka brokers with replication factor greater than one for each partition.

C Deploy a single Kafka broker with multiple partitions on one server.

D Disable replication and rely on client retries to handle failures.

💡 Hint

Think about how Kafka keeps copies of data to survive broker failures.

Kafka achieves high availability by replicating partitions across multiple brokers. If one broker fails, replicas serve the data.

❓ tradeoff

advanced

Tradeoffs Between Push and Pull Messaging Models

RabbitMQ uses a push model to deliver messages to consumers, while Kafka uses a pull model. What is a key tradeoff of the pull model used by Kafka?

A Pull model reduces consumer control over message flow, causing overload.

B Pull model increases latency because consumers must request messages actively.

C Pull model allows consumers to control consumption rate, improving backpressure handling.

D Pull model requires brokers to maintain consumer state, increasing complexity.

💡 Hint

Consider how consumers manage message flow and avoid being overwhelmed.

Kafka's pull model lets consumers fetch messages at their own pace, enabling better handling of slow consumers and backpressure.

❓ estimation

expert

Estimating Kafka Cluster Capacity

You expect to handle 30,000 messages per second, each 1 KB in size, with a replication factor of 3 and retention of 7 days. Approximately how much storage capacity (in TB) should your Kafka cluster have to store all replicas?

A About 18 TB

B About 1.8 TB

C About 378 TB

D About 54 TB

💡 Hint

Calculate total data per day, multiply by retention days and replication factor, then convert to TB.

30,000 messages/sec × 1 KB = 30 MB/sec (≈0.03 GB/sec). Per day: 0.03 GB/sec × 86,400 sec ≈ 2.6 TB raw data. With replication factor 3: 2.6 × 3 ≈ 7.8 TB/day. For 7 days retention: 7.8 × 7 ≈ 54 TB total storage for all replicas.

Practice

1. What is the primary role of a message broker like Kafka or RabbitMQ in a microservices architecture?

easy

A. To store large amounts of user data permanently

B. To enable services to communicate asynchronously by passing messages

C. To replace the database in microservices

D. To directly execute business logic in services

Solution

1. Step 1: Understand message broker function

   Message brokers act as middlemen that help services send and receive messages without waiting for each other.

2. Step 2: Identify correct role in microservices

   They enable asynchronous communication, improving scalability and fault tolerance.

3. Final Answer:

   To enable services to communicate asynchronously by passing messages -> Option B

4. Quick Check:

   Message broker = asynchronous communication [OK]

Hint: Message brokers pass messages between services asynchronously [OK]

Common Mistakes:

• Confusing brokers with databases
• Thinking brokers execute business logic
• Assuming brokers store permanent user data

2. Which of the following is the correct way to declare a RabbitMQ queue in code?

easy

A. channel.queueDeclare('task_queue', true, false, false, null);

B. channel.createQueue('task_queue', durable=true);

C. queue.declare('task_queue', persistent=True);

D. rabbitmq.queue('task_queue', durable=True);

Solution

1. Step 1: Recall RabbitMQ queue declaration syntax

   In RabbitMQ Java client, channel.queueDeclare is used with parameters: queue name, durable, exclusive, autoDelete, and arguments.

2. Step 2: Match correct syntax

   channel.queueDeclare('task_queue', true, false, false, null); matches the official method signature and parameter order correctly.

3. Final Answer:

   channel.queueDeclare('task_queue', true, false, false, null); -> Option A

4. Quick Check:

   RabbitMQ queueDeclare syntax = channel.queueDeclare('task_queue', true, false, false, null); [OK]

Hint: Remember RabbitMQ uses channel.queueDeclare with 5 parameters [OK]

Common Mistakes:

• Using incorrect method names like createQueue
• Passing parameters with wrong names or order
• Confusing RabbitMQ syntax with other brokers

3. Given the following Kafka consumer code snippet, what will be the output if the topic has 3 messages and auto-commit is enabled?

consumer.subscribe(['orders'])
for message in consumer.poll(timeout_ms=1000).values():
    print(message.value.decode('utf-8'))

medium

A. Prints nothing because poll returns a dict of lists

B. Prints only the first message and stops

C. Prints all 3 messages from the 'orders' topic

D. Raises an error due to wrong method usage

Solution

1. Step 1: Analyze Kafka consumer.poll() return type

   The poll() method returns a dictionary where keys are partitions and values are lists of messages.

2. Step 2: Understand iteration over poll().values()

   Iterating over values() gives lists of messages, not individual messages, so calling message.value will cause an error because message is a list, not a message object.

3. Final Answer:

   Raises an error due to wrong method usage -> Option D

4. Quick Check:

   poll() returns dict of lists; iterating directly over values and accessing message.value causes error [OK]

Hint: poll() returns dict of lists, not single messages [OK]

Common Mistakes:

• Assuming poll() returns a flat list of messages
• Not decoding message values properly
• Ignoring that poll() returns per-partition batches

4. A developer wrote this RabbitMQ consumer code but it never receives messages:

channel.basicConsume('task_queue', autoAck=False, callback=process_message)

What is the likely issue?

medium

A. The consumer must call channel.start_consuming() to begin receiving messages

B. The callback function name should be 'on_message' instead of 'process_message'

C. autoAck must be set to True for messages to be received

D. The queue name 'task_queue' is invalid and must be changed

Solution

1. Step 1: Understand RabbitMQ consumer lifecycle

   After setting up basicConsume, the consumer must start the event loop with channel.start_consuming() to receive messages.

2. Step 2: Identify missing call

   The code lacks start_consuming(), so no messages are delivered.

3. Final Answer:

   The consumer must call channel.start_consuming() to begin receiving messages -> Option A

4. Quick Check:

   Missing start_consuming() = The consumer must call channel.start_consuming() to begin receiving messages [OK]

Hint: Remember to call start_consuming() after basicConsume [OK]

Common Mistakes:

• Thinking callback function name must be fixed
• Believing autoAck controls message receipt
• Assuming queue name is invalid without evidence

5. You need to design a scalable order processing system using Kafka. Which approach best ensures message order per customer while allowing parallel processing across customers?

hard

A. Use a single Kafka partition for all orders to keep global order

B. Use multiple topics, one per customer, to isolate order streams

C. Partition messages by customer ID so each customer's orders stay ordered in their partition

D. Send all orders to a single consumer instance to maintain order

Solution

1. Step 1: Understand Kafka partitioning and ordering

   Kafka guarantees order only within a partition, so to keep order per customer, messages must be partitioned by customer ID.

2. Step 2: Evaluate options for scalability and ordering

   Partitioning by customer ID allows parallel processing across partitions (customers) while preserving order per customer.

3. Final Answer:

   Partition messages by customer ID so each customer's orders stay ordered in their partition -> Option C

4. Quick Check:

   Partition by key for order + parallelism = Partition messages by customer ID so each customer's orders stay ordered in their partition [OK]

Hint: Partition by customer ID to keep order and scale processing [OK]

Common Mistakes:

• Using single partition limits scalability
• Creating many topics adds unnecessary complexity
• Using single consumer blocks parallelism