How can you gracefully make a Kafka consumer to stop immediately polling data from Kafka and gracefully shut down a consumer application?
The kafka-console-consumer CLI, when used with the default options
To transform data from a Kafka topic to another one, I should use
Which of the following statements are true regarding the number of partitions of a topic?
You create a producer that writes messages about bank account transactions from tens of thousands of different customers into a topic.
Your consumers must process these messages with low latency and minimize consumer lag
Processing takes ~6x longer than producing
Transactions for each bank account must be processedin orderWhich strategy should you use?
Your application is consuming from a topic with one consumer group.
The number of running consumers is equal to the number of partitions.
Application logs show that some consumers are leaving the consumer group during peak time, triggering a rebalance. You also notice that your application is processing many duplicates.
You need to stop consumers from leaving the consumer group.
What should you do?
You have a topic t1 with six partitions. You use Kafka Connect to send data from topic t1 in your Kafka cluster to Amazon S3. Kafka Connect is configured for two tasks.
How many partitions will each task process?
You need to configure a sink connector to write records that fail into a dead letter queue topic. Requirements:
Topic name: DLQ-Topic
Headers containing error context must be added to the messagesWhich three configuration parameters are necessary?(Select three.)
Match the testing tool with the type of test it is typically used to perform.
Your Kafka cluster has five brokers. The topic t1 on the cluster has:
Two partitions
Replication factor = 4
min.insync.replicas = 3You need strong durability guarantees for messages written to topic t1.You configure a producer acks=all and all the replicas for t1 are in-sync.How many brokers need to acknowledge a message before it is considered committed?
