City automation engineers want a model-driven way to set interface descriptions on IOS XE edge routers using YANG-based RPC operations over a secure management channel. Which protocol is the primary fit?
Select an answer to reveal the explanation.
Short Explanation
NETCONF is the structured remote-control language for boxes that speak YANG—ideal for pushing something like an interface description without scraping CLI text like it’s 1998.
Full Explanation
City automation engineers want a model-driven way to set interface descriptions on IOS XE edge routers using YANG-based RPC operations over a secure management channel. NETCONF is the primary fit: it provides model-driven configuration operations commonly transported over SSH, using YANG data models and RPC semantics (<edit-config>, <get-config>, etc.) rather than scraping CLI. That matches secure, structured interface-description changes on municipal edge routers.
Local SPAN to copy description strings to a syslog collector fails by concept—SPAN mirrors frames; it does not apply YANG configuration. IP SLA ICMP echo carrying YANG payloads in the data field is not a configuration API; IP SLA is synthetic monitoring. CDP v2 TLV updates as the only supported configuration API is false—CDP is neighbor discovery, not a YANG RPC configuration protocol.
Exam caveat: associate NETCONF with YANG + RPC + SSH (commonly), and RESTCONF with YANG resources over HTTP/HTTPS. Both are model-driven; transport and operation style differ.
Operational check for city automation: enable NETCONF/SSH on the IOS XE edges, use a YANG-aware client to set an interface description, retrieve the interface resource/config to confirm the change, and ensure management ACLs allow the automation source without exposing broader VTYs unnecessarily.