A election office automation team must integrate county scripts with a controller northbound API that returns structured objects for inventory and health. Which data encoding is the most common fit for that REST-style integration?
Select an answer to reveal the explanation.
Short Explanation
Controller APIs speak the same language web apps do: JSON. It is curly-brace structured data your Python scripts chew into dicts and lists. Syslog novels, serial bitstreams, and print jobs are not how modern civic automation talks to controllers.
Full Explanation
JSON is the dominant encoding for REST/HTTP controller and device APIs because it maps cleanly to objects, arrays, and scalar types that automation languages parse easily. Election-office scripts typically authenticate, GET/POST JSON, and branch on fields such as device status or site IDs. Unstructured syslog lacks reliable schema for inventory APIs. HDLC and PostScript are unrelated transport/print formats. Domain 5 starts with recognizing JSON as the everyday API payload format.