View Full Confluent CCDAK Exam Dumps and Practice Test Dumps

 

Question 361

Which Kafka broker setting limits the maximum size of a socket request?

1. socket.request.max.bytes
2. message.max.bytes
3. replica.fetch.max.bytes
4. fetch.max.bytes

Correct Answer: 1

Explanation:

The socket.request.max.bytes broker setting controls the maximum number of bytes in a request that the broker will accept from a network connection. It provides a boundary for individual requests reaching the broker. This setting is different from message.max.bytes, which limits the maximum record batch size stored in a topic. Similarly, fetch.max.bytes is a consumer-side setting, while replica.fetch.max.bytes applies to replica fetching. Understanding these distinctions is important when diagnosing oversized-request errors and configuring brokers for workloads containing large messages.

Question 362

Which Kafka consumer method retrieves partitions available for a topic?

1. listTopics()
2. partitionsFor()
3. metrics()
4. offsetsForTimes()

Correct Answer: 2

Explanation:

The partitionsFor() consumer method retrieves metadata describing the partitions available for a specified topic. Applications can use this information when they need partition metadata without explicitly subscribing to the topic. listTopics() retrieves broader topic metadata, while metrics() exposes client metrics. offsetsForTimes() serves a different purpose by finding offsets corresponding to supplied timestamps. Knowing the appropriate Consumer API method helps applications inspect cluster metadata efficiently and avoid using an unrelated method for partition discovery.

Question 363

What does a Kafka Streams Transformer allow an application to do?

1. Only serialize records
2. Only monitor brokers
3. Process records with context
4. Only create topics

Correct Answer: 3

Explanation:

A Kafka Streams Transformer provides a processor-level mechanism for transforming records while accessing processing context. The context can provide information such as record metadata and allow scheduling or forwarding behavior depending on the API being used. This makes the Transformer API more flexible than simple value-mapping operations. Serialization is handled through serializers and related configuration, broker monitoring uses different mechanisms, and topic creation is an administrative operation. Transformers are useful when stream processing requires more control than straightforward stateless transformations.

Question 364

Which Kafka Streams method sends records through an explicitly named topic?

1. merge()
2. branch()
3. through()
4. aggregate()

Correct Answer: 3

Explanation:

The Kafka Streams through() operation writes records to a specified Kafka topic and then reads them back into the topology. This can be useful when an application intentionally wants a topic to act as an intermediate boundary in processing. The operation therefore introduces a Kafka-backed stage between processing steps. merge() combines streams, branch() splits records according to predicates, and aggregate() creates an aggregated state representation. Understanding these topology operations helps developers select the correct mechanism for routing and persistence requirements.

Question 365

Which setting controls how long deleted log segments remain before physical removal?

1. log.segment.delete.delay.ms
2. log.retention.bytes
3. log.cleaner.delete.retention.ms
4. log.roll.ms

Correct Answer: 1

Explanation:

log.segment.delete.delay.ms controls the delay before Kafka physically deletes a log segment that has already become eligible for deletion. This delay can provide time for the filesystem to complete related operations before removal occurs. It is different from log.retention.bytes, which limits retained log size, and log.roll.ms, which influences segment rolling. log.cleaner.delete.retention.ms is associated with how long delete markers are retained for compacted logs, so it serves a different purpose.

Question 366

Which Kafka Streams component schedules punctuation during stream processing?

1. ConsumerRecord
2. Punctuator
3. Serializer
4. Partitioner

Correct Answer: 2

Explanation:

A Kafka Streams Punctuator defines logic that can be executed when scheduled punctuation occurs. Punctuation allows stream-processing applications to perform periodic actions based on stream time or wall-clock time, depending on how the processor schedules it. This capability is useful for tasks such as emitting periodic results or performing time-based processing. A ConsumerRecord represents consumed data, a Serializer converts objects to bytes, and a Partitioner determines record partitioning. Punctuators therefore belong specifically to timed processing behavior.

Question 367

Which consumer method moves the position to the first offset of assigned partitions?

1. seekToBeginning()
2. seekToEnd()
3. position()
4. committed()

Correct Answer: 1

Explanation:

The Kafka Consumer API method seekToBeginning() moves the consumer’s position to the earliest available offset for specified assigned partitions. This is useful when an application needs to replay retained records from the beginning rather than continuing from its current position. seekToEnd() moves the position toward the latest offset, while position() reports the current position. committed() retrieves the committed offset associated with a consumer group. These methods provide precise control over where consumption resumes within assigned partitions.

Question 368

Which Kafka Connect setting specifies the replication factor for dead-letter topics?

1. errors.tolerance
2. errors.deadletterqueue.topic.replication.factor
3. errors.log.enable
4. tasks.max

Correct Answer: 2

Explanation:

The errors.deadletterqueue.topic.replication.factor setting determines the replication factor used when Kafka Connect creates a dead-letter queue topic. A suitable replication factor can improve the durability of records routed to the error topic. errors.tolerance determines whether processing continues after errors, while errors.log.enable controls error logging. tasks.max controls the maximum number of connector tasks and is unrelated to dead-letter topic replication. Proper configuration of error handling helps prevent failed records from becoming difficult to investigate or recover.

Question 369

Which Kafka broker setting limits the number of simultaneous connections from one IP address?

1. max.connections.per.ip.overrides
2. connections.max.idle.ms
3. max.connections
4. max.connections.per.ip

Correct Answer: 4

Explanation:

The max.connections.per.ip broker setting limits the number of simultaneous connections permitted from each IP address. This can help control connection concentration from individual clients or network sources. It differs from max.connections, which provides a broader broker-level connection limit. connections.max.idle.ms controls how long idle connections may remain open. The per-IP setting is particularly relevant when many clients originate from the same address, such as applications behind a shared network gateway or load-balancing infrastructure.

Question 370

Which Kafka consumer method moves consumption to the latest available offset?

1. seekToEnd()
2. seekToBeginning()
3. position()
4. committed()

Correct Answer: 1

Explanation:

The seekToEnd() method moves the consumer position to the end offset of specified assigned partitions. Applications can use it when they want to skip currently retained historical records and begin consuming newly arriving records. This operation applies to the consumer’s current position and requires the partitions to be assigned. seekToBeginning() performs the opposite movement toward the earliest available offsets. position() reports a position, while committed() retrieves a previously committed group offset rather than changing the current consumer position.

Question 371

What does Kafka Streams Materialized primarily control?

1. Broker authentication
2. Consumer assignment
3. State-store materialization
4. Topic deletion

Correct Answer: 3

Explanation:

The Kafka Streams Materialized class provides configuration for materializing state stores and, when appropriate, their underlying serialization details and store naming. Materialized state can make processed results available for interactive access and can support stateful stream-processing operations. Broker authentication is handled through security configuration, consumer assignment is managed through consumer-group mechanisms, and topic deletion is an administrative operation. Using Materialized gives developers explicit control over how stateful results are represented and persisted within a Kafka Streams topology.

Question 372

Which Schema Registry value identifies a specific registered schema independently of its version?

1. Subject name
2. Schema ID
3. Schema version
4. Compatibility level

Correct Answer: 3

Explanation:

A schema version identifies the revision of a schema under a particular subject in Schema Registry. A subject can therefore have multiple versions as schemas evolve. A schema ID is a separate identifier associated with a registered schema and is not simply the same concept as a subject-relative version number. The subject identifies the logical namespace where schemas are registered, while compatibility level defines allowed evolution behavior. Distinguishing schema IDs from versions is important when troubleshooting serialization metadata and schema-evolution workflows.

Question 373

Which Kafka security setting defines mechanisms available for SASL authentication?

1. sasl.enabled.mechanisms
2. sasl.jaas.config
3. security.protocol
4. ssl.keystore.location

Correct Answer: 1

Explanation:

The sasl.enabled.mechanisms setting specifies the SASL mechanisms enabled for authentication. SASL provides an authentication framework, and different mechanisms can support different credential-handling approaches. sasl.jaas.config supplies JAAS-related authentication configuration, while security.protocol determines the overall security protocol used by the client. ssl.keystore.location belongs to TLS certificate and key configuration. Separating mechanism selection from credential configuration helps administrators build secure Kafka client and broker configurations without confusing authentication with transport encryption.

Question 374

Which ksqlDB command displays the functions available to users?

1. SHOW STREAMS
2. SHOW TABLES
3. SHOW QUERIES
4. SHOW FUNCTIONS

Correct Answer: 4

Explanation:

The SHOW FUNCTIONS statement in ksqlDB displays functions available in the environment. This can help users discover built-in functions and registered user-defined functions when constructing SQL expressions. SHOW STREAMS lists streams, SHOW TABLES lists tables, and SHOW QUERIES provides information about queries. Function discovery is especially useful when developing ksqlDB statements because it allows users to verify what reusable processing functionality is available before writing or modifying a query.

Question 375

Which Kafka broker setting controls the maximum lifetime of a reauthentication interval?

1. connections.max.idle.ms
2. connections.max.reauth.ms
3. socket.request.max.bytes
4. queued.max.requests

Correct Answer: 2

Explanation:

connections.max.reauth.ms controls the maximum time allowed between reauthentication events for supported Kafka security configurations. Reauthentication can require clients to authenticate again on an established connection instead of maintaining authentication indefinitely. This setting is distinct from connections.max.idle.ms, which controls idle connection lifetime. socket.request.max.bytes limits request size, while queued.max.requests relates to queued network requests. Understanding these settings helps administrators distinguish connection lifecycle controls from request-size and network-processing limits.

Question 376

Which Kafka Streams operation repartitions records using their current keys?

1. filter()
2. repartition()
3. peek()
4. suppress()

Correct Answer: 2

Explanation:

The Kafka Streams repartition() operation creates a repartitioning stage so records can be redistributed according to their current keys. Repartitioning is important when subsequent processing requires records with the same key to be colocated in the same partition. This can be particularly relevant before key-based aggregation or joins. filter() removes records that do not satisfy a predicate, peek() provides observation without changing records, and suppress() controls result emission. Repartitioning therefore addresses data distribution rather than filtering or output suppression.

Question 377

Which Kafka consumer method returns metadata for all topics visible to the client?

1. listTopics()
2. partitionsFor()
3. metrics()
4. position()

Correct Answer: 1

Explanation:

The listTopics() Consumer API method retrieves metadata describing topics visible to the client. It can be used when an application needs information about available topics and their partitions. partitionsFor() is narrower because it retrieves partition metadata for a specified topic. metrics() exposes client metrics, while position() reports the consumer’s current offset position for an assigned partition. Selecting the correct metadata method helps applications avoid unnecessary operations and makes consumer-side administrative or discovery logic clearer.

Question 378

Which Schema Registry concept identifies a schema revision within one subject?

1. Schema ID
2. Compatibility mode
3. Schema version
4. Subject name

Correct Answer: 3

Explanation:

A schema version identifies a particular revision registered under a Schema Registry subject. As a subject evolves, multiple schema versions can exist, allowing applications and administrators to track changes over time. The subject identifies the logical grouping, while the schema ID is a separate identifier associated with registered schemas. Compatibility mode defines which changes are permitted between versions. Understanding these distinctions is important when examining schema history, debugging serialization failures, or determining which revision is associated with a particular subject.

Question 379

Which Kafka Streams operation writes records to an intermediate Kafka topic before continuing?

1. filter()
2. mapValues()
3. through()
4. branch()

Correct Answer: 3

Explanation:

The Kafka Streams through() operation writes records to a specified Kafka topic and then consumes them again as part of the topology. This creates an explicit Kafka-backed boundary between processing stages. Such a boundary can be useful when records need to be persisted or redistributed before subsequent processing. filter() selects records, mapValues() changes values while retaining keys, and branch() divides a stream based on predicates. Therefore, through() is specifically associated with routing records through an intermediate Kafka topic.

Question 380

Which Kafka Streams API class groups records by a selected key and prepares them for aggregation?

1. Joined
2. Produced
3. Grouped
4. Consumed

Correct Answer: 3

Explanation:

The Kafka Streams Grouped class provides grouping configuration for records, including the key and value serdes used during grouped operations. It is commonly used after selecting or transforming a key when preparing a stream for aggregation or reduction. Joined configures stream or table join behavior, Produced configures output records, and Consumed configures source-topic consumption. Proper grouping configuration ensures records are organized according to the intended key before stateful operations such as aggregation are performed.