Kafka Monitoring (JMX/Prometheus) — Concept Check
Questions on Kafka Monitoring (JMX/Prometheus). Key metrics: under-replicated partitions, offline partitions, consumer group lag, request latency, and network throughput — export via JMX exporter to Prometheus/Grafana.
Questions in this quiz
8 questions on Kafka Monitoring (JMX/Prometheus) — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A Kafka cluster's under-replicated partitions metric is consistently greater than 0. What does this indicate?
- AThere is a risk of data loss due to replicas being out of sync.
- BThe Kafka brokers are experiencing high request latency.
- CThe active controller count is incorrect.
- DThe consumer group lag is increasing.
2.You notice the Kafka offline partitions metric is greater than 0. What immediate action should you take?
- AIncrease the consumer group lag monitoring frequency.
- BAdjust the JMX exporter settings.
- CInvestigate the cause of partition unavailability to restore access.
- DAdd more brokers to the Kafka cluster.
3.A consumer group shows unbounded lag growth. What does this suggest about the consumer's performance?
- AThe JMX exporter is not functioning correctly.
- BThe Kafka broker is misconfigured.
- CThe consumer is unable to keep up with the producer's data rate.
- DThe consumer has achieved optimal performance.
4.What is the significance of the active controller count metric being exactly 1 in a Kafka cluster?
- AIt confirms that request latency is within acceptable limits.
- BIt indicates that all partitions are online.
- CIt ensures there is no split-brain scenario in the cluster.
- DIt shows that the consumer group lag is under control.
5.You are setting up JMX exporter for Kafka. Which port should you configure it to expose metrics on?
- A9090
- B8080
- C9092
- D9404
6.A Kafka consumer group shows a lag of 5000. What does this mean?
- AThe consumer is ahead by 5000 messages.
- BThe Kafka broker has 5000 under-replicated partitions.
- CThe consumer is 5000 messages behind the producer.
- DThe active controller count is incorrect.
7.Which tool can you use to check consumer group lag in Kafka?
- Akafka-consumer-groups.sh
- Bkafka.yaml
- Cjmx_prometheus_javaagent
- Dvmstat
8.A Kafka cluster's request latency metric shows high values. What might be the impact?
- AIncreased latency can lead to slower message processing and potential consumer lag.
- BIt means the active controller count is incorrect.
- CHigh latency suggests that under-replicated partitions are increasing.
- DHigh request latency indicates more offline partitions.