Bird
Raised Fist0

You want to create a monitoring dashboard that combines Kafka broker CPU usage and consumer lag to prevent outages. What is the best approach?

hard📝 Workflow Q8 of Q15
Kafka - Monitoring and Operations
You want to create a monitoring dashboard that combines Kafka broker CPU usage and consumer lag to prevent outages. What is the best approach?
ACombine both metrics to detect resource and processing bottlenecks
BMonitor only consumer lag and ignore broker metrics
CMonitor only CPU usage since lag is less important
DUse topic count as a proxy for both CPU and lag
Step-by-Step Solution
Solution:

  1. Step 1: Understand the importance of combined metrics

    CPU usage shows resource stress; consumer lag shows processing delays.

  2. Step 2: Combine metrics for comprehensive monitoring

    Using both helps detect different outage causes early.

  3. Final Answer:

    Combine both metrics to detect resource and processing bottlenecks -> Option A

  4. Quick Check:

    Combined metrics = Better outage prevention [OK]
Quick Trick: Combine CPU and lag metrics for full health view [OK]
Common Mistakes:
MISTAKES
  • Monitoring only one metric
  • Using topic count as a misleading proxy
  • Ignoring resource bottlenecks

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Kafka Connect - Standalone vs distributed mode - Quiz 10hard Kafka Connect - Sink connectors - Quiz 14medium Kafka Streams - Why stream processing transforms data - Quiz 14medium Kafka with Java/Python - Error handling in clients - Quiz 5medium Kafka with Java/Python - Error handling in clients - Quiz 13medium Kafka with Java/Python - Python producer (confluent-kafka) - Quiz 11easy Kafka with Java/Python - Python producer (confluent-kafka) - Quiz 3easy Message Delivery Semantics - Transactional producer - Quiz 10hard Schema Registry - Schema evolution (backward, forward, full) - Quiz 12easy Schema Registry - Schema compatibility rules - Quiz 5medium