Why Kafka exists - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why was Kafka created?

Kafka was created to solve which main problem in data systems?

A To provide a distributed messaging system that can handle high throughput and fault tolerance

B To replace traditional relational databases with a new query language

C To create a user interface for managing cloud resources

D To serve as a web server for hosting websites

💡 Hint

Think about what kind of data flow Kafka is designed to support.

Kafka was designed as a distributed messaging system to handle large volumes of data with high speed and reliability.

❓ Predict Output

intermediate

Kafka Producer Message Delivery

What will be the output when a Kafka producer sends a message with acks=all?

Kafka

producer.send('topic1', b'message').get()  # with acks='all'

A The producer waits for all replicas to acknowledge before confirming the send

B The producer sends the message without waiting for any acknowledgment

C The producer retries sending the message indefinitely without acknowledgment

D The producer waits only for the leader broker to acknowledge

💡 Hint

Consider what acks=all means for message durability.

Setting acks=all means the producer waits for all in-sync replicas to confirm the message, ensuring durability.

❓ Predict Output

advanced

Kafka Consumer Offset Behavior

What happens if a Kafka consumer commits an offset that is higher than the last message in the partition?

Kafka

consumer.commit(offset=1000)  # when last message offset is 900

A The consumer will throw an OffsetOutOfRangeException immediately

B The consumer will read messages starting from offset 900 instead

C The consumer will reset to offset 0 automatically

D The consumer will start reading from offset 1000, which does not exist, causing it to wait for new messages

💡 Hint

Think about how Kafka handles offsets beyond the current log end.

If the committed offset is beyond the last message, the consumer waits for new messages at that offset.

🧠 Conceptual

advanced

Kafka's Role in Event-Driven Architectures

Why is Kafka often used as the backbone in event-driven architectures?

A Because it automatically generates user interfaces for events

B Because it stores data in relational tables for easy querying

C Because it provides a scalable, fault-tolerant, and durable event streaming platform

D Because it replaces all microservices with a single monolithic app

💡 Hint

Consider Kafka's strengths in handling streams of data reliably.

Kafka is used in event-driven systems because it can handle large streams of events reliably and scale easily.

🧠 Conceptual

expert

Kafka's Partitioning and Scalability

How does Kafka achieve horizontal scalability and parallel processing?

A By using a centralized database to manage all messages

B By dividing topics into partitions that can be distributed across multiple brokers

C By limiting the number of consumers to one per topic

D By storing all data in a single broker to avoid network overhead

💡 Hint

Think about how Kafka spreads workload to handle more data.

Kafka splits topics into partitions, allowing multiple brokers and consumers to work in parallel, increasing scalability.