300-420 Question #178: Real Exam Question with Answer & Explanation

Question

Drag and Drop Question Drag and drop the elements from the left onto the YANG models where they and used on the right. Answer:

Explanation

This drag-and-drop question assesses knowledge of network management protocols and data models by requiring the categorization of elements into either IETF YANG Push Coverage or OpenConfig Telemetry Coverage.

Approach. The correct interaction is to drag 'XML' and 'NETCONF' into the 'IETF YANG Push Coverage' container, and 'GBP' and 'gNMI' into the 'OpenConfig Telemetry Coverage' container.

• IETF YANG Push Coverage:

  • XML: The Network Configuration Protocol (NETCONF), an IETF standard, uses YANG for data modeling and relies on XML (Extensible Markup Language) as its primary encoding format for configuration and operational data. IETF YANG Push mechanisms are often closely related to or leverage NETCONF principles, making XML a relevant component for data encoding.
  • NETCONF: NETCONF is an IETF standard protocol used for installing, manipulating, and deleting configuration data on network devices. It uses YANG data models. IETF YANG Push leverages existing IETF standards, and NETCONF is a fundamental protocol for configuration and data retrieval within the IETF framework, thus falling under its coverage.

• OpenConfig Telemetry Coverage:

  • GBP: 'GBP' stands for Group-Based Policy. OpenConfig aims to define vendor-neutral YANG models for various aspects of network configuration and operational state, including advanced policy definitions. Telemetry collected via OpenConfig would encompass the operational state and effectiveness of such policies. Therefore, Group-Based Policy, as a concept modeled by OpenConfig, aligns with OpenConfig Telemetry's coverage.
  • gNMI: The gRPC Network Management Interface (gNMI) is a gRPC-based protocol specifically developed in conjunction with OpenConfig. It provides a single service for configuration management and operational state retrieval (telemetry streaming) from network devices, making it the primary protocol for OpenConfig Telemetry.

Common mistakes.

• common_mistake. Common mistakes include incorrectly associating protocols or data formats with the wrong framework. For instance:
• Placing 'gNMI' or 'GBP' into 'IETF YANG Push Coverage' is incorrect because gNMI is an OpenConfig-led initiative for telemetry, and GBP represents a concept that OpenConfig models aim to cover. IETF YANG Push primarily leverages existing IETF protocols like NETCONF/RESTCONF.
• Placing 'XML' or 'NETCONF' into 'OpenConfig Telemetry Coverage' would be incorrect because while OpenConfig uses YANG, its primary telemetry protocol is gNMI, and it often uses Protobuf over gRPC for transport rather than XML for streaming telemetry data. NETCONF is a distinct IETF protocol, not the primary mechanism for OpenConfig telemetry.

Concept tested. This question tests the understanding of network management standards and technologies, specifically: IETF YANG Push, OpenConfig Telemetry, NETCONF protocol, gNMI protocol, XML data encoding, and the concept of Group-Based Policy (GBP) within the context of network configuration and telemetry.

No community discussion yet for this question.