Examkin

Question

Difficulty: Very hardImpact of Automation on Network Management

An enterprise network engineering team is evaluating the operational impact of transitioning from traditional SNMPv2c polling and manual CLI management to an automated, controller-based network architecture using RESTCONF and streaming telemetry. During a recent outage post-mortem, the team noted two major operational issues: high CPU utilization on core switches caused by frequent SNMP polling requests led to missed monitoring alerts, and manual CLI configuration updates across 200 branch switches caused severe configuration drift. Which statement accurately describes how adopting model-driven telemetry and centralized controller automation resolves these specific operational deficiencies?

  1. Streaming telemetry utilizes a push-based subscription model over protocols like gRPC to continuously transmit data without CPU-intensive polling, while centralized controllers leverage structured data models and APIs to enforce automated configuration consistency across all managed devices.Answer
  2. B
    Streaming telemetry requires installing heavy local software agents on each switch to aggregate SNMP traps before transmission, while controller automation uses agentless SSH script generation to eliminate the physical underlay network.
  3. C
    RESTCONF uses HTTP GET requests to continuously push streaming telemetry data to monitoring collectors without active subscriptions, while controller automation relies on HTTP PUT operations to perform initial device bootstrapping.
  4. D
    Model-driven telemetry automatically escalates SNMP polling severity to level 7 during high CPU events to prioritize monitoring traffic, while controller automation uses Syslog messages to autonomously overwrite invalid CLI commands.

Answer

Streaming telemetry utilizes a push-based subscription model over protocols like gRPC to continuously transmit data without CPU-intensive polling, while centralized controllers leverage structured data models and APIs to enforce automated configuration consistency across all managed devices.
The correct answer accurately reflects the two primary operational shifts brought by network automation: (1) Replacing pull-based SNMP polling with subscription-based streaming telemetry (e.g., gRPC, NETCONF, RESTCONF) to dramatically reduce device CPU overhead and improve monitoring granularity; and (2) Replacing manual CLI configuration with centralized controller APIs and data models (YANG) to automate change management, guarantee consistency, and prevent configuration drift.

Step-by-Step Solution

1
Analyze the operational deficiency related to network monitoring (SNMP polling overhead).
Identify that traditional SNMP uses a pull mechanism where management stations repeatedly query devices, causing high CPU consumption. Streaming telemetry solves this by using a push mechanism based on subscriptions, allowing devices to continuously stream structured data with significantly less overhead.
Understanding the shift from reactive pull-based polling to proactive push-based telemetry.
2
Analyze the operational deficiency related to device configuration management (configuration drift across 200 branch switches).
Identify that manual per-device CLI configuration leads to inconsistencies and human error. Centralized controller automation uses RESTful APIs and YANG data models to treat network configurations programmatically and declaratively, ensuring uniform deployment and automated compliance auditing.
Understanding how controller-driven automation enforces central intent and eliminates manual configuration errors.
3
Evaluate the choices to identify the statement that accurately addresses both telemetry push mechanics and controller-driven configuration consistency.
Select the option stating that streaming telemetry uses push subscriptions to eliminate polling overhead and centralized controllers use structured data models/APIs to enforce consistency.
Correlating the theoretical benefits of network automation with real-world enterprise operational shifts.

Key Concept

Operational impacts of network automation: Push-based telemetry vs SNMP polling, and controller/API-driven consistency vs manual CLI drift.
Rate this question

Topics

Impact of Automation on Network Management

More questions from this topic