CCDAK 試験問題を無料オンラインアクセス

(Your application consumes from a topic configured with a deserializer.
You want the application to be resilient to badly formatted records (poison pills).
You surround the poll() call with a try/catch block for RecordDeserializationException.
You need to log the bad record, skip it, and continue processing other records.
Which action should you take in the catch block?)

• A.Log the bad record and seek the consumer to the offset of the next record.
• B.Log the bad record and call consumer.skip() method.
• C.Throw a runtime exception to trigger a restart of the application.
• D.Log the bad record; no other action is needed.

Match the topic configuration setting with the reason the setting affects topic durability.
(You are given settings like unclean.leader.election.enable=false, replication.factor, min.insync.replicas=2)

正解：

Explanation:
unclean.leader.election.enable=false # Prevents data loss by only considering in-sync replicas when rebalancing.
replication.factor # Specifies how many redundant copies of partitions are distributed across brokers.
min.insync.replicas=2 # Sets the standard for the number of partition instances that must keep up with the latest committed message.
unclean.leader.election.enable=false ensures that only in-sync replicas can be elected as leaders. If disabled, an out-of-sync replica may become leader, potentially leading to data loss.
replication.factor defines how many brokers will maintain copies of each partition, directly impacting durability and availability.
min.insync.replicas determines how many replicas must acknowledge a write when acks=all is used, enforcing write durability.
Reference: Apache Kafka Topic Configuration Documentation

(You are writing to a Kafka topic with producer configuration acks=all.
The producer receives acknowledgements from the broker but still creates duplicate messages due to network timeouts and retries.
You need to ensure that duplicate messages are not created.
Which producer configuration should you set?)

• A.retries=0max.in.flight.requests.per.connection=5enable.idempotence=true
• B.retries=2147483647max.in.flight.requests.per.connection=1enable.idempotence=true
• C.retries=2147483647max.in.flight.requests.per.connection=5enable.idempotence=false
• D.enable.auto.commit=true

(You create a topic with five partitions.
What can you assume about messages read from that topic by a single consumer group?)

• A.Messages from one partition can be consumed by any of the consumers in a group for faster processing.
• B.The consumer group can only read the same number of messages from all the partitions.
• C.Messages can be consumed by a maximum of five consumers in the same consumer group.
• D.All messages will be read from exactly one broker by the consumer group.

Which tool can you use to modify the replication factor of an existing topic?

• A.kafka-reassign-topics.sh
• B.kafka-recreate-topic.sh
• C.kafka-topics.sh
• D.kafka-reassign-partitions.sh