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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Confluent Exam CCDAK Topic 4 Question 71 Discussion

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

In Avro, adding an element to an enum without a default is a __ schema evolution

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.


by Cecil at Dec 11, 2024, 06:11 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Tawna
2 months ago
Exactly, it's all about ensuring that existing data can still be read correctly.
upvoted 0 times
...
Kirby
2 months ago
I think the answer is D. Forward schema evolution, because the new schema can be read by both old and new applications, even with the added enum element.
upvoted 0 times
Carolynn
28 days ago
No, it's forward schema evolution because the new schema is compatible with the old one.
upvoted 0 times
...
Colton
1 months ago
I think it might be backward schema evolution, actually.
upvoted 0 times
...
Shaunna
1 months ago
I agree, it's definitely forward schema evolution.
upvoted 0 times
...
...
Merrilee
2 months ago
Haha, this question is a real head-scratcher! I'm going to guess A. breaking schema evolution, because who knows what kind of chaos that enum change might cause.
upvoted 0 times
Leonardo
1 months ago
I'm not sure, but I'll go with B) full.
upvoted 0 times
...
Laurene
1 months ago
I agree with A) breaking.
upvoted 0 times
...
Man
1 months ago
I'm going with D) forward.
upvoted 0 times
...
Frederica
1 months ago
I think it's C) backward.
upvoted 0 times
...
...
Orville
2 months ago
Hmm, that makes sense. So, it's about maintaining compatibility with older versions?
upvoted 0 times
...
Tawna
2 months ago
No, I believe it's C) backward because you're adding an element without a default value.
upvoted 0 times
...
Nadine
2 months ago
Hmm, I'm not sure about this one. Let me think... I'll go with B. Full schema evolution, since the new schema is not entirely compatible with the old one.
upvoted 0 times
...
Orville
2 months ago
I think the answer is A) breaking.
upvoted 0 times
...
Fausto
2 months ago
I'm pretty sure it's C. Backward schema evolution means the new schema is compatible with the old one, and that's what adding an enum element without a default does.
upvoted 0 times
Curtis
2 months ago
Yes, adding an element to an enum without a default is a backward schema evolution. It maintains compatibility with the old schema.
upvoted 0 times
...
Rene
2 months ago
I think you're right, it's definitely C. Backward schema evolution makes sense in this case.
upvoted 0 times
...
...
Coletta
3 months ago
I think the answer is D. Adding an element to an enum without a default is a forward schema evolution, as it allows new applications to read the new enum values but older applications can still read the existing values.
upvoted 0 times
Terrilyn
1 months ago
Exactly, it allows new applications to read the new enum values.
upvoted 0 times
...
Justine
2 months ago
So, adding an element to an enum without a default is safe for older applications.
upvoted 0 times
...
Shaunna
2 months ago
Yes, you're right. It is a forward schema evolution.
upvoted 0 times
...
Wynell
2 months ago
I think the answer is D.
upvoted 0 times
...
...

Save Cancel