Confluent CCDAK Exam - Topic 4 Question 84 Discussion

Actual exam question for Confluent's CCDAK exam

Question #: 84
Topic #: 4

[All CCDAK Questions]

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

Amax.in.flight.requests.per.connection=1

Benable.idempotence=true

Cretries=200000

Dbatch.size=1

Show Suggested Answer

Suggested Answer: B

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

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

Limited Time Offer

25%

Off

Get Premium CCDAK Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Lyda

24 hours ago

D seems too limiting. Batch size of 1 isn't efficient.

upvoted 0 times

...

Omega

6 days ago

I feel like C is overkill. 200,000 retries?

upvoted 0 times

...

Detra

11 days ago

A could work too, but it might slow things down.

upvoted 0 times

...

Shantay

16 days ago

I agree, B makes sense. Idempotence is key.

upvoted 0 times

...

Bettyann

22 days ago

I’m not sure about D, batch.size=1 feels limiting.

upvoted 0 times

...

Wendell

27 days ago

Totally agree with B, it’s essential for avoiding duplicates.

upvoted 0 times

...

Terina

2 months ago

Wait, retries=200000? That seems excessive!

upvoted 0 times

...

Leota

2 months ago

A) max.in.flight.requests.per.connection=1 is also a good choice.

upvoted 0 times

...

Krissy

2 months ago

B) enable.idempotence=true, because who wants to deal with network-induced duplicates? Not this guy!

upvoted 0 times

...

Goldie

2 months ago

I'd go with B as well. Retries and batch size won't help with duplicate prevention.

upvoted 0 times

...

Jose

2 months ago

Definitely B. Enabling idempotence is the way to go to prevent those pesky network-induced duplicates.

upvoted 0 times

...

Malissa

2 months ago

Batch size seems more about performance than duplicates, so I doubt D is correct. I’m really torn between A and B!

upvoted 0 times

...

Dalene

3 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.

upvoted 0 times

...

Tammara

3 months ago

I'm not entirely sure, but I remember something about max in-flight requests affecting duplicates. Maybe A is relevant?

upvoted 0 times

...

Corazon

3 months ago

I think enabling idempotence is the key here, so I would go with B. It sounds familiar from our practice sessions.

upvoted 0 times

...

Franchesca

3 months ago

B seems like the most straightforward solution. Enabling idempotence should do the trick.

upvoted 0 times

...

Jamie

3 months ago

I'm a bit confused on the difference between these options. I'll need to review the docs again.

upvoted 0 times

...

Hobert

3 months ago

I'm pretty sure the answer is B. Enabling idempotence is the way to go here.

upvoted 0 times

...

Felix

4 months ago

I think B is the best choice. It ensures no duplicates.

upvoted 0 times

...

Carmela

4 months ago

B) enable.idempotence=true is the way to go!

upvoted 0 times

...

Hildegarde

4 months ago

B) enable.idempotence=true is the correct answer.

upvoted 0 times

...

Daron

4 months ago

Option B is the way to go. Enabling idempotence is the key to avoiding those annoying duplicates.

upvoted 0 times

...

Reuben

5 months ago

Okay, let's see. Preventing duplicates is key, so I'm leaning towards B or D.

upvoted 0 times

...

Tamar

5 months ago

Hmm, this one's tricky. I'll need to think through the Kafka producer configs carefully.

upvoted 0 times

Danica

4 months ago

I think enabling idempotence is key here.

upvoted 0 times

...