Multiple ChoiceIntermediate 45s
Exactly-once via idempotent producer
Which combination enables exactly-once semantics for a Kafka producer writing into Kafka?
Options
- 1enable.idempotence=true plus transactions, combined with consumer read_committed
- 2acks=0 on the producer plus consumer auto commit, which loses records whenever a rebalance occurs
- 3A single partition for the topic with acks=1 per produce, which prevents reordering but duplicates
- 4Committing the consumer offset before processing, so a crash loses data but never duplicates
Think you can answer under pressure?
Get matched and answer live questions in 3-minute 1v1 battles. Elo ranking, badge tiers and bragging rights on the line.