The Best Practice Test Preparation for the CCDAK Certification Exam [Q102-Q120]

Share

The Best Practice Test Preparation for the CCDAK Certification Exam

CCDAK Exam Dumps, Practice Test Questions BUNDLE PACK


Achieving the CCDAK Certification is a valuable credential for developers who work with Apache Kafka. Confluent Certified Developer for Apache Kafka Certification Examination certification demonstrates a high level of proficiency in working with Kafka and can help developers advance their careers and open up new job opportunities. Additionally, the certification is recognized by industry leaders and demonstrates a commitment to professional development and staying up-to-date with the latest trends and technologies in the field.

 

NEW QUESTION # 102
Which configuration determines how many bytes of data are collected before sending messages to the Kafka broker?

  • A. buffer.memory
  • B. send.buffer.bytes
  • C. batch.size
  • D. max.block.size

Answer: C

Explanation:
Thebatch.sizeconfig sets themaximum number of bytes to batch per partitionbefore sending. This allows Kafka producers toamortize I/Oand improve throughput.
FromKafka Producer Configuration Docs:
"batch.size is the maximum amount of data per partition the producer will batch before sending."
* buffer.memory sets total memory for the producer, not per-batch.
* send.buffer.bytes is aTCP socket buffer, not a Kafka config.
* max.block.ms controls blocking time, not size.
Reference:Kafka Producer Configs > batch.size


NEW QUESTION # 103
You are using JDBC source connector to copy data from 3 tables to three Kafka topics. There is one connector created with max.tasks equal to 2 deployed on a cluster of 3 workers. How many tasks are launched?

  • A. 0
  • B. 1
  • C. 2
  • D. 3

Answer: A

Explanation:
here, we have three tables, but the max.tasks is 2, so that's the maximum number of tasks that will be created


NEW QUESTION # 104
What's is true about Kafka brokers and clients from version 0.10.2 onwards?

  • A. Clients and brokers must have the exact same version to be able to communicate
  • B. A newer client can't talk to a newer broker, but an older client can talk to a newer broker
  • C. A newer client can talk to a newer broker, and an older client can talk to a newer broker
  • D. A newer client can talk to a newer broker, but an older client cannot talk to a newer broker

Answer: C

Explanation:
Kafka's new bidirectional client compatibility introduced in 0.10.2 allows this. Read more herehttps://www.confluent.io/blog/upgrading-apache-kafka-clients-just-got-easier/


NEW QUESTION # 105
A Zookeeper ensemble contains 5 servers. What is the maximum number of servers that can go missing and the ensemble still run?

  • A. 0
  • B. 1
  • C. 2
  • D. 3

Answer: A

Explanation:
majority consists of 3 zk nodes for 5 nodes zk cluster, so 2 can fail


NEW QUESTION # 106
There are two consumers C1 and C2 belonging to the same group G subscribed to topics T1 and T2. Each of the topics has 3 partitions. How will the partitions be assigned to consumers with Partition Assigner being Round Robin Assigner?

  • A. C1 will be assigned partitions 0 and 1 from T1 and T2, C2 will be assigned partition 2 from T1 and T2.
  • B. All consumers will read from all partitions
  • C. C1 will be assigned partitions 0 and 2 from T1 and partition 1 from T2. C2 will have partition 1 from T1 and partitions 0 and 2 from T2.
  • D. Two consumers cannot read from two topics at the same time

Answer: C

Explanation:
The correct option is the only one where the two consumers share an equal number of partitions amongst the two topics of three partitions. An interesting article to read ishttps://medium.com/@anyili0928/what-i-have-learned-from-kafka-partition-assignment-strategy-799fdf15d3ab


NEW QUESTION # 107
In Kafka, what are Topics split into?

  • A. Partitions
  • B. Sub Topics
  • C. Consumers
  • D. Chunks

Answer: A


NEW QUESTION # 108
A consumer is configured with enable.auto.commit=false. What happens when close() is called on the consumer object?

  • A. A rebalance in the consumer group will happen immediately
  • B. The uncommitted offsets are committed
  • C. The group coordinator will discover that the consumer stopped sending heartbeats. It will cause rebalance after session.timeout.ms

Answer: A

Explanation:
Calling close() on consumer immediately triggers a partition rebalance as the consumer will not be available anymore.


NEW QUESTION # 109
You are sending messages to a Kafka cluster in JSON format and want to add more information related to each message:
* Format of the message payload
* Message creation time
* A globally unique identifier that allows the message to be traced through the systemWhere should this additional information be set?

  • A. Broker
  • B. Key
  • C. Value
  • D. Header

Answer: D

Explanation:
Kafkamessage headersare the right place to includemetadatasuch as:
* Payload format (e.g., schema version)
* Timestamps (custom)
* Trace or correlation IDs
FromKafka Producer API Docs:
"Headers are a map of key-value pairs that can be used to include metadata alongside the message, without modifying the message body."
* Keys determine partitioning and ordering
* Values are the message payload
* Brokers do not store arbitrary metadata fields
Reference:Kafka ProducerRecord API > Headers


NEW QUESTION # 110
A consumer application needs to use an "at most once" delivery semantic.
What is the best consumer configuration lo avoid duplicate messages being read?

  • A. auto.offset.reset=earliest and enable auto commit=true
  • B. auto.offset.reset=eariiest and enable.auto.commit=false
  • C. auto.offset.reset-latest and enable auto commit-false
  • D. auto.offset.reset=latest and enable.auto.commit=true

Answer: D


NEW QUESTION # 111
Which actions will trigger partition rebalance for a consumer group? (select three)

  • A. A consumer in a consumer group shuts down
  • B. Increase partitions of a topic
  • C. Add a new consumer to consumer group
  • D. Remove a broker from the cluster

Answer: A,B,C

Explanation:
Add a broker to the cluster
Explanation:
Rebalance occurs when a new consumer is added, removed or consumer dies or paritions increased.


NEW QUESTION # 112
A bank uses a Kafka cluster for credit card payments. What should be the value of the property unclean.leader.election.enable?

  • A. FALSE
  • B. TRUE

Answer: A

Explanation:
Setting unclean.leader.election.enable to true means we allow out-of-sync replicas to become leaders, we will lose messages when this occurs, effectively losing credit card payments and making our customers very angry.


NEW QUESTION # 113
What's is true about Kafka brokers and clients from version 0.10.2 onwards?

  • A. Clients and brokers must have the exact same version to be able to communicate
  • B. A newer client can't talk to a newer broker, but an older client can talk to a newer broker
  • C. A newer client can talk to a newer broker, and an older client can talk to a newer broker
  • D. A newer client can talk to a newer broker, but an older client cannot talk to a newer broker

Answer: C

Explanation:
Kafka's new bidirectional client compatibility introduced in 0.10.2 allows this. Read more herehttps://www.
confluent.io/blog/upgrading-apache-kafka-clients-just-got-easier/


NEW QUESTION # 114
You are sending messages with keys to a topic. To increase throughput, you decide to increase the number of partitions of the topic. Select all that apply.

  • A. Old records will stay in their partitions
  • B. New records may get written to a different partition
  • C. All the existing records will get rebalanced among the partitions to balance load
  • D. New records with the same key will get written to the partition where old records with that key were written

Answer: A,B

Explanation:
Increasing the number of partition causes new messages keys to get hashed differently, and breaks the guarantee "same keys goes to the same partition". Kafka logs are immutable and the previous messages are not re-shuffled


NEW QUESTION # 115
is KSQL ANSI SQL compliant?

  • A. Yes
  • B. No

Answer: B

Explanation:
KSQL is not ANSI SQL compliant, for now there are no defined standards on streaming SQL languages


NEW QUESTION # 116
Refer to the producer code below. It features a 'Callback' class with a method called 'onCompletion()'.
In the 'on Completion*.)' method, what does the 'metadata.offset()' value represent?

producer.send(record, new MyCallback(record));

  • A. The id of the partition that the message was committed to
  • B. The number of bytes that overflowed beyond a producer batch of messages
  • C. Its position in the producer's batch of messages
  • D. The sequential id of the message is committed into a partition

Answer: D


NEW QUESTION # 117
Kafka is configured with following parameters - log.retention.hours = 168 log.retention.minutes = 168 log.
retention.ms = 168 How long will the messages be retained for?

  • A. Broker will not start due to bad configuration
  • B. 168 ms
  • C. 168 hours
  • D. 168 minutes

Answer: B

Explanation:
If more than one similar config is specified, the smaller unit size will take precedence.


NEW QUESTION # 118
Your topic is log compacted and you are sending a message with the key K and value null. What will happen?

  • A. The broker will delete all messages with the key K upon cleanup
  • B. The producer will throw a Runtime exception
  • C. The message will get ignored by the Kafka broker
  • D. The broker will delete the message with the key K and null value only upon cleanup

Answer: A

Explanation:
Sending a message with the null value is called a tombstone in Kafka and will ensure the log compacted topic does not contain any messages with the key K upon compaction


NEW QUESTION # 119
Your Kafka cluster has five brokers. The topic t1 on the cluster has:
* Two partitions
* Replication factor = 4
* min.insync.replicas = 3You need strong durability guarantees for messages written to topic t1.You configure a producer acks=all and all the replicas for t1 are in-sync.How many brokers need to acknowledge a message before it is considered committed?

  • A. 0
  • B. 1
  • C. 2
  • D. 3

Answer: C

Explanation:
With acks=all, the leader waits formin.insync.replicasto acknowledge the message. Since min.insync.
replicas=3, Kafka will only commit the messageonce 3 brokers (leader + 2 followers)confirm they have the message.
FromKafka Documentation > Acks and Durability:
"If acks=all is specified, the producer will wait until the full set of in-sync replicas has acknowledged the record. The minimum number of in-sync replicas is controlled by min.insync.replicas." Even though the replication factor is 4, only3 acknowledgments are needed, as defined by min.insync.
replicas.
Reference:Apache Kafka Producer Configs > acks, min.insync.replicas


NEW QUESTION # 120
......

Prepare for the Actual Confluent Certified Developer CCDAK Exam Practice Materials Collection: https://www.examboosts.com/Confluent/CCDAK-practice-exam-dumps.html

Confluent Certified Developer Certification CCDAK Sample Questions Reliable: https://drive.google.com/open?id=1eN-RNUaQx6gPTyTW8jmeKdTtPXf2ZRdp