Pearson CCDAK New Attempt

BothLeaderNotAvailableExceptionandNotEnoughReplicasExceptionare subclasses of RetriableException, which representstransient issuesthat may succeed upon retry.

FromApache Kafka Java Client Documentation:

“RetriableException indicates that the request can be retried. This includes network errors and certain broker-side failures like leader not available or not enough replicas.”

RecordTooLargeException and AuthorizationException arenon-retriablebecause they represent client misconfigurations or access issues.

Using assign() givesmanual controlover partition assignment. In this mode:

B is true: The applicationchooses partitionsdirectly without involving the group coordinator.

C is true: Since no group coordination occurs,no rebalancinghappens if a consumer dies.

FromKafka Consumer API Docs:

“assign() manually assigns a list of partitions to this consumer. No coordination takes place and no rebalancing is triggered.”

A is false: subscribe() and assign() aremutually exclusive.

D is incorrect: Partitions don't need to be equal across topics.

The default maximum message size that a Kafka broker accepts is1MB (1,048,576 bytes), controlled by the config propertymessage.max.bytes.

FromKafka Broker Configuration Docs:

“The default maximum message size is 1MB. To accept larger messages, configure message.max.bytes and the producer’s max.request.size.”

Producers also have a matching limit via max.request.size, and consumers via fetch.message.max.bytes.

Kafka Connectsource connectorsuse theoffset.storage.topicconfiguration parameter to define where to storeoffsets that track the connector's positionin the source system (e.g., database, file, etc.).

FromKafka Connect Worker Configuration:

“offset.storage.topic specifies the topic in Kafka where the connector stores offsets for each source partition.”

This allows Kafka Connect toresumefrom the correct position on restart.

The other options (B–D) are not valid Kafka configs.