A government engineer wants to read and edit wireless controller configuration as structured data over SSH, using a formal model of that data. Which pairing names the protocol and the model?
Select an answer to reveal the explanation.
Short Explanation
YANG is the blueprint, and NETCONF is the truck that hauls get and edit requests down the SSH session. You do not configure a radio profile by renaming the truck. If the script is editing structured config, you want that pair and not a trap log.
Full Explanation
YANG is a modeling language. A YANG module describes the configuration and state tree, including types and constraints. NETCONF is the protocol that carries operations such as retrieving configuration and editing it, and its usual transport is SSH. Together they are the pairing that matches structured read and edit over SSH. YANG is not a transport, and NETCONF is not an RF profile. Swapping the names produces a design you cannot configure. NETCONF is also not a syslog forwarder. Syslog is a separate notification path. You do not have to abandon NETCONF for REST merely to perform an edit; RESTCONF is an alternative protocol that can use the same YANG models, but it is not required by a failure of NETCONF to carry edits. SNMP traps are unstructured notifications by comparison, not the data model, and YANG does not select a channel by itself. A channel change would be an edit to whatever YANG node represents the radio, carried by the protocol. Exam caveat: the model has to be one the controller actually implements. A syntactically valid YANG document from a different platform will not edit this controller. Operational check: open an SSH session to the NETCONF port, retrieve the running configuration for one known WLAN, and confirm the reply is the modeled data rather than a CLI transcript.