Certified Developer for Apache Kafka · 15% of the exam

Application Observability: free practice questions

5 sample questions from our 12-question bank for this domain — answers and explanations included. These are the same scenario-based style as the real Confluent exam.

1. What does distributed TRACING add to observability of an event-driven pipeline built on Kafka?

  • A. End-to-end visibility of how a message flows and is transformed across producers, topics, and consumers, revealing latency and bottlenecks✓ Correct
  • B. It stores the messages permanently
  • C. It replaces the need for metrics and logs
  • D. It changes the topic's replication factor
Explanation

Distributed tracing follows a message/transaction across services and Kafka hops, exposing where latency accrues and where failures occur end-to-end. It doesn't store messages (B), replace metrics/logs (C) — the three are complementary — or alter replication (D).

2. Which metric helps determine whether a consumer is committing offsets successfully and not repeatedly reprocessing the same records?

  • A. Commit rate / commit latency metrics (and stable committed offsets advancing over time)✓ Correct
  • B. The producer's compression type
  • C. The number of brokers
  • D. The Schema Registry's port number
Explanation

Offset commit metrics (rate, latency) and advancing committed offsets show that a consumer is committing progress and not stuck reprocessing. Compression type (B), broker count (C), and Schema Registry port (D) don't reflect commit health.

3. Kafka clients (producers, consumers, Streams) expose runtime metrics primarily through which mechanism?

  • A. JMX (Java Management Extensions) metrics✓ Correct
  • B. The Schema Registry API
  • C. S3 access logs
  • D. DNS records
Explanation

Kafka clients expose metrics via JMX, which monitoring systems scrape (often through exporters) for throughput, latency, and lag. The Schema Registry API (B) serves schemas, S3 logs (C) and DNS (D) are unrelated to client metrics.

4. What does CONSUMER LAG measure in a Kafka application?

  • A. The difference between the latest offset produced to a partition and the consumer's committed offset (how far behind the consumer is)✓ Correct
  • B. The network round-trip time between brokers
  • C. The number of partitions in a topic
  • D. The producer's batch size
Explanation

Consumer lag is the gap between the log-end offset (latest produced) and the consumer's committed offset per partition — a key indicator of whether consumers are keeping up. It's not broker network latency (B), partition count (C), or producer batch size (D).

5. A team wants to alert when consumer lag exceeds a threshold for a critical consumer group. What should they set up?

  • A. A metric-based alert on consumer lag (e.g., via a monitoring system consuming JMX/exporter metrics)✓ Correct
  • B. A manual daily check by an engineer
  • C. A change to the topic's retention only
  • D. Disabling the consumer group
Explanation

Automated, metric-based alerting on consumer lag notifies the team promptly when consumers fall behind a threshold. Manual daily checks (B) are slow and error-prone, changing retention (C) doesn't monitor lag, and disabling the group (D) stops processing.

7 more questions in this domain

Practice the full bank with instant grading, flashcards, and a timed mock exam.

Start practicing free