Bird
0
0

Which statement best explains why Kafka producer idempotency requires max.in.flight.requests.per.connection to be 5 or less?

hard📝 Conceptual Q10 of 15
Kafka - Producers
Which statement best explains why Kafka producer idempotency requires max.in.flight.requests.per.connection to be 5 or less?
ABecause higher values can cause message reordering leading to duplicates.
BBecause lower values increase throughput significantly.
CBecause it disables retries automatically.
DBecause it encrypts messages for security.
Step-by-Step Solution
Solution:

  1. Step 1: Understand max.in.flight.requests.per.connection

    This setting controls how many messages can be sent without waiting for acknowledgments.

  2. Step 2: Effect of high values on idempotency

    Higher values can cause messages to be acknowledged out of order, breaking idempotency guarantees and causing duplicates.

  3. Final Answer:

    Because higher values can cause message reordering leading to duplicates. -> Option A

  4. Quick Check:

    Max in-flight > 5 risks duplicates due to reordering [OK]
Quick Trick: Keep max.in.flight ≤ 5 to avoid duplicates from reordering [OK]
Common Mistakes:
  • Thinking lower max.in.flight increases throughput
  • Assuming it disables retries
  • Confusing with encryption settings

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kafka Quizzes
Consumer Groups - Group coordinator - Quiz 12easy Consumer Groups - Consumer group concept - Quiz 12easy Consumer Groups - Group coordinator - Quiz 4medium Consumers - Deserialization - Quiz 7medium Kafka Cluster Architecture - Broker configuration basics - Quiz 7medium Kafka Cluster Architecture - Broker nodes - Quiz 3easy Kafka Cluster Architecture - Broker configuration basics - Quiz 12easy Producers - Compression (gzip, snappy, lz4) - Quiz 10hard Producers - Producer API basics - Quiz 15hard Topics and Partitions - Topic configuration - Quiz 13medium