An animal control HQ collector will consume interface statistics from model-driven telemetry and must choose an encoding the collector stack supports. What should guide GPB versus JSON selection?
Select an answer to reveal the explanation.
Short Explanation
Encoding is the language the Edge and the collector both speak—GPB is compact binary, JSON is readable text. Pick the one your collector actually understands from what the platform offers. Talking both at once into a monolingual ear just drops the message.
Full Explanation
Animal-control collectors consuming interface statistics from model-driven telemetry must choose GPB versus JSON based on platform subscription options and what the collector can decode efficiently. Encoding selection is a compatibility and performance decision, not a religious preference. The stem asks what should guide the choice.
Always forcing ASCII syslog because GPB and JSON cannot carry interface stats is false. Using both encodings on every subscription regardless of collector support wastes resources and may fail. Preferring YAML text files on flash FTP-polled hourly abandons streaming telemetry encoding.
Exam caveat: self-describing JSON eases debugging; compact GPB often scales better—collectors must match dial-out encoding. Operational check: subscribe one sensor with the chosen encoding, verify decode in the collector, benchmark CPU/bandwidth, then standardize. Document encoding per platform family in the animal-control telemetry design. Record the chosen control and rejected alternatives in the municipal change record so future on-call engineers understand the failure modes avoided for city services. Re-validate after the next maintenance window that telemetry, API results, and device state still match the documented design intent.