[2026年01月18日]Confluent CCAAKリアル試験問題と解答を無料で提供いたします [Q26-Q44]

Share

[2026年01月18日]Confluent CCAAKリアル試験問題と解答を無料で提供いたします

合格できるConfluent CCAAK試験情報と無料練習テスト問題


Confluent CCAAK 認定試験の出題範囲:

トピック出題範囲
トピック 1
  • Apache Kafka® Fundamentals: This section of the exam measures skills of a Kafka Administrator and covers core concepts such as Kafka architecture, components, and data flow. It assesses the candidate’s understanding of topics like topics and partitions, brokers, producers, consumers, and message retention.
トピック 2
  • Apache Kafka® Cluster Configuration: This section of the exam measures skills of a Kafka Administrator and includes configuring broker properties, tuning for performance, managing topic-level settings, and applying best practices for production-grade environments.
トピック 3
  • Kafka Connect: This section of the exam measures skills of a Site Reliability Engineer and addresses the use and management of Kafka Connect for data integration. It includes setting up connectors, managing configurations, and ensuring efficient movement of data between Kafka and external systems.
トピック 4
  • Troubleshooting: This section of the exam measures skills of a Kafka Administrator and includes diagnosing common issues in Kafka clusters. It covers problem areas such as performance bottlenecks, message delivery failures, replication issues, and consumer lag, along with techniques to resolve them effectively.

 

質問 # 26
You have a Kafka cluster with topics t1 and t2. In the output below, topic t2 shows Partition 1 with a leader "-1".
What is the most likely reason for this?
...
$ kafka-topics --zookeeper localhost:2181 --describe --topic t1
Topic:t1 PartitionCount 1 ReplicationFactor 1 Configs:
Topic: t1 Partition: 0 Leader: 0 Replicas: 0 Isr: 0
$ kafka-topics --zookeeper localhost:2181 --describe --topic t2
Topic:t2 PartitionCount 2 ReplicationFactor 1 Configs:
Topic: t2 Partition: 0 Leader: 0 Replicas: 0 Isr: 0
Topic: t2 Partition: 1 Leader: -1 Replicas: 1 Isr:

  • A. Compression has been enabled on Broker 1.
  • B. Leader shows "-1" while the log cleaner thread runs on Broker 1.
  • C. Broker 1 failed.
  • D. Broker 1 has another partition clashing with the same name.

正解:C

解説:
A Leader of -1 indicates that no broker is currently the leader for that partition. This usually happens when the only replica for that partition is unavailable, often due to the associated broker (in this case, Broker 1) failing or being offline. Kafka cannot elect a leader if no replica is in the in-sync replica (ISR) list, which leads to leader = -1.


質問 # 27
You have an existing topic t1 that you want to delete because there are no more producers writing to it or consumers reading from it.
What is the recommended way to delete the topic?

  • A. Delete the offsets for that topic from the consumer offsets topic.
  • B. Delete the log files and their corresponding index files from the leader broker.
  • C. The consumer should send a message with a 'null' key.
  • D. If topic deletion is enabled on the brokers, delete the topic using Kafka command line tools.

正解:D

解説:
The recommended and safe method to delete a topic is to use the Kafka CLI tool kafka-topics.sh --delete command, provided that delete.topic.enable=true is set on the brokers.


質問 # 28
What is the relationship between topics and partitions? (Choose two.)

  • A. Atopic may have more than one partition.
  • B. A partition may have more than one topic.
  • C. Atopic always has one partition.
  • D. There is no relationship between topics and partitions.
  • E. A partition is always linked to a single topic.

正解:A、E

解説:
Kafka topics are split into one or more partitions to enable parallelism and scalability.
Each partition belongs to exactly one topic; it cannot span multiple topics.


質問 # 29
What does Kafka replication factor provide? (Choose two.)

  • A. Security
  • B. Durability
  • C. Availability
  • D. Performance

正解:B、C

解説:
Replication ensures that multiple copies of data exist across different brokers, so data is not lost if one broker fails.
With multiple replicas, Kafka can continue to serve data even if the leader or one replica fails, maintaining service availability.


質問 # 30
How can authentication for both internal component traffic and external client traffic be accomplished?

  • A. Configure multiple listeners on the broker.
  • B. Configure LoadBalancer.
  • C. Configure multiple brokers.
  • D. Configure multiple security protocols on the same listener.

正解:A

解説:
Kafka supports multiple listeners, each with its own port, hostname, and security protocol. This allows you to:
* Use one listener for internal communication (e.g., brokers, ZooKeeper, Connect, etc.) with one type of authentication (e.g., PLAINTEXT or SASL).
* Use a separate listener for external clients (e.g., producers and consumers) with a different protocol (e.g., SSL or SASL_SSL).


質問 # 31
If the Controller detects the failure of a broker that was the leader for some partitions, which actions will be taken? (Choose two.)

  • A. The Controller sends the new leader and ISR list changes to all producers and consumers.
  • B. The Controller sends the new leader and ISR list changes to all brokers.
  • C. The Controller persists the new leader and ISR list to ZooKeeper.
  • D. The Controller waits for a new leader to be nominated by ZooKeeper.

正解:B、C

解説:
The Controller updates ZooKeeper with the new leader and in-sync replica (ISR) information to maintain metadata consistency.
Brokers need this information to correctly route client requests and continue replication.


質問 # 32
Which option is a valid Kafka Topic cleanup policy? (Choose two.)

  • A. delete
  • B. cleanup
  • C. compact
  • D. default

正解:A、C

解説:
The delete policy deletes old log segments when they exceed the retention period or size.
The compact policy retains only the latest record for each key, enabling efficient key-based storage.


質問 # 33
Which property in broker configuration specifies that a broker belongs to a particular rack?
Which property in broker configuration specifies that a broker belongs to a particular rack?

  • A. broker.rack
  • B. kafka.rack
  • C. client.rack
  • D. zookeeper.rack

正解:A

解説:
The broker.rack property is used in a Kafka broker's configuration to specify the rack or availability zone the broker belongs to. This is important for rack-aware replica placement, allowing Kafka to distribute replicas across different racks for fault tolerance.


質問 # 34
Which connector type takes data from a topic and sends it to an external data system?

  • A. SvsIog Connector
  • B. Streams Connector
  • C. Sink Connector
  • D. Source Connector

正解:C

解説:
A Sink Connector reads data from a Kafka topic and writes it to an external data system, such as a database, file system, or cloud service.


質問 # 35
An employee in the reporting department needs assistance because their data feed is slowing down. You start by quickly checking the consumer lag for the clients on the data stream.
Which command will allow you to quickly check for lag on the consumers?

  • A. bin/kafka-consumer-group-throughput.sh
  • B. bin/kafka-consumer-lag.sh
  • C. bin/kafka-reassign-partitions.sh
  • D. bin/kafka-consumer-groups.sh

正解:D

解説:
The kafka-consumer-groups.sh script is used to inspect consumer group details, including consumer lag, which indicates how far behind a consumer is from the latest data in the partition.
The typical usage is bin/kafka-consumer-groups.sh --bootstrap-server <broker> --describe --group <group_id>


質問 # 36
What are benefits to gracefully shutting down brokers? (Choose two.)

  • A. It will balance the partitions across brokers before restarting.
  • B. It will sync all its logs to disk to avoid needing to do any log recovery when it restarts.
  • C. It will migrate any partitions the server is the leader for to other replicas prior to shutting down.
  • D. It will automatically re-elect leaders on restart.

正解:B、C

解説:
A graceful shutdown ensures that logs are flushed to disk, minimizing recovery time during restart.
Kafka performs controlled leader migration during a graceful shutdown to avoid disruption and ensure availability.


質問 # 37
A company is setting up a log ingestion use case where they will consume logs from numerous systems. The company wants to tune Kafka for the utmost throughput.
In this scenario, what acknowledgment setting makes the most sense?

  • A. acks=undefined
  • B. acks=1
  • C. acks=all
  • D. acks=0

正解:D

解説:
acks=0 provides the highest throughput because the producer does not wait for any acknowledgment from the broker. This minimizes latency and maximizes performance.
However, it comes at the cost of no durability guarantees - messages may be lost if the broker fails before writing them. This setting is suitable when throughput is critical and occasional data loss is acceptable, such as in some log ingestion use cases where logs are also stored elsewhere.


質問 # 38
You are managing a Kafka cluster with five brokers (broker id '0', '1','2','3','4') and three ZooKeepers. There are 100 topics, five partitions for each topic, and replication factor three on the cluster. Broker id '0' is currently the Controller, and this broker suddenly fails.
Which statements are correct? (Choose three.)

  • A. The Controller uses the epoch number to prevent a split brain scenario.
  • B. The broker id is used as the epoch number to prevent a split brain scenario.
  • C. The Controller is responsible for reassigning partitions to the consumers in a Consumer Group.
  • D. Kafka uses ZooKeeper's ephemeral node feature to elect a controller.
  • E. The number of Controllers should always be equal to the number of brokers alive in the cluster.
  • F. The Controller is responsible for electing Leaders among the partitions and replicas.

正解:A、D、F

解説:
Kafka relies on ZooKeeper's ephemeral nodes to detect if a broker (controller) goes down and to elect a new controller.
The controller manages partition leadership assignments and handles leader election when a broker fails.
The epoch number ensures coordination and avoids outdated controllers acting on stale data.


質問 # 39
A Kafka cluster with three brokers has a topic with 10 partitions and a replication factor set to three. Each partition stores 25 GB data per day and data retention is set to 24 hours.
How much storage will be consumed by the topic on each broker?

  • A. 300 GB
  • B. 250 GB
  • C. 750 GB
  • D. 75 GB

正解:A

解説:
10 partitions × 25 GB/day = 250 GB total per day for the topic (primary data).
With a replication factor of 3, there are 3 full copies of the data: 250 GB × 3 = 750 GB total across the entire cluster.
The cluster has 3 brokers, and Kafka tries to distribute replicas evenly among them: 750 GB ÷ 3 brokers = 250 GB per broker on average.
However, due to replication, some partitions have leaders and followers, so there's some overlap and not-perfect distribution. Each broker stores approximately 2/3 of the total topic data (since each broker holds replicas for around 2/3 of the partitions).
2/3 × 750 GB = 500 GB, but this is shared, so each broker ends up storing ~300 GB of replicated data, including its share of leaders and followers.


質問 # 40
When a broker goes down, what will the Controller do?

  • A. Automatically elect the least loaded broker to become the leader for every orphan's partitions.
  • B. Become the leader for the topic/partition that needs a leader, pending the broker return in the cluster.
  • C. Wait for a follower to take the lead.
  • D. Trigger a leader election among the remaining followers to distribute leadership.

正解:D

解説:
When a broker goes down, the Controller detects the failure and triggers a leader election for all partitions that had their leader on the failed broker. The leader is chosen from the in-sync replicas (ISRs) of each partition.


質問 # 41
Multiple clients are sharing a Kafka cluster.
As an administrator, how would you ensure that Kafka resources are distributed fairly to all clients?

  • A. Rebalancing
  • B. Consumer Groups
  • C. ACLs
  • D. Quotas

正解:D

解説:
Kafka quotas allow administrators to control and limit the rate of data production and consumption per client (producer/consumer), ensuring fair use of broker resources among multiple clients.


質問 # 42
The Consumer property 'auto offset reset' determines what to do if there is no valid offset for a Consumer Group.
Which scenario is an example of a valid offset and therefore the 'auto.offset.reset' does NOT apply?

  • A. The Consumer Group started for the first time.
  • B. The Consumer offset is greater than the last offset in the partition (log end offset).
  • C. The Consumer offset is less than the smallest offset in the partition (log start offset).
  • D. When an offset points to a message that has been removed by compaction but is still within the current partition.offset range.

正解:D

解説:
In this scenario, the offset itself is still valid, even though the record at that offset was compacted away. The consumer can continue consuming from the next available record. Therefore, auto.offset.reset does NOT apply, because there is a valid offset present.


質問 # 43
In certain scenarios, it is necessary to weigh the trade-off between latency and throughput. One method to increase throughput is to configure batching of messages.
In addition to batch.size, what other producer property can be used to accomplish this?

  • A. delivery.timeout.ms
  • B. compression
  • C. sendbufferbytes
  • D. linger.ms

正解:D

解説:
The linger.ms property sets the maximum time the producer will wait before sending a batch, even if the batch isn't full. By increasing linger.ms, you allow more records to accumulate in the batch.


質問 # 44
......

最新のCCAAK試験問題集でConfluent試験が合格できます:https://www.jpntest.com/shiken/CCAAK-mondaishu

最強の2026年最新の問題CCAAK問題集を試そう!更新されたConfluent試験が合格できます:https://drive.google.com/open?id=1ikmvy0EeHuS9HIjM8hzrkfzEiH8tpfXf

弊社を連絡する

我々は12時間以内ですべてのお問い合わせを答えます。

オンラインサポート時間:( UTC+9 ) 9:00-24:00
月曜日から土曜日まで

サポート:現在連絡