Producer Acknowledgements (acks) — Concept Check
Questions on Producer Acknowledgements (acks). acks=0 (fire-and-forget), acks=1 (leader ack), acks=all (all ISR ack) — higher acks improve durability at the cost of latency; combine with min.insync.replicas for safety.
Questions in this quiz
7 questions on Producer Acknowledgements (acks) — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A Kafka producer is configured with acks=0. What is the primary trade-off of using this setting?
- AMaximum throughput with zero durability guarantee
- BModerate durability with leader-only acknowledgement
- CHigh durability with increased latency
- DHigh latency with all ISR acknowledgement
2.A service using Kafka with acks=1 experiences data loss after a leader failure. Why did this happen?
- AThe producer was configured with min.insync.replicas=2
- BThe producer used acks=all with retries disabled
- CAll ISR members acknowledged the write
- DThe leader failed before followers replicated the data
3.In a Kafka setup with acks=all and min.insync.replicas=2, what happens if the ISR shrinks to 1?
- AThe leader continues to acknowledge writes
- BThe producer switches to acks=1 automatically
- CWrites are blocked until another replica rejoins the ISR
- DData is silently lost without any error
4.A Kafka producer is set with acks=all. What is the primary benefit of this configuration?
- AGuarantees data loss prevention with acks=0
- BEnsures all ISR members have persisted the record
- CProvides maximum throughput with zero durability
- DAllows leader-only acknowledgement for moderate durability
5.A developer believes acks=all guarantees data safety even if ISR shrinks to 1. Why is this incorrect?
- AISR size does not affect data safety with acks=all
- Backs=all requires min.insync.replicas to ensure safety
- Cacks=all automatically switches to acks=1 in this case
- DThe producer will continue writing without any checks
6.If a Kafka broker is configured with min.insync.replicas=2 and acks=all, what happens during a broker failure?
- AData is lost without any notification
- BThe producer automatically switches to acks=1
- CWrites are blocked until the ISR is restored
- DThe leader acknowledges writes without waiting
7.What does the acks=1 setting imply for a Kafka producer?
- AThe producer retries indefinitely until all replicas acknowledge
- BAll ISR members must acknowledge the write
- CNo acknowledgement is required, maximizing throughput
- DThe leader acknowledges writes, but data can be lost if the leader fails