A fleet garage automation team must pick encodings for three jobs: REST controller calls, NETCONF device edits, and hand-maintained inventory files. Which mapping best matches common practice?
Select an answer to reveal the explanation.
Short Explanation
Match the tool to the job: JSON rides REST taxis, XML rides the NETCONF bus, and YAML sits on the clipboard while humans edit inventory. Mixing those roles is how garage automation gets lost on the wrong street.
Full Explanation
Practitioners typically use JSON with HTTP/REST controller and many device APIs, XML with NETCONF (YANG-modeled), and YAML for operator-friendly inventory and variable files. Swapping those roles—XML-only REST, YAML-as-NETCONF-wire, CSV-as-API—fights ecosystem conventions and tooling. Understanding when each encoding is preferred is the Domain 5 comparison skill, not memorizing one universal format.