Drag and Drop Question. Drag and drop the characteristic from the left onto the monitoring type described on the right.

Question

Exhibit

Explanation

The Python code snippet demonstrates programmatic retrieval of structured network data using the RESTCONF protocol over HTTPS, leveraging YANG data models and JSON encoding.

Approach. Given a drag-and-drop question where characteristics are mapped to monitoring types, this Python code unequivocally depicts a RESTCONF interaction. The correct interaction would involve dragging characteristics that describe RESTCONF, as evidenced by the code. The key characteristics shown in the code are:

1. Client-initiated, pull-based communication: The 'requests.get()' method signifies that the client actively requests data from the network device.
2. Uses HTTP/HTTPS as the transport protocol: The URL 'https://10.10.20.48:443...' clearly indicates secure HTTP.
3. Leverages YANG data models for structured data: The HTTP headers ('application/yang-data+json') and the URI path ('ietf-interfaces:interfaces', 'ietf-ip:ipv4') explicitly refer to YANG data models, ensuring structured data representation.
4. Data encoded in JSON: The 'yang-data+json' header confirms JSON as the data encoding format. Therefore, the characteristics that should be dragged onto the 'RESTCONF' monitoring type are those reflecting its pull-based nature, use of HTTP/HTTPS, reliance on YANG data models, and JSON encoding.

Common mistakes.

• common_mistake. Common mistakes would involve incorrectly identifying the monitoring type or misattributing its characteristics. For example:
• Selecting SNMP: SNMP uses MIBs and different protocols (e.g., UDP port 161/162). The code shows no MIBs or SNMP-specific interactions.
• Selecting Syslog: Syslog is for sending log messages (event-driven, often unstructured text), not for structured data retrieval via HTTP/HTTPS.
• Selecting NetFlow/IPFIX: These protocols are for collecting network flow statistics, not for retrieving interface configuration or operational state as shown.
• Selecting Streaming Telemetry: While Streaming Telemetry also uses YANG, it's primarily a push-based model where the device streams data proactively. The code clearly shows a client-initiated 'GET' (pull) request, not a subscription or push model.
• Selecting gRPC Network Management Interface (gNMI): gNMI uses gRPC for transport, which is distinct from HTTP/REST, even though it also leverages YANG. The code explicitly uses HTTP with the 'requests' library, not gRPC.

Concept tested. Network Programmability and Automation - specifically, the understanding of different network device data retrieval protocols and their characteristics, including RESTCONF, YANG data models, HTTP/HTTPS, and JSON encoding.

No community discussion yet for this question.