A consumer is configured with enable.auto.commit=false. What happens when close() is called on the consumer object?
Correct Answer:B
Calling close() on consumer immediately triggers a partition rebalance as the consumer will not be available anymore.
In the Kafka consumer metrics it is observed that fetch-rate is very high and each fetch is small. What steps will you take to increase throughput?
Correct Answer:E
This will allow consumers to wait and receive more bytes in each fetch request.
The rule "same key goes to the same partition" is true unless...
Correct Answer:C
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.
A consumer has auto.offset.reset=latest, and the topic partition currently has data for offsets going from 45 to 2311. The consumer group never committed offsets for the topic before. Where will the consumer read from?
Correct Answer:A
Latest means that data retrievals will start from where the offsets currently end
You are building a consumer application that processes events from a Kafka topic. What is the most important metric to monitor to ensure real-time processing?
Correct Answer:B
This metric shows the current lag (number of messages behind the broker)