A tax assessor validates an interface change on IOS XE over NETCONF and must inspect the protocol replies. Which encoding should the engineer expect in those NETCONF messages?
Select an answer to reveal the explanation.
Short Explanation
NETCONF is the XML conversation with the router. YANG names the fields; XML is the envelope and body you read when validating that interface change. YAML is great for humans elsewhere, but classic NETCONF replies show up as XML.
Full Explanation
NETCONF encodes RPCs, configuration, and operational data as XML, typically aligned to YANG models on IOS XE. Operators and tools (for example ncclient) parse XML trees for interface state and edit-config results. YAML is popular for inventory and Ansible-style content but is not the wire encoding of NETCONF. gNMI often uses protobuf; CSV is not a NETCONF payload format. Recognize XML’s role when validating model-driven changes over NETCONF.