Client metrics monitoring in Kafka - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Kafka Consumer Lag Metric Output

You run the command to check consumer lag for a Kafka consumer group:

kafka-consumer-groups.sh --bootstrap-server localhost:9092 --describe --group my-group

What output indicates the consumer is fully caught up with the latest messages?

A PARTITION 0 CURRENT-OFFSET 100 LAG 0

B PARTITION 0 CURRENT-OFFSET 90 LAG 10

C PARTITION 0 CURRENT-OFFSET 100 LAG 10

D PARTITION 0 CURRENT-OFFSET 90 LAG 0

💡 Hint

Lag of zero means the consumer has processed all messages.

The lag value shows how many messages the consumer is behind. A lag of 0 means it is fully caught up.

🧠 Conceptual

intermediate

Purpose of Kafka Client Metrics

What is the main purpose of monitoring Kafka client metrics in a production environment?

A To backup Kafka topics to external storage

B To encrypt messages between clients and brokers

C To detect client performance issues and message processing delays

D To increase the number of Kafka brokers automatically

💡 Hint

Think about what client metrics help you understand about your application.

Client metrics help identify delays, errors, and throughput issues in message consumption or production.

❓ Troubleshoot

advanced

Troubleshooting Kafka Producer Throughput Drop

You notice a sudden drop in Kafka producer throughput. Which client metric is the best indicator to check first?

A record-send-rate

B fetch-latency-avg

C records-consumed-rate

D request-latency-max

💡 Hint

Look for metrics related to how fast the producer sends messages.

The record-send-rate metric shows how many records the producer sends per second, directly reflecting throughput.

🔀 Workflow

advanced

Setting Up Kafka Client Metrics Exporter

Which sequence correctly describes setting up a Kafka client metrics exporter for Prometheus monitoring?

A 3,1,2,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about enabling metrics first, then exporting, then scraping, then visualization.

First enable JMX metrics in the client, then attach the exporter, then configure Prometheus to scrape, finally visualize.

✅ Best Practice

expert

Best Practice for Kafka Client Metrics Retention

What is the best practice for retaining Kafka client metrics data in a monitoring system?

A Store all metrics data indefinitely for full historical analysis

B Keep metrics data for a short period (days) to reduce storage and focus on recent trends

C Delete metrics data immediately after collection to save space

D Only store metrics data when errors occur

💡 Hint

Think about balancing storage cost and usefulness of data.

Keeping metrics for a short period allows trend analysis without excessive storage use.