Which of the following protocols does not support network configuration management?

Question

Options

• ALLDP
• BNETCONF
• CSSH
• DSNMP

• A
  79% (22)
• B
  7% (2)
• C
  4% (1)
• D
  11% (3)

Explanation

LLDP (Link Layer Discovery Protocol) is purely a Layer 2 neighbor discovery protocol - it allows devices to advertise their identity and capabilities to directly connected neighbors, but it has no mechanism to push, modify, or manage device configurations.

The distractors are each wrong for specific reasons:

• NETCONF (B) is purpose-built for network configuration management, using XML-encoded RPCs over SSH to read and write device configs per RFC 6241.
• SSH (C) provides a secure CLI channel through which administrators can directly configure network devices (routers, switches, firewalls, etc.).
• SNMP (D) supports configuration management via SET operations that write values to a device's MIB, and SNMPv3 is commonly used for this in enterprise environments.

Memory tip: Think of LLDP as a "name tag" protocol - devices only wear the tag so neighbors can read it. You can't write anything back through a name tag. If the protocol's job is to listen and learn, it can't configure and control.

No community discussion yet for this question.