Why monitoring prevents outages in Kafka - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Kafka consumer that subscribes to a topic.

Kafka

consumer.subscribe([[1]])

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

A"my_topic"

Bmy_topic

Ctopic_name

D"topic"

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the topic name

Passing a variable without quotes

The subscribe method requires a list of topic names as strings. So the topic name must be in quotes inside a list.

2fill in blank

medium

Complete the code to set the consumer group id for Kafka monitoring.

Kafka

consumer_config = {"group.id": [1]

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

A"monitoring_group"

B123

Cmonitoring_group

Dgroup1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a number without quotes

Using an undefined variable

The group.id must be a string, so it needs quotes.

3fill in blank

hard

Fix the error in the code to poll messages from Kafka with a timeout of 1 second.

Kafka

msg = consumer.poll(timeout_ms=[1])

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

A1

B1000

C1.0

D"1s"

Attempts:

3 left

💡 Hint

Common Mistakes

Using seconds as float or string

Using 1 instead of 1000

The poll method expects timeout_ms in milliseconds as an integer, so 1000 means 1 second.

4fill in blank

hard

Fill both blanks to configure Kafka consumer to auto-commit offsets and set auto offset reset to earliest.

Kafka

consumer_config = {"enable.auto.commit": [1], "auto.offset.reset": [2]

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

ATrue

BFalse

C"earliest"

D"latest"

Attempts:

3 left

💡 Hint

Common Mistakes

Setting auto commit to False

Using 'latest' instead of 'earliest'

To auto-commit offsets, enable.auto.commit must be True. To start from the earliest message if no offset is found, auto.offset.reset must be 'earliest'.

5fill in blank

hard

Complete the code to create a dictionary comprehension that maps topic partitions to their current offsets if the offset is greater than 0.

Kafka

offsets = {partition: offset for partition, offset in offsets_dict.items() if offset [1] 0}

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

A.partition

C>

D>=

Attempts:

3 left

💡 Hint

Common Mistakes

Adding .partition or .offset incorrectly

Using '>=' instead of '>'

The dictionary keys and values are partition and offset directly, so no extra attribute is needed. The condition checks if offset is greater than 0.

Practice

1. Why is monitoring Kafka important to prevent outages?

easy

A. It helps detect problems early before they cause failures.

B. It automatically fixes all Kafka bugs without human help.

C. It slows down Kafka to reduce load on the system.

D. It deletes old data to free up disk space.

Solution

1. Step 1: Understand the role of monitoring

   Monitoring tracks Kafka's health and performance to spot issues early.

2. Step 2: Connect monitoring to outage prevention

   Early detection allows quick fixes, preventing outages from happening.

3. Final Answer:

   It helps detect problems early before they cause failures. -> Option A

4. Quick Check:

   Monitoring = Early problem detection [OK]

Hint: Monitoring alerts you before outages happen [OK]

Common Mistakes:

• Thinking monitoring fixes problems automatically
• Believing monitoring slows down Kafka
• Confusing monitoring with data deletion

2. Which Kafka command helps check the status of brokers to monitor their health?

easy

A. kafka-topics.sh --list

B. kafka-consumer-groups.sh --describe

C. kafka-broker-api-versions.sh --bootstrap-server localhost:9092

D. kafka-console-producer.sh --broker-list localhost:9092

Solution

1. Step 1: Identify commands related to broker status

   kafka-broker-api-versions.sh shows broker API versions and connectivity, useful for health checks.

2. Step 2: Compare other commands

   Other commands list topics, produce messages, or describe consumer groups, not broker health.

3. Final Answer:

   kafka-broker-api-versions.sh --bootstrap-server localhost:9092 -> Option C

4. Quick Check:

   Broker status command = kafka-broker-api-versions.sh [OK]

Hint: Broker health check uses kafka-broker-api-versions.sh [OK]

Common Mistakes:

• Using kafka-topics.sh which lists topics, not brokers
• Confusing producer or consumer commands with monitoring
• Missing the --bootstrap-server option

3. Given this command output snippet from Kafka monitoring, what does it indicate?

Partition 0 Leader: 1
Partition 0 ISR: 1,2
Partition 1 Leader: 2
Partition 1 ISR: 2

medium

A. Partition 1 has no in-sync replicas, risking data loss.

B. All partitions have healthy leaders and in-sync replicas.

C. Partition 0 leader is down because ISR is missing.

D. Kafka cluster has no active brokers.

Solution

1. Step 1: Understand Leader and ISR meaning

   Leader is the broker handling writes; ISR (in-sync replicas) are replicas up to date with leader.

2. Step 2: Analyze the output

   Partition 0 leader is broker 1 with ISR 1 and 2, both in sync. Partition 1 leader is 2 with ISR 2, also in sync.

3. Final Answer:

   All partitions have healthy leaders and in-sync replicas. -> Option B

4. Quick Check:

   Leader and ISR present = healthy partitions [OK]

Hint: Leader and ISR presence means healthy partitions [OK]

Common Mistakes:

• Assuming missing ISR means leader down
• Confusing ISR with offline replicas
• Ignoring that leader IDs are shown

4. You see this alert from Kafka monitoring: Under-replicated partitions detected. What is the most likely cause?

medium

A. All brokers are offline.

B. Kafka topics have no partitions configured.

C. Kafka consumer groups are lagging behind.

D. Some replicas are not catching up with the leader.

Solution

1. Step 1: Understand under-replicated partitions

   This alert means some replicas are behind the leader and not fully synced.

2. Step 2: Eliminate other options

   No partitions or all brokers offline would cause different alerts; consumer lag is unrelated.

3. Final Answer:

   Some replicas are not catching up with the leader. -> Option D

4. Quick Check:

   Under-replicated = replicas behind leader [OK]

Hint: Under-replicated means replicas lag leader [OK]

Common Mistakes:

• Confusing consumer lag with replica lag
• Thinking no partitions cause this alert
• Assuming all brokers are offline

5. You want to set up monitoring to prevent Kafka outages. Which combination of metrics and alerts is best to catch problems early?

hard

A. Monitor broker CPU usage, under-replicated partitions, and consumer lag with alerts on thresholds.

B. Only monitor topic creation commands to track new topics.

C. Alert only when Kafka brokers restart, ignoring other metrics.

D. Monitor disk space on unrelated servers without Kafka metrics.

Solution

1. Step 1: Identify key Kafka health metrics

   Broker CPU, under-replicated partitions, and consumer lag indicate system load, replication health, and consumption delays.

2. Step 2: Understand alerting importance

   Alerts on thresholds help catch issues early before outages occur.

3. Step 3: Evaluate other options

   Only monitoring topic creation or broker restarts misses many problems; unrelated server metrics don't help Kafka health.

4. Final Answer:

   Monitor broker CPU usage, under-replicated partitions, and consumer lag with alerts on thresholds. -> Option A

5. Quick Check:

   Comprehensive metrics + alerts = best outage prevention [OK]

Hint: Combine key metrics with alerts for early problem detection [OK]

Common Mistakes:

• Monitoring only one metric or event
• Ignoring consumer lag or replication health
• Tracking unrelated server metrics