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

Cisco Exam 300-535 Topic 11 Question 48 Discussion

Actual exam question for Cisco's 300-535 exam
Question #: 48
Topic #: 11
[All 300-535 Questions]

Which data format should be used to serialize structured data in the most compact way?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Nikita
3 days ago
YAML is more human-readable than JSON, but I don't think it's as compact. XML is just too verbose for this use case.
upvoted 0 times
...
Leatha
8 days ago
Protobufs seem like the way to go here. They're designed for efficient serialization and are smaller than JSON in most cases.
upvoted 0 times
Elizabeth
2 days ago
I agree, protobufs are definitely more compact than JSON.
upvoted 0 times
...
...
Virgilio
14 days ago
I believe YAML is a good option as well, it strikes a balance between readability and compactness.
upvoted 0 times
...
Elsa
16 days ago
I prefer JSON because it is widely supported and easy to read.
upvoted 0 times
...
Shawna
19 days ago
I think protobufs would be the best choice for compact serialization.
upvoted 0 times
...
Candra
22 days ago
I think JSON is the most compact way to serialize structured data. It's lightweight and easy to read and write.
upvoted 0 times
Herman
6 days ago
I prefer using protobufs for serializing structured data. It's more efficient and compact.
upvoted 0 times
...
...
Aliza
22 days ago
I personally prefer JSON because it's more human-readable, even if it's not the most compact option.
upvoted 0 times
...
Doretha
29 days ago
I agree with Carin, protobufs are known for their efficiency in data serialization.
upvoted 0 times
...
Carin
30 days ago
I think protobufs would be the best choice for compact serialization.
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