Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Confluent CCDAK Exam - Topic 4 Question 84 Discussion

Posted by Ronald on Nov 23, 2025 at 09:11 PM

To prevent network-induced duplicates when producing to Kafka, I should use

Suggested Answer: B

Producer idempotence helps prevent the network introduced duplicates. More details herehttps://cwiki.apache.org/confluence/display/KAFKA/Idempotent+Producer


Get Premium CCDAK Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
30 comments · newest first
MA
Matthew 6 months ago
Overall, B is the safest option for preventing duplicates.
LY
Lyda 6 months ago
D seems too limiting. Batch size of 1 isn't efficient.
OM
Omega 6 months ago
I feel like C is overkill. 200,000 retries?
DE
Detra 6 months ago
A could work too, but it might slow things down.
SH
Shantay 7 months ago
I agree, B makes sense. Idempotence is key.
BE
Bettyann 7 months ago
I’m not sure about D, batch.size=1 feels limiting.
WE
Wendell 7 months ago
Totally agree with B, it’s essential for avoiding duplicates.
TE
Terina 8 months ago
Wait, retries=200000? That seems excessive!
LE
Leota 8 months ago
A) max.in.flight.requests.per.connection=1 is also a good choice.
KR
Krissy 8 months ago
B) enable.idempotence=true, because who wants to deal with network-induced duplicates? Not this guy!
GO
Goldie 8 months ago
I'd go with B as well. Retries and batch size won't help with duplicate prevention.
JO
Jose 8 months ago
Definitely B. Enabling idempotence is the way to go to prevent those pesky network-induced duplicates.
MA
Malissa 8 months ago
Batch size seems more about performance than duplicates, so I doubt D is correct. I’m really torn between A and B!
DA
Dalene 9 months ago
I feel like retries could help, but I don't think it's the right answer for preventing duplicates. So, I would lean towards B as well.
TA
Tammara 9 months ago
I'm not entirely sure, but I remember something about max in-flight requests affecting duplicates. Maybe A is relevant?
CO
Corazon 9 months ago
I think enabling idempotence is the key here, so I would go with B. It sounds familiar from our practice sessions.
FR
Franchesca 9 months ago
B seems like the most straightforward solution. Enabling idempotence should do the trick.
JA
Jamie 9 months ago
I'm a bit confused on the difference between these options. I'll need to review the docs again.
HO
Hobert 9 months ago
I'm pretty sure the answer is B. Enabling idempotence is the way to go here.
FE
Felix 10 months ago
I think B is the best choice. It ensures no duplicates.
CA
Carmela 10 months ago
B) enable.idempotence=true is the way to go!
HI
Hildegarde 10 months ago
B) enable.idempotence=true is the correct answer.
DA
Daron 10 months ago
Option B is the way to go. Enabling idempotence is the key to avoiding those annoying duplicates.
RE
Reuben 11 months ago
Okay, let's see. Preventing duplicates is key, so I'm leaning towards B or D.
TA
Tamar 11 months ago
Hmm, this one's tricky. I'll need to think through the Kafka producer configs carefully.
AU
Audry 5 months ago
↳ replying to Tamar
I agree, let's go with option B!
MI
Milly 5 months ago
↳ replying to Tamar
That could help too, but idempotence is more reliable.
TR
Trinidad 6 months ago
↳ replying to Tamar
But what about max in flight requests?
CH
Chara 6 months ago
↳ replying to Tamar
Definitely! It prevents duplicates effectively.
DA
Danica 10 months ago
↳ replying to Tamar
I think enabling idempotence is key here.
0/2000 characters

Save Cancel