350-901 · Question #47
Which two data encoding techniques are supported by gRPC? (Choose two.)
The correct answer is B. JSON D. Protobuf. gRPC primarily uses Protocol Buffers (Protobuf) for its efficient, schema-driven data serialization, which is its native and recommended encoding.
Question
Options
- AXML
- BJSON
- CASCII
- DProtobuf
- EYAML
How the community answered
(21 responses)- A5% (1)
- B90% (19)
- E5% (1)
Why each option
gRPC primarily uses Protocol Buffers (Protobuf) for its efficient, schema-driven data serialization, which is its native and recommended encoding.
XML is not natively or commonly used as a data encoding technique in gRPC due to its verbosity and parsing overhead compared to Protobuf.
gRPC officially supports JSON as a data encoding format, especially for interoperability with web browsers and RESTful services, often via gRPC-JSON transcoding or helper libraries.
ASCII is a character encoding scheme, not a structured data serialization format used by gRPC for message payload exchange.
Protocol Buffers (Protobuf) is the primary, default, and highly efficient data serialization format designed specifically for gRPC, providing a schema-driven approach for defining service interfaces and message structures.
YAML is a human-friendly data serialization format but is not natively supported or commonly used for gRPC message encoding.
Concept tested: gRPC data encoding formats (Protobuf, JSON)
Source: https://grpc.io/docs/what-is-grpc/core-concepts/
Topics
Community Discussion
No community discussion yet for this question.