Why distributed architecture ensures reliability in Kafka - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Kafka producer that sends messages to a topic.

Kafka

producer = KafkaProducer(bootstrap_servers='localhost:9092')
producer.send('[1]', b'Hello Kafka')
producer.flush()

Drag options to blanks, or click blank then click option'

Alocalhost

Bmessage_topic

Ckafka_server

Dmy_topic

Attempts:

3 left

💡 Hint

Common Mistakes

Using server names instead of topic names in the send method.

The send method requires the topic name as the first argument. Here, my_topic is the correct topic name.

2fill in blank

medium

Complete the code to consume messages from a Kafka topic.

Kafka

consumer = KafkaConsumer('[1]', bootstrap_servers='localhost:9092')
for message in consumer:
    print(message.value)

Drag options to blanks, or click blank then click option'

Aserver

Bmy_topic

Cconsumer_group

Dlocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Using server or group names instead of topic names.

The consumer needs the topic name to subscribe to messages. my_topic is the correct topic name.

3fill in blank

hard

Fix the error in the code to ensure the Kafka consumer joins the correct consumer group.

Kafka

consumer = KafkaConsumer('my_topic', bootstrap_servers='localhost:9092', group_id=[1])
for message in consumer:
    print(message.value)

Drag options to blanks, or click blank then click option'

A'my_group'

B123

CNone

Dlocalhost

Attempts:

3 left

💡 Hint

Common Mistakes

Passing None or numbers instead of a string for group_id.

The group_id must be a string identifying the consumer group, like 'my_group'.

4fill in blank

hard

Fill both blanks to create a Kafka topic with 3 partitions and a replication factor of 2.

Kafka

topic_config = NewTopic(name='my_topic', num_partitions=[1], replication_factor=[2])

Drag options to blanks, or click blank then click option'

A3

B1

C2

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Using replication factor 1 which does not provide redundancy.

The topic needs 3 partitions and a replication factor of 2 to ensure reliability through distribution.

5fill in blank

hard

Fill all three blanks to configure a Kafka producer with retries, acks, and a timeout for reliability.

Kafka

producer = KafkaProducer(bootstrap_servers='localhost:9092', retries=[1], acks=[2], request_timeout_ms=[3])

Drag options to blanks, or click blank then click option'

A0

B'all'

C30000

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Setting retries to 0 disables retrying.

Using acks=1 or acks=0 reduces reliability.

Retries set to 5 allow resending messages on failure, acks='all' waits for all replicas to confirm, and request_timeout_ms=30000 sets a 30-second timeout for requests.

Practice

1. Why does Kafka use a distributed architecture with multiple brokers?

easy

A. To ensure data is safe and available even if some machines fail

B. To make the system slower and less efficient

C. To store all data on a single machine for simplicity

D. To avoid using network communication between machines

Solution

1. Step 1: Understand distributed architecture purpose

   Distributed architecture spreads data and work across many machines to avoid single points of failure.

2. Step 2: Connect to Kafka's design

   Kafka uses multiple brokers so if one fails, others still have data, keeping the system reliable.

3. Final Answer:

   To ensure data is safe and available even if some machines fail -> Option A

4. Quick Check:

   Distributed architecture = reliability [OK]

Hint: Distributed means many machines share work for safety [OK]

Common Mistakes:

• Thinking distributed means slower system
• Believing all data is on one machine
• Ignoring network communication in distributed systems

2. Which Kafka feature directly supports data replication for reliability?

easy

A. Replication factor

B. Topics

C. Partitions

D. Consumer groups

Solution

1. Step 1: Identify Kafka features related to data safety

   Partitions split data, topics organize data, consumer groups read data, replication factor controls copies.

2. Step 2: Match feature to replication

   Replication factor sets how many copies of data exist, ensuring safety if one copy fails.

3. Final Answer:

   Replication factor -> Option A

4. Quick Check:

   Replication factor = copies for safety [OK]

Hint: Replication factor means how many copies exist [OK]

Common Mistakes:

• Confusing partitions with replication
• Thinking consumer groups handle replication
• Assuming topics control replication

3. Given a Kafka topic with 3 partitions and replication factor 2, what happens if one broker fails?

medium

A. Data in partitions on the failed broker is lost permanently

B. All partitions become unavailable until the broker is fixed

C. Kafka automatically switches to replicas on other brokers to keep data available

D. Kafka stops producing new messages until manual intervention

Solution

1. Step 1: Understand replication factor 2 means two copies

   Each partition has two copies on different brokers for safety.

2. Step 2: Analyze broker failure impact

   If one broker fails, the other copy still exists, so Kafka switches to it automatically.

3. Final Answer:

   Kafka automatically switches to replicas on other brokers to keep data available -> Option C

4. Quick Check:

   Replication ensures availability despite failures [OK]

Hint: Replication factor 2 means one copy survives failure [OK]

Common Mistakes:

• Assuming data is lost immediately on failure
• Thinking Kafka stops all activity on failure
• Believing manual fix is always needed

4. Look at this Kafka configuration snippet:

replication.factor=1
num.partitions=3

What is the main reliability issue here?

medium

A. Partitions cannot be more than replication factor

B. Having 3 partitions causes data duplication

C. The configuration syntax is incorrect

D. Replication factor 1 means no data copies, risking data loss if a broker fails

Solution

1. Step 1: Understand replication factor meaning

   Replication factor 1 means only one copy of data exists, no backups.

2. Step 2: Identify reliability risk

   If the broker holding data fails, data is lost because no replicas exist.

3. Final Answer:

   Replication factor 1 means no data copies, risking data loss if a broker fails -> Option D

4. Quick Check:

   Replication factor 1 = no backup copies [OK]

Hint: Replication factor 1 means no backups, risky for failures [OK]

Common Mistakes:

• Confusing partitions with replication
• Thinking syntax is wrong
• Believing partitions must be less than replication factor

5. You want to design a Kafka topic to maximize reliability and scalability. Which setup is best?

hard

A. Set replication factor to 1 and partitions to 1

B. Set replication factor to 3 and partitions to 10

C. Set replication factor to 2 and partitions to 1

D. Set replication factor to 1 and partitions to 10

Solution

1. Step 1: Understand replication factor and partitions roles

   Replication factor controls copies for reliability; partitions allow parallelism for scalability.

2. Step 2: Evaluate options for reliability and scalability

   Replication factor 3 means 3 copies for safety; 10 partitions allow many consumers to read in parallel.

3. Final Answer:

   Set replication factor to 3 and partitions to 10 -> Option B

4. Quick Check:

   More replicas + more partitions = reliable and scalable [OK]

Hint: More replicas and partitions improve reliability and speed [OK]

Common Mistakes:

• Choosing low replication factor risking data loss
• Choosing few partitions limiting scalability
• Confusing replication factor with partitions