Cyber Monday 2024! 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]

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.


Contribute your Thoughts:

Ulysses
4 months ago
Gotta be B. Full schema evolution is the only way to ensure our data stays pristine, right? Anything else is just asking for trouble.
upvoted 0 times
Gracia
2 months ago
C) backward
upvoted 0 times
...
Valentine
2 months ago
D) forward
upvoted 0 times
...
Catarina
2 months ago
B) full
upvoted 0 times
...
Herman
3 months ago
C) backward
upvoted 0 times
...
Jina
3 months ago
B) full
upvoted 0 times
...
Lucina
3 months ago
A) breaking
upvoted 0 times
...
Leonor
3 months ago
A) breaking
upvoted 0 times
...
...
Winfred
4 months ago
Hmm, I'm not so sure. This seems more like a full schema evolution to me. Avro is tricky, man.
upvoted 0 times
James
3 months ago
No, I believe it's a forward schema evolution.
upvoted 0 times
...
Gail
3 months ago
I think it's a breaking schema evolution.
upvoted 0 times
...
...
Fausto
4 months ago
I agree with Lanie, C) backward makes more sense in this context.
upvoted 0 times
...
Lanie
4 months ago
No, I believe it's C) backward because adding an element without a default is not breaking the existing schema.
upvoted 0 times
...
Phung
4 months ago
I think the answer is A) breaking.
upvoted 0 times
...
Nana
4 months ago
Definitely C. Backward schema evolution is the way to go here. We don't want to break existing applications, do we?
upvoted 0 times
...
Yvonne
4 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 consumers to read the new enum values but maintains compatibility with older consumers.
upvoted 0 times
Rosalia
3 months ago
Exactly, it allows new consumers to read new enum values.
upvoted 0 times
...
Christa
3 months ago
So, the answer is D, forward.
upvoted 0 times
...
Pete
3 months ago
It's important to maintain compatibility with older consumers.
upvoted 0 times
...
Hester
4 months ago
I agree, adding an element without a default is a forward schema evolution.
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