SNMP and NETCONF are both commonly used network management protocols in campus networks, but they differ significantly in architecture, capabilities, and configuration management mechanisms. According to HCIP Datacom Campus Network documentation,NETCONF is designed for modern, model-driven network management, while SNMP is mainly used for monitoring and simple management.
Option A is incorrect because although both protocols use a client/server model, their roles are different. In SNMP, the managed device operates as an SNMP agent (server), while the NMS acts as the client. In NETCONF, the network device functions as the NETCONF server, and the management system is the client, not the other way around.
Option B is also incorrect because SNMP manages data using MIBs, whereas NETCONF usesdata models, typically based on YANG, instead of MIBs.
Option D is incorrect because SNMP does not support multiple configuration databases. It mainly provides basic read and write operations and is not suitable for complex configuration management or rollback.
Option C is correct. NETCONF provides alocking mechanismthat allows a client to lock a configuration datastore during configuration changes. This prevents multiple users or systems from modifying the same configuration simultaneously, avoiding conflicts and ensuring configuration consistency. This capability is a key advantage of NETCONF in intelligent campus network management and aligns with HCIP Datacom Campus Network best practices.
