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 2 Question 61 Discussion

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

How often is log compaction evaluated?

Show Suggested Answer Hide Answer
Suggested Answer: A

Since Confluent 5.4.0, Avro 1.9.1 is used. Since default value was added to enum complex type , the schema resolution changed from:

(<1.9.1) if both are enums:** if the writer's symbol is not present in the reader's enum, then an error is signalled. **(>=1.9.1) if both are enums:

if the writer's symbol is not present in the reader's enum and the reader has a default value, then that value is used, otherwise an error is signalled.


Contribute your Thoughts:

Josphine
4 days ago
Option A is interesting, but I don't think creating a new partition should automatically trigger log compaction.
upvoted 0 times
...
Lajuana
6 days ago
Option C is just silly. Log compaction has nothing to do with message sending in Kafka.
upvoted 0 times
...
Elliot
11 days ago
I'm not sure if Option D is correct. Flushing a message to disk doesn't necessarily mean it's time for log compaction.
upvoted 0 times
...
Malcolm
17 days ago
Hmm, I see. That makes sense too, since Kafka needs to keep track of messages being sent.
upvoted 0 times
...
Kristofer
18 days ago
Option B seems the most logical choice. Segment closes should trigger log compaction evaluation.
upvoted 0 times
Sherly
2 days ago
I think it's B) Every time a segment is closed.
upvoted 0 times
...
...
Kati
20 days ago
I believe it's actually evaluated every time a message is sent to Kafka.
upvoted 0 times
...
Malcolm
24 days ago
I think log compaction is evaluated every time a segment is closed.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77