Why multi-datacenter ensures availability in Kafka - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the replication factor for a Kafka topic.

Kafka

bin/kafka-topics.sh --create --topic my-topic --partitions 3 --replication-factor [1] --bootstrap-server localhost:9092

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

A3

B0

C1

D5

Attempts:

3 left

💡 Hint

Common Mistakes

Setting replication factor to 1 means no replication, risking data loss.

The replication factor defines how many copies of the data exist across different brokers or datacenters. Setting it to 3 ensures data is replicated in multiple places for availability.

2fill in blank

medium

Complete the code to configure Kafka producer to wait for acknowledgments from all replicas.

Kafka

props.put("acks", "[1]");

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

Aall

B1

C-1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using '1' waits only for the leader, risking data loss if leader fails.

Setting 'acks' to 'all' ensures the producer waits for all replicas to acknowledge the write, improving availability and durability.

3fill in blank

hard

Fix the error in the consumer configuration to enable automatic failover across datacenters.

Kafka

props.put("group.id", "my-group");
props.put("enable.auto.commit", [1]);

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

A"true"

Bfalse

Ctrue

D"false"

Attempts:

3 left

💡 Hint

Common Mistakes

Using string values instead of boolean causes config errors.

Setting 'enable.auto.commit' to true (boolean) allows the consumer to commit offsets automatically, helping with failover and availability.

4fill in blank

hard

Fill both blanks to create a Kafka topic with a replication factor and enable unclean leader election.

Kafka

bin/kafka-topics.sh --create --topic logs --partitions 5 --replication-factor [1] --config [2]=true --bootstrap-server localhost:9092

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

A3

B1

Cunclean.leader.election.enable

Dmin.insync.replicas

Attempts:

3 left

💡 Hint

Common Mistakes

Using replication factor 1 disables replication.

Replication factor 3 ensures data is on multiple brokers. Enabling 'unclean.leader.election.enable' allows leader election even if some replicas are out of sync, improving availability but risking data loss.

5fill in blank

hard

Fill all three blanks to configure a Kafka consumer to read from multiple datacenters with failover.

Kafka

props.put("bootstrap.servers", "[1]");
props.put("group.id", "[2]");
props.put("auto.offset.reset", "[3]");

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

Adc1.kafka.local:9092,dc2.kafka.local:9092

Bmulti-dc-group

Cearliest

Dlatest

Attempts:

3 left

💡 Hint

Common Mistakes

Using only one datacenter in bootstrap servers limits availability.

Setting bootstrap servers to multiple datacenters allows failover. Group id identifies the consumer group. 'auto.offset.reset' to 'earliest' ensures the consumer reads from the beginning if no offset is found.

Practice

1. Why does using multiple datacenters in Kafka improve availability?

easy

A. Because if one datacenter fails, others can continue serving data

B. Because it reduces the total amount of data stored

C. Because it makes Kafka run faster on a single machine

D. Because it removes the need for data replication

Solution

1. Step 1: Understand what availability means in Kafka

   Availability means Kafka can keep working and serving data even if some parts fail.

2. Step 2: Explain how multiple datacenters help availability

   By having data in multiple datacenters, if one datacenter goes down, others still have the data and keep Kafka running.

3. Final Answer:

   Because if one datacenter fails, others can continue serving data -> Option A

4. Quick Check:

   Multi-datacenter = High availability [OK]

Hint: Think: backup locations keep service running [OK]

Common Mistakes:

• Confusing availability with performance
• Thinking multi-datacenter reduces data size
• Believing replication is not needed

2. Which Kafka configuration option is essential for multi-datacenter replication?

easy

A. log.retention.hours

B. replication.factor

C. auto.offset.reset

D. max.poll.records

Solution

1. Step 1: Identify replication-related Kafka settings

   Replication factor controls how many copies of data Kafka keeps across brokers and datacenters.

2. Step 2: Match replication.factor to multi-datacenter replication

   Setting replication.factor > 1 ensures data is copied to multiple brokers, enabling multi-datacenter setups.

3. Final Answer:

   replication.factor -> Option B

4. Quick Check:

   Replication setting = replication.factor [OK]

Hint: Replication needs replication.factor set > 1 [OK]

Common Mistakes:

• Choosing unrelated config options
• Confusing offset or polling settings with replication
• Ignoring replication factor importance

3. Given this simplified Kafka setup code snippet, what happens if datacenter1 goes down?

clusters = {"datacenter1": ["broker1", "broker2"], "datacenter2": ["broker3", "broker4"]}
replication_factor = 2

# Messages are replicated across datacenters
messages = ["msg1", "msg2"]

# Simulate datacenter1 goes down
del clusters["datacenter1"]

# Consumer reads from datacenter2 if datacenter1 fails
consumer_datacenter = "datacenter2" if "datacenter1" not in clusters else "datacenter1"
print(f"Consumer reads from {consumer_datacenter}")

medium

A. Consumer reads from datacenter2

B. Consumer reads from datacenter1

C. Consumer reads from both datacenters simultaneously

D. Consumer fails to read any data

Solution

1. Step 1: Understand the condition for consumer_datacenter

   The code sets consumer_datacenter to datacenter2 if datacenter1 is missing from clusters.

2. Step 2: Analyze what happens if datacenter1 goes down

   If datacenter1 is removed or down, it won't be in clusters, so consumer_datacenter becomes datacenter2.

3. Final Answer:

   Consumer reads from datacenter2 -> Option A

4. Quick Check:

   Failover to datacenter2 = Consumer reads datacenter2 [OK]

Hint: Check condition for datacenter presence in clusters [OK]

Common Mistakes:

• Assuming consumer always reads datacenter1
• Thinking consumer reads both datacenters at once
• Ignoring the if condition logic

4. This Kafka multi-datacenter replication code has a bug. What is it?

def replicate_message(message, datacenters):
    for dc in datacenters:
        if dc == "primary":
            continue
        datacenters[dc].append(message)

clusters = {"primary": [], "backup": []}
replicate_message("hello", clusters)
print(clusters)

medium

A. It causes an infinite loop

B. It tries to append to a string instead of a list

C. It modifies the dictionary keys instead of values

D. It skips replicating to the primary datacenter

Solution

1. Step 1: Review the replicate_message function logic

   The function skips the datacenter named "primary" and only appends message to others.

2. Step 2: Understand the impact of skipping primary

   Skipping primary means the original datacenter does not get the message, which is a bug for replication.

3. Final Answer:

   It skips replicating to the primary datacenter -> Option D

4. Quick Check:

   Skipping primary = Bug in replication [OK]

Hint: Check which datacenters get the message appended [OK]

Common Mistakes:

• Thinking it modifies keys instead of values
• Assuming infinite loop due to for loop
• Confusing list and string types

5. You want to design a Kafka system that stays available worldwide even if one datacenter fails. Which approach best ensures this?

hard

A. Store all data only in one datacenter and back it up manually

B. Use a single datacenter with very powerful brokers

C. Replicate data asynchronously between multiple datacenters with automatic failover

D. Disable replication to reduce network traffic

Solution

1. Step 1: Understand the goal of worldwide availability

   Worldwide availability means users anywhere can access Kafka even if one datacenter fails.

2. Step 2: Evaluate options for multi-datacenter setup

   Replicating data asynchronously between datacenters with automatic failover ensures data is copied and clients switch to healthy datacenters.

3. Final Answer:

   Replicate data asynchronously between multiple datacenters with automatic failover -> Option C

4. Quick Check:

   Multi-datacenter replication + failover = High availability [OK]

Hint: Choose replication plus failover for availability [OK]

Common Mistakes:

• Thinking one powerful datacenter is enough
• Ignoring automatic failover importance
• Disabling replication reduces availability