Redis as message broker in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a Django app publishes a message to Redis?

Consider a Django app configured to use Redis as a message broker. When the app publishes a message to a Redis channel, what is the expected behavior?

A The message is sent to all clients subscribed to that Redis channel immediately.

B The message is stored in Redis and delivered only when the subscriber requests it.

C The message is saved in a Redis list and requires manual polling to retrieve.

D The message is lost if no subscriber is connected at the time of publishing.

💡 Hint

Think about how Redis Pub/Sub works with subscribers.

Redis Pub/Sub delivers messages instantly to all connected subscribers of the channel. If no subscriber is connected, the message is not stored or queued.

📝 Syntax

intermediate

Identify the correct Redis publish command in Django using redis-py

Which of the following code snippets correctly publishes a message to a Redis channel named 'notifications' using the redis-py client in Django?

A redis_client.publish_message('notifications', 'New user signed up')

B redis_client.send('notifications', 'New user signed up')

C redis_client.push('notifications', 'New user signed up')

D redis_client.publish('notifications', 'New user signed up')

💡 Hint

Check the redis-py documentation for the method to send messages to a channel.

The correct method to publish a message to a Redis channel using redis-py is publish. Other methods do not exist or serve different purposes.

🔧 Debug

advanced

Why does the Redis subscriber in Django not receive messages?

A Django app subscribes to a Redis channel but never receives messages published to that channel. Which of the following is the most likely cause?

A The subscriber is using a blocking call that prevents message processing.

B The subscriber did not call the <code>subscribe</code> method before listening.

C The Redis server is configured to reject all Pub/Sub messages.

D The published messages are too large and get dropped silently.

💡 Hint

Check the subscriber setup steps carefully.

If the subscriber does not call subscribe on the Redis client, it will not receive any messages from the channel.

❓ state_output

advanced

What is the state of Redis after publishing messages with no subscribers?

If a Django app publishes messages to a Redis channel but no clients are subscribed at that moment, what happens to those messages in Redis?

A Messages are discarded immediately and not stored anywhere.

B Messages are stored in a Redis list for later retrieval.

C Messages are saved in Redis memory until a subscriber connects.

D Messages cause Redis to throw an error due to no subscribers.

💡 Hint

Think about Redis Pub/Sub message persistence.

Redis Pub/Sub does not store messages if no subscribers are connected. Messages are discarded immediately.

🧠 Conceptual

expert

Why choose Redis as a message broker in Django over other brokers?

Which of the following reasons best explains why a developer might choose Redis as a message broker for a Django app?

A Redis guarantees message delivery persistence and complex routing like RabbitMQ.

B Redis automatically scales horizontally without any configuration.

C Redis offers fast in-memory message delivery with simple Pub/Sub and supports lightweight task queues.

D Redis supports only synchronous message processing, which simplifies debugging.

💡 Hint

Consider Redis strengths and limitations compared to other brokers.

Redis is known for fast in-memory operations and simple Pub/Sub, making it suitable for lightweight messaging and task queues. It does not guarantee persistence or complex routing like RabbitMQ.