DevNet Associate (DEVASC) v1.0Infrastructure and AutomationMedium
A network operations team is implementing an event-driven automation system. They want to react automatically to specific network events, such as an interface going down or high CPU utilization. The system needs to capture these events as they occur and trigger predefined actions. Which mechanism is most suitable for receiving real-time, push-based notifications from network devices about these events?
- APeriodic RESTCONF GET requests
- BPolling via SNMP GET requests
- CNETCONF Notifications
- DSyslog messages
Show answer & explanationAnswer & explanation
Correct answer: C. NETCONF Notifications
NETCONF Notifications provide a standardized, structured, and push-based mechanism for network devices to send real-time event notifications to a subscribed client. Unlike polling or syslog, NETCONF Notifications deliver structured data about specific events as they happen, making them ideal for event-driven automation.
Why the other options are wrong
- A. Periodic RESTCONF GET requests are pull-based and incur latency, making them unsuitable for immediate, real-time event detection.
- B. Polling is pull-based, not real-time push, and inefficient for immediate event detection.
- D. Syslog messages are unstructured text and require complex parsing, making them less suitable for programmatic, structured event-driven automation.
NETCONF Notifications
NETCONF Notifications provide a mechanism for network devices to asynchronously send structured, real-time event information to subscribed clients. They are defined using YANG and delivered over the NETCONF session.
- Push-based, real-time events.
- Structured data (YANG-defined).
- Delivered over NETCONF session.
- Supports event-driven automation.
Memory trick: NETCONF Notifications 'NOTIFY' you of network events instantly.