Confluent Certified Administrator for Apache Kafka Free Practice Questions
This deck synthesizes 15 practice questions covering core Kafka administration topics: broker roles, cluster metadata management, log cleanup policies, upgrade safety, consumer groups, replication health, security, and troubleshooting. It focuses on understanding why each answer is correct based on underlying concepts, not rote memorization. Use these flashcards to reinforce the decision-making process for common administrative tasks such as configuring durability, monitoring under-replicated partitions, and applying dynamic broker settings. Mastery of this content will help you reason through similar scenarios on the certification exam.
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.
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.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 15-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
What is the primary purpose of a Kafka broker in a distributed streaming platform?
Show hint
Understand core broker responsibilities
Study workflow
Turn one Confluent Certified Administrator for Apache Kafka attempt into a study plan
- 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
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
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
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
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.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.