Exam 300-535 topic 1 question 29 discussion

Protocol buffers are Google’s language-neutral, platform-neutral, extensible mechanism for serializing structured data in a manner that is similar to XML but is smaller, faster, and simpler. They define the structure of data and then generate source code to easily write and read your structured data to and from various data streams in various languages. Source: https://ondemandelearning.cisco.com/cisco-cte/spaui10/sections/3/pages/2

It's funny how B is the worst answer. It's the least structured of all four.

Google developed Protocol buffers (or Protobuf for short) to serve as the main language to define both the gRPC message format and RPC calls. Protocol buffers are one of the core technologies developed and used by Google to serialize data for communication between the elements of highly loaded systems. The reason they are so efficient has to do with the way the data is encoded for transmission: Only key indexes, data types, and values are converted to binary format and sent over the wire Indexes: The schema identifies an index associated with each variable name, as the names aren’t included in the Protobuf message sent over the wire. It is the indexes that are included. This is very different from XML and JSON data formats, where the actual key names are transferred. The indexes are both an advantage and a disadvantage of the Protobuf: On the one hand, they allow you to save a lot of bandwidth on the wire, especially in bandwidth-hungry applications such as streaming telemetry.

Protobuf is the most compact

Protobuf is the most compact of the options Ref: https://blog.mbedded.ninja/programming/serialization-formats/a-comparison-of-serialization-formats/#file-size-comparison