CCDAK Practice Questions

Clients with new schema will be able to read records saved with old schema and clients with old

schema will be able to read records saved with new schema.

With this configuration, a single in-sync replica is still readable, but not writeable if the producer

using acks=all

Producers can set acks=1 to get acknowledgement from partition leader only.

each consumer can process only 50 MB/s, so we need at least 20 consumers consuming one partition

so that 50 * 20 = 1000 MB target is achieved.

Consumer offsets are stored in a Kafka topic __consumer_offsets, and the Schema Registry stored

schemas in the _schemas topic.

With SSL, messages will need to be encrypted and decrypted, by being first loaded into the JVM, so

you

lose

the

zero

copy

optimization.

See

more

information

herehttps://twitter.com/ijuma/status/1161303431501324293?s=09

Kafka Streams can only guarantee exactly once processing if you have a Kafka to Kafka topology.

retention.ms can be configured at topic level while creating topic or by altering topic. It shouldn't be

set at the broker level (log.retention.ms) as this would impact all the topics in the cluster, not just the

one we are interested in

Replicas are spread across available brokers, and each replica = one broker. RF 3 = 3 brokers

batch.size controls how many bytes of data to collect before sending messages to the Kafka broker.

Set this as high as possible, without exceeding available memory. Enabling compression can also help

make more compact batches and increase the throughput of your producer. Linger.ms will have no

effect as the batches are already full