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 Exam CCDAK 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:

Lauran
23 days 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
24 days 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
...
Fannie
1 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
22 hours ago
C) Reduce throughput
upvoted 0 times
...
Filiberto
7 days ago
B) Message order not preserved
upvoted 0 times
...
Wilbert
20 days ago
A) At least once delivery is not guaranteed
upvoted 0 times
...
...
Carri
1 months ago
But increasing max.in.flight.requests.per.connection can also improve throughput, so it's a trade-off.
upvoted 0 times
...
Lottie
2 months ago
I agree with Jame. Enabling retries in a producer can lead to duplicate messages being sent.
upvoted 0 times
...
Jame
2 months ago
I think the risk is that at least once delivery is not guaranteed.
upvoted 0 times
...

Save Cancel