In Avro, adding an element to an enum without a default is a __ schema evolution
Answer : A
Since Confluent 5.4.0, Avro 1.9.1 is used. Since default value was added to enum complex type , the schema resolution changed from:
(<1.9.1) if both are enums:** if the writer's symbol is not present in the reader's enum, then an error is signalled. **(>=1.9.1) if both are enums:
if the writer's symbol is not present in the reader's enum and the reader has a default value, then that value is used, otherwise an error is signalled.
Your manager would like to have topic availability over consistency. Which setting do you need to change in order to enable that?
Answer : B
unclean.leader.election.enable=true allows non ISR replicas to become leader, ensuring availability but losing consistency as data loss will occur
A topic has three replicas and you set min.insync.replicas to 2. If two out of three replicas are not available, what happens when a produce request with acks=all is sent to broker?
Answer : A
With this configuration, a single in-sync replica becomes read-only. Produce request will receive NotEnoughReplicasException.
In Avro, removing or adding a field that has a default is a __ schema evolution
Answer : A
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.
You are receiving orders from different customer in an "orders" topic with multiple partitions. Each message has the customer name as the key. There is a special customer named ABC that generates a lot of orders and you would like to reserve a partition exclusively for ABC. The rest of the message should be distributed among other partitions. How can this be achieved?
Answer : B
A Custom Partitioner allows you to easily customise how the partition number gets computed from a source message.
What is the protocol used by Kafka clients to securely connect to the Confluent REST Proxy?
Answer : C
TLS - but it is still called SSL.
You have a consumer group of 12 consumers and when a consumer gets killed by the process management system, rather abruptly, it does not trigger a graceful shutdown of your consumer. Therefore, it takes up to 10 seconds for a rebalance to happen. The business would like to have a 3 seconds rebalance time. What should you do? (select two)
Answer : B, E
session.timeout.ms must be decreased to 3 seconds to allow for a faster rebalance, and the heartbeat thread must be quicker, so we also need to decrease heartbeat.interval.ms