New Year Sale 2026! 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 3 Question 77 Discussion

Actual exam question for Confluent's CCDAK exam
Question #: 77
Topic #: 3
[All CCDAK Questions]

What is the risk of increasing max.in.flight.requests.per.connection while also enabling retries in a producer?

Show Suggested Answer Hide Answer
Suggested Answer: B

Some messages may require multiple retries. If there are more than 1 requests in flight, it may result in messages received out of order. Note an exception to this rule is if you enable the producer settingenable.idempotence=true which takes care of the out of ordering case on its own. Seehttps://issues.apache.org/jira/browse/KAFKA-5494


Contribute your Thoughts:

0/2000 characters
Melvin
2 months ago
Wait, so retries can actually cause more problems?
upvoted 0 times
...
Aja
2 months ago
Totally agree, message order can get messed up too!
upvoted 0 times
...
Tyisha
3 months ago
I thought increasing requests would boost throughput, not reduce it?
upvoted 0 times
...
Kirby
3 months ago
Less resilient? That sounds risky!
upvoted 0 times
...
Erasmo
3 months ago
A higher max in-flight requests can lead to at least once delivery issues.
upvoted 0 times
...
Emmanuel
3 months ago
Less resilient sounds familiar, but I’m not confident if that’s the main risk here. I need to think back to the examples we went over in class.
upvoted 0 times
...
Laticia
4 months ago
I feel like reducing throughput might be a concern, but I can't recall the specifics. It seems like it could be related to how many requests are being processed at once.
upvoted 0 times
...
Brice
4 months ago
I think there was a practice question that mentioned message order not being preserved when retries are enabled. That could be a risk too.
upvoted 0 times
...
Gwenn
4 months ago
I remember something about how increasing max.in.flight.requests.per.connection can lead to at least once delivery issues, but I'm not entirely sure.
upvoted 0 times
...
Ronny
4 months ago
I'm feeling pretty confident about this one. Increasing the max in-flight requests while enabling retries is likely to reduce the overall reliability of the system, potentially leading to at least once delivery and message order issues. I'll make sure to select the best answer.
upvoted 0 times
...
Belen
4 months ago
Okay, I think I've got a handle on this. Increasing the max in-flight requests could reduce throughput, while enabling retries might impact message order. I'll need to be careful to balance these factors to ensure the system remains resilient.
upvoted 0 times
...
Katlyn
5 months ago
Hmm, this seems like a tricky one. Increasing the max in-flight requests could help improve throughput, but enabling retries might introduce some risks around message order and delivery guarantees. I'll need to weigh the pros and cons.
upvoted 0 times
...
Lashawnda
5 months ago
I'm a bit confused about how increasing max.in.flight.requests.per.connection and enabling retries in a producer could impact the system. I'll need to think through the potential tradeoffs carefully.
upvoted 0 times
...
Lauran
10 months ago
I think D is the way to go. 'Less resilient' sounds like the perfect recipe for a system that's as sturdy as a house of cards in a hurricane.
upvoted 0 times
...
Winfred
10 months ago
Ooh, C for sure! Reducing throughput is the way to go if you want to slow down your message delivery like a snail on a treadmill.
upvoted 0 times
Denae
8 months ago
D) Less resilient
upvoted 0 times
...
Jaleesa
8 months ago
A) At least once delivery is not guaranteed
upvoted 0 times
...
Antione
8 months ago
C) Reduce throughput
upvoted 0 times
...
...
Fannie
10 months ago
Increasing max.in.flight.requests.per.connection with retries? That's like putting a turbocharger on a tricycle - you're just asking for trouble!
upvoted 0 times
Shawna
9 months ago
C) Reduce throughput
upvoted 0 times
...
Filiberto
9 months ago
B) Message order not preserved
upvoted 0 times
...
Wilbert
9 months ago
A) At least once delivery is not guaranteed
upvoted 0 times
...
...
Carri
10 months ago
But increasing max.in.flight.requests.per.connection can also improve throughput, so it's a trade-off.
upvoted 0 times
...
Lottie
10 months ago
I agree with Jame. Enabling retries in a producer can lead to duplicate messages being sent.
upvoted 0 times
...
Jame
11 months ago
I think the risk is that at least once delivery is not guaranteed.
upvoted 0 times
...

Save Cancel