An engineer edits a controller with HTTPS and a JSON body and calls the session NETCONF. Which description of NETCONF is accurate?
Select an answer to reveal the explanation.
Short Explanation
Your HTTPS call with a JSON body is a different door from NETCONF, which uses SSH to carry XML operations shaped by a YANG model. Your script may be a fine API call, but changing a controller setting does not make it NETCONF.
Full Explanation
NETCONF is a protocol that uses SSH and XML-encoded operations, such as retrieving and editing configuration. YANG is the model that describes the data those operations touch. An HTTPS call with a JSON body is not NETCONF, even if it edits the same controller; calling it NETCONF confuses it with a REST-style API call. Not every HTTPS JSON call is NETCONF, and the script can stay as it is under its real name. NETCONF is not a radio channel plan, and YANG is not an antenna model number: they are a protocol and a data model, not RF objects. NETCONF is also not a syslog feed; syslog is an event stream. YANG does not select a guest VLAN by itself. A VLAN change would be an edit to a node in a model, carried by a protocol, not a rename of the model into a VLAN picker. Exam caveat: RESTCONF can use YANG too, over HTTPS, often with JSON. The same models can be used with different protocols, so transport and encoding help distinguish them. Practical check: inspect the session. SSH with XML is NETCONF; HTTPS with JSON is not.