400-007 · Question #242
Which feature is supported by NETCONF but is not supported by SNMP?
The correct answer is A. distinguishing between configuration data and operational data. NETCONF uniquely distinguishes between configuration datastores and operational state data, a separation that SNMP does not provide due to its flat MIB-based architecture.
Question
Which feature is supported by NETCONF but is not supported by SNMP?
Options
- Adistinguishing between configuration data and operational data
- Btaking administrative actions
- Ccollecting the status of specific fields
- Dchanging the configuration of specific fields
How the community answered
(43 responses)- A93% (40)
- B2% (1)
- C5% (2)
Why each option
NETCONF uniquely distinguishes between configuration datastores and operational state data, a separation that SNMP does not provide due to its flat MIB-based architecture.
NETCONF explicitly models separate datastores - running, candidate, and startup - for configuration data and provides distinct operations such as get-config versus get to retrieve configuration versus live operational state. SNMP's MIB hierarchy conflates configuration and operational data within the same object tree, offering no formal mechanism to differentiate between the two types of data.
Both NETCONF and SNMP support administrative actions - NETCONF through RPC operations and SNMP through SET operations on writable MIB objects.
Both protocols support collecting status of specific fields - NETCONF via get with subtree or XPath filters and SNMP via GET requests for specific OIDs.
Both protocols can change specific configuration fields - NETCONF via edit-config and SNMP via SET operations on writable MIB objects.
Concept tested: NETCONF configuration vs operational data distinction
Source: https://www.rfc-editor.org/rfc/rfc6241
Topics
Community Discussion
No community discussion yet for this question.