Certbie

Free practice · No sign-up required

Confluent Certified Administrator for Apache Kafka free practice test

15 questions with answer explanations. Choose an answer below to begin.

Question 1 of 15

What is the primary purpose of a Kafka broker in a distributed streaming platform?

Show hint

Understand core broker responsibilities

0/15 answered · Bookmark questions to review later. Focus the practice area to use keys 1–9 and Enter.

Learn by doing

Put your answers into practice

Use official documentation and hands-on labs to work through topics you missed.

Explore all study resources →

All questions and explanations

Prefer to read at your own pace? Work through each question below, then open its answer to check your reasoning. You can link directly to a question or print this reference.

  1. Question 1

    Link to question

    What is the primary purpose of a Kafka broker in a distributed streaming platform?

    1. To store and serve streams of records

    2. To develop stream processing applications

    3. To define data schemas for messages

    4. To manage user authentication

    Show answer and explanation

    Correct answer

    • To store and serve streams of records

    A Kafka broker is responsible for storing, retrieving, and replicating data streams across the cluster. It does not handle application development, schema definition, or authentication directly.

  2. Question 2

    Link to question

    Which component is responsible for maintaining metadata about topics and broker availability?

    1. Controller

    2. Producer

    3. Consumer

    4. Connector

    Show answer and explanation

    Correct answer

    • Controller

    The Controller broker manages cluster metadata, including topic configurations and leader election. Producers write data, consumers read data, and connectors integrate with external systems.

  3. Question 3

    Link to question

    Which log cleaner policy helps reduce disk usage while preserving recent messages?

    1. Delete retention

    2. Compact retention

    3. Time-based compaction

    4. Size-based compaction

    Show answer and explanation

    Correct answer

    • Compact retention

    Compact retention retains the latest version of each key and removes older duplicates, effectively managing storage for stateful applications. Delete retention removes messages after a time or size threshold.

  4. Question 4

    Link to question

    What is a common prerequisite for safely upgrading a Kafka cluster?

    1. Stop all producers and consumers

    2. Verify broker compatibility matrix

    3. Increase topic partition counts

    4. Disable inter-broker communication

    Show answer and explanation

    Correct answer

    • Verify broker compatibility matrix

    Reviewing the compatibility matrix ensures that new software versions work with existing brokers and clients. Upgrades can often proceed without stopping producers and consumers.

  5. Question 5

    Link to question

    Which configuration property helps control the number of open file handles on a broker?

    1. num.io.threads

    2. num.network.threads

    3. num.replica.fetchers

    4. num.partitions

    Show answer and explanation

    Correct answer

    • num.partitions

    The num.partitions setting influences the number of files and handles the broker manages. While not the only factor, it is closely related to file handle usage on the system.

  6. Question 6

    Link to question

    What is the role of a consumer group in Kafka?

    1. To guarantee message order across all topics

    2. To distribute message consumption among instances

    3. To replicate data between clusters

    4. To authenticate client connections

    Show answer and explanation

    Correct answer

    • To distribute message consumption among instances

    Consumer groups enable multiple consumer instances to share the reading workload for a topic, ensuring each partition is consumed by only one member at a time.

  7. Question 7

    Link to question

    Which action is most likely to cause data unavailability during maintenance?

    1. Adding a new broker to the cluster

    2. Shutting down a broker without pref leader election

    3. Increasing topic retention period

    4. Creating a new consumer group

    Show answer and explanation

    Correct answer

    • Shutting down a broker without pref leader election

    Shutting down a broker abruptly can leave its partitions without leaders until a new leader is elected, causing temporary unavailability. Adding brokers and creating consumer groups do not disrupt availability.

  8. Question 8

    Link to question

    What is a typical use case for compacted topics?

    1. Event sourcing with full history

    2. Configuration or lookup data storage

    3. High-volume raw log ingestion

    4. Long-term archival storage

    Show answer and explanation

    Correct answer

    • Configuration or lookup data storage

    Compacted topics retain the latest value for each key, making them suitable for state-like data such as configurations. Event sourcing and archival typically use delete retention.

  9. Question 9

    Link to question

    Which metric is most useful for detecting under-replicated partitions?

    1. Consumer lag

    2. Active controller count

    3. Under-replicated partitions

    4. Request handler idle ratio

    Show answer and explanation

    Correct answer

    • Under-replicated partitions

    The under-replicated partitions metric directly indicates partitions that do not have the expected number of in-sync replicas. Other metrics reflect different aspects of cluster health.

  10. Question 10

    Link to question

    What is the purpose of min.insync.replicas in a producer configuration?

    1. To guarantee message delivery to all brokers

    2. To ensure a minimum number of replicas acknowledge writes

    3. To limit the number of producers per topic

    4. To throttle consumer fetch rates

    Show answer and explanation

    Correct answer

    • To ensure a minimum number of replicas acknowledge writes

    min.insync.replicas specifies the minimum number of replicas that must acknowledge a write for it to be considered successful, improving durability guarantees.

  11. Question 11

    Link to question

    Which practice supports secure communication between clients and brokers?

    1. Enable plaintext listeners only

    2. Use SSL/TLS for inter-broker and client-broker communication

    3. Share credentials in configuration files

    4. Disable authorization for simplicity

    Show answer and explanation

    Correct answer

    • Use SSL/TLS for inter-broker and client-broker communication

    SSL/TLS encrypts traffic and helps prevent eavesdropping or tampering. Secure deployments should use encrypted listeners and proper credential management.

  12. Question 12

    Link to question

    What is a common symptom of a full disk on a Kafka broker?

    1. Increased consumer group rebalance frequency

    2. Producers receiving 'not leader' errors

    3. Kafka broker log directory read-only warnings

    4. Higher than normal request handler threads

    Show answer and explanation

    Correct answer

    • Kafka broker log directory read-only warnings

    When disk space is exhausted, the broker logs may become read-only and produce warnings. Other errors relate to leadership or configuration issues.

  13. Question 13

    Link to question

    Which configuration helps reduce the impact of a slow consumer on the cluster?

    1. Increase message.timestamp.type

    2. Enable log compaction

    3. Adjust replica.lag.time.max.ms

    4. Set retention.ms to a low value

    Show answer and explanation

    Correct answer

    • Adjust replica.lag.time.max.ms

    Replica lag settings control how far behind a follower replica can be before being considered out of sync. This helps protect the cluster from slow consumers affecting replication.

  14. Question 14

    Link to question

    What is the recommended approach for handling configuration changes across a cluster?

    1. Apply changes directly on each broker

    2. Use dynamic broker configurations where possible

    3. Restart all brokers after any configuration update

    4. Disable dynamic updates to ensure consistency

    Show answer and explanation

    Correct answer

    • Use dynamic broker configurations where possible

    Dynamic configurations allow certain settings to be updated without restarting brokers, reducing operational disruption. Some changes still require restarts.

  15. Question 15

    Link to question

    Which protocol ensures ordered and durable message delivery in Kafka?

    1. UDP-based transmission

    2. Produce request with acknowledgment and log append

    3. Fire-and-forget HTTP POST

    4. Multicast streaming

    Show answer and explanation

    Correct answer

    • Produce request with acknowledgment and log append

    Kafka uses a produce request with leader append and replica acknowledgment to guarantee order and durability.

Read all flashcards

Recall the answer before opening each card.

What is the primary purpose of a Kafka broker?

To store and serve streams of records. It also retrieves and replicates data across the cluster.

Which component manages cluster metadata and leader election?

The Controller broker handles metadata, topic configurations, and leader election for partitions.

Which log cleanup policy retains only the latest value per key?

Compact retention policy removes older duplicates and keeps the latest version per key, reducing disk usage.

What is a prerequisite for upgrading a Kafka cluster safely?

Verify the broker compatibility matrix to ensure new software versions work with existing brokers and clients.

Which configuration closely affects the number of open file handles on a broker?

The num.partitions setting influences file handle usage because each partition corresponds to files on disk.

What is the role of a consumer group in Kafka?

To distribute message consumption among multiple consumer instances, ensuring each partition is consumed by only one member.

Which action most likely causes temporary data unavailability during maintenance?

Shutting down a broker without preferred leader election can leave partitions without leaders until re-election.

What is a typical use case for compacted topics?

Configuration or lookup data storage, where the latest value for each key is needed and old versions can be discarded.

Which metric directly indicates replication health issues?

Under-replicated partitions metric shows partitions that do not have the expected number of in-sync replicas.

What does min.insync.replicas ensure in producer configuration?

It ensures a minimum number of replicas have acknowledged a write before it is considered successful, improving durability.

Which practice secures communication between clients and brokers?

Use SSL/TLS for inter-broker and client-broker communication to encrypt traffic and prevent tampering.

What symptom indicates a full disk on a Kafka broker?

Kafka broker log directory read-only warnings appear when disk space is exhausted.

Which configuration helps protect the cluster from a slow consumer?

Adjust replica.lag.time.max.ms to control how far behind a follower can be before being considered out of sync.

What is the recommended approach for making configuration changes with minimal disruption?

Use dynamic broker configurations where possible, as they allow certain settings to be updated without restarting brokers.

Which protocol ensures ordered and durable message delivery in Kafka?

Produce request with acknowledgment and log append guarantees order and durability through leader append and replica acknowledgment.

What component maintains topic metadata besides the controller?

ZooKeeper (or KRaft metadata quorum in newer versions) stores cluster metadata like topic configurations and broker availability.

How does a producer guarantee that a message is written to multiple replicas?

Set acks=all and min.insync.replicas appropriately; the leader waits for acknowledgment from all in-sync replicas before confirming.

What is the effect of setting cleanup.policy=delete on a topic?

Messages are removed after retention.ms time or retention.bytes size limit, suitable for event logs where old data is expired.

What happens if a producer's acks=all request cannot meet min.insync.replicas?

The producer receives a NotEnoughReplicasException, and the write fails to ensure durability guarantees are not violated.

Why is it important to have a preferred leader election during broker shutdown?

It ensures that partitions for which the shutting down broker is leader are gracefully transferred to other replicas, minimizing downtime.

Active recall deck

Practice Confluent Certified Administrator for Apache Kafka with real flashcards

Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.

20 free cards

Card 1 of 20

1 reviewed this session

Connect the concepts

Your Confluent Certified Administrator for Apache Kafka study mind map

Open a branch to connect a topic with its practice questions and explanations. Use the map to choose your next review topic.

Confluent Certified Administrator for Apache Kafka15 questions in this practice set
Understand core broker responsibilities(1)
Identify cluster coordination roles(1)
Choose appropriate log cleanup strategy(1)
Plan controlled cluster maintenance(1)
Relate broker settings to system resources(1)
Understand consumer group mechanics(1)
Identify risky operational actions(1)
Match topic types to usage patterns(1)
Monitor replication health indicators(1)
Apply producer durability settings(1)
Implement secure networking practices(1)
Troubleshoot storage-related failures(1)
More practice connections(3)
Exam-focused analysis

What this Confluent Certified Administrator for Apache Kafka practice set measures

This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.

Broker Architecture & Cluster Coordination

The practice bank emphasizes the fundamental roles within a Kafka cluster. A broker stores and serves record streams, while the Controller maintains metadata about topics and broker availability. Consumer groups distribute partition consumption among instances to scale read throughput. Understanding these components is critical for diagnosing cluster behavior and planning maintenance.

  • Broker: stores, retrieves, and replicates data streams.
  • Controller: manages cluster metadata and leader election.
  • Consumer group: enables parallel consumption by assigning each partition to one member.

Log Cleanup & Data Retention

Two log retention policies are contrasted: compact retention retains the latest value per key, reducing disk usage for stateful data like configuration lookups. Delete retention removes messages after a time or size threshold. Compacted topics are ideal for keyed state stores, while delete retention suits event logs. Choosing the right policy affects storage efficiency and data availability.

  • Compact retention: keeps latest per key, removes older duplicates.
  • Delete retention: removes messages after threshold (time/size).
  • Compacted topics: used for configuration or lookup data storage.

Operational Safety & Troubleshooting

Safe upgrades require verifying the compatibility matrix to avoid version mismatches. Abruptly shutting down a broker without preferred leader election can cause data unavailability. A full disk triggers read-only log directory warnings. Under-replicated partitions are a key metric for replication health. Dynamic broker configurations allow some changes without broker restarts, reducing disruption.

  • Upgrade prerequisite: verify broker compatibility matrix.
  • Maintenance risk: shutting broker without preferred leader election.
  • Full disk symptom: broker log directory read-only warnings.
  • Replication health metric: under-replicated partitions.
  • Configuration change: use dynamic broker configurations where possible.

Client Communication & Durability Guarantees

Secure communication is enforced via SSL/TLS for inter-broker and client-broker channels. Producer durability is controlled by min.insync.replicas, ensuring a minimum number of replicas acknowledge writes. Ordered and durable delivery relies on produce requests with leader append and replica acknowledgment. Slow consumers can be mitigated by adjusting replica.lag.time.max.ms to protect cluster resources.

  • Security: use SSL/TLS for encrypted communication.
  • Durability: min.insync.replicas ensures minimum replica acknowledgment.
  • Ordered delivery: produce request with log append and acknowledgment.
  • Slow consumer impact: reduce by tuning replica.lag.time.max.ms.

Study workflow

Turn one Confluent Certified Administrator for Apache Kafka attempt into a study plan

  1. 1

    Check for Under-Replicated Partitions

    Monitor the 'Under-replicated partitions' metric in JMX or Confluent Control Center. If non-zero, identify the partitions and the missing replicas. Verify that all in-sync replicas are alive and have sufficient disk space. Resolve by restarting brokers or increasing replication factor if necessary.

  2. 2

    Configure Log Cleanup Policy for a Topic

    Use the kafka-configs.sh script to set cleanup.policy=compact for stateful topics. Verify with kafka-topics.sh --describe. For delete retention, set cleanup.policy=delete and configure retention.ms or retention.bytes. Monitor disk usage to ensure policy effectiveness.

  3. 3

    Perform a Rolling Upgrade Safely

    First, verify the compatibility matrix for your version path. Upgrade one broker at a time: shut it down gracefully using controlled shutdown, install the new version, and restart. Ensure the broker rejoins the cluster and completes leader re-elections before moving to the next.

  4. 4

    Enable Dynamic Broker Configuration

    Use kafka-configs.sh with --bootstrap-server, --entity-type brokers, --entity-name <broker-id>, --alter --add-config to set parameters like log.retention.bytes dynamically. Confirm the change with --describe. Verify that the broker does not restart; only certain configurations are dynamically updatable.

  5. 5

    Set Minimum In-Sync Replicas for a Topic

    For topics requiring strong durability, set min.insync.replicas to at least 2 using kafka-configs.sh or in the server.properties. Must be replicated to enough brokers. Also set producer acks=all to guarantee acknowledgment from that many replicas. Failure to meet min.insync.replicas will result in NotEnoughReplicasException.

FAQ

Questions about this exam practice page

Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.

What is the role of the Controller in Kafka?+

The Controller is a broker elected from the cluster to manage metadata, including topic configurations, partition leader election, and broker membership changes. It ensures cluster coordination without relying on external coordination services.

How does compact retention differ from delete retention?+

Compact retention retains the most recent value for each message key and discards older duplicates, reducing storage for keyed state. Delete retention removes entire messages after a specified time or size threshold, suitable for event logs where key uniqueness is not required.

What causes under-replicated partitions?+

Under-replicated partitions occur when one or more replicas are not in sync with the leader. Common causes include broker failure, network issues, or slow replica fetchers. Monitoring this metric helps detect replication lag or unavailability.

Why is min.insync.replicas important for producer durability?+

min.insync.replicas sets the minimum number of replicas that must acknowledge a write for it to succeed. Combined with acks=all, it prevents data loss when brokers fail, ensuring that the message is durable across at least that many replicas.

What metric is most indicative of a consumer impacting cluster replication?+

The replica.lag.time.max.ms configuration defines how far behind a follower can be before being considered out of sync. If a consumer lags, it may slow down replication and cause under-replicated partitions. Monitoring consumer lag and adjusting this value can protect cluster stability.

Keep studying

Build the next review session

Browse another free bank or use the study strategy guide to turn your misses into spaced review.

All free testsStudy strategy