Model-Driven Telemetry

A network engineer is configuring model-driven telemetry on a Cisco IOS-XE router to stream interface statistics to a collector using gRPC. The engineer wants to ensure that the telemetry data is sent only when there is a change in the interface counters, rather than at a fixed interval. Which configuration parameter should the engineer use to achieve this behavior?

A network engineer is deploying model-driven telemetry on a Cisco Nexus 9000 switch to monitor BGP prefix changes. The engineer wants to use YANG data models and prefers a transport protocol that is lightweight and uses UDP. Which transport protocol should the engineer select for the telemetry stream?

A network engineer is configuring model-driven telemetry on a Cisco IOS-XE router to stream CPU and memory statistics to a collector. The engineer wants to use the YANG model 'Cisco-IOS-XE-process-cpu-oper' and 'Cisco-IOS-XE-memory-oper'. After configuring the telemetry subscription, the engineer notices that no data is being received at the collector. The collector is reachable and the gRPC dial-out is configured correctly. What is the most likely cause of the issue?

A network engineer is designing a model-driven telemetry solution for a large enterprise network with thousands of devices. The engineer wants to minimize the load on the network devices and the collector by sending data only when significant changes occur. The engineer decides to use on-change subscriptions. However, after deployment, the engineer notices that some subscriptions are sending updates too frequently, causing high CPU usage on the devices. What is the most likely reason for this excessive update frequency?

A network engineer is configuring model-driven telemetry on a Cisco IOS-XE router to stream BGP route updates to a collector using gRPC dial-out. The engineer wants to ensure that the telemetry data is encrypted in transit. Which additional configuration is required to secure the gRPC telemetry stream?

A network engineer is implementing model-driven telemetry on a Cisco Nexus 9000 switch to monitor VLAN and STP changes. The engineer wants to use the native telemetry protocol with UDP as the transport. After configuring the telemetry subscription with the 'destination-group' and 'sensor-group', the engineer notices that the collector is not receiving any data. The collector is reachable and the UDP port is open. What is the most likely missing configuration?

A network engineer is troubleshooting a model-driven telemetry deployment on a Cisco IOS-XE router. The telemetry subscription is configured to stream interface statistics using gRPC dial-out to a collector at 10.1.1.100:50051. The engineer verifies that the collector is listening on the port and the router can reach it. However, the collector shows no data received. The engineer checks the router's telemetry logs and sees 'Connection refused' errors. What is the most likely cause?

A network engineer is planning to deploy model-driven telemetry in a brownfield network with a mix of Cisco IOS-XE and Nexus devices. The engineer wants to use a single collector that supports both gRPC and UDP-based telemetry. The engineer is concerned about the scalability of the solution, as the network has over 5000 devices. Which design consideration is most important to ensure the telemetry solution scales effectively?

A network engineer is configuring model-driven telemetry on a Cisco IOS-XE router to stream OSPF neighbor state changes. The engineer uses the YANG model 'Cisco-IOS-XE-ospf-oper' and creates an on-change subscription. After testing, the engineer notices that the telemetry data is being sent, but the collector is receiving duplicate updates for the same OSPF neighbor state change. What is the most likely cause of these duplicate updates?

A network engineer writes the following Python script to collect telemetry data from a Cisco IOS-XE device using NETCONF: ```python from ncclient import manager m = manager.connect( host='192.168.1.1', port=830, username='admin', password='cisco', hostkey_verify=False ) filter = ''' <filter xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <interfaces xmlns="http://openconfig.net/yang/interfaces"> <interface> <name>GigabitEthernet1</name> </interface> </interfaces> </filter> ''' reply = m.get(filter=('subtree', filter)) print(reply.xml) m.close_session() ``` What is the issue with this code?

An engineer creates an Ansible playbook to configure model-driven telemetry on a Cisco IOS-XE device: ```yaml --- - name: Configure MDT subscription hosts: ios_xe gather_facts: no tasks: - name: Configure telemetry receiver cisco.ios.ios_config: lines: - telemetry ietf subscription 101 - receiver ip address 10.10.10.10 port 57500 protocol grpc-tcp - encoding encode-kvgpb - filter xpath /interfaces/interface/state/counters - update-policy periodic 5000 ``` What is the problem with this playbook?

A developer sends a RESTCONF request to retrieve interface statistics from a Cisco IOS-XE device: Request: ``` GET /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet1/statistics HTTP/1.1 Host: 192.168.1.1 Accept: application/yang-data+json ``` Response: ```json { "ietf-interfaces:statistics": { "discontinuity-time": "2023-01-01T00:00:00Z", "in-octets": 1000000, "in-errors": 0, "out-octets": 500000, "out-errors": 0 } } ``` What is the correct way to interpret this response?

A network engineer uses Cisco DNA Center API to retrieve the health of a device. The API call returns: ```json { "response": [ { "deviceId": "1234567890", "healthScore": 85, "overallHealth": "good", "memory": { "used": 4096, "total": 8192, "usage": 50 }, "cpu": { "usage": 25 } } ] } ``` What does the healthScore of 85 indicate?

An engineer configures gRPC dial-out telemetry on a Cisco IOS-XE device: ``` telemetry ietf subscription 100 receiver ip address 10.1.1.100 port 50051 protocol grpc-tcp source-address 10.1.1.1 encoding encode-kvgpb filter xpath /interfaces/interface/state/counters update-policy periodic 10000 ``` What is the purpose of the 'source-address' command?

A Python script using Netmiko to configure telemetry on a Cisco IOS-XE device: ```python from netmiko import ConnectHandler device = { 'device_type': 'cisco_ios', 'host': '192.168.1.1', 'username': 'admin', 'password': 'cisco', } connection = ConnectHandler(**device) config_commands = [ 'telemetry ietf subscription 200', 'receiver ip address 10.1.1.100 port 50051 protocol grpc-tcp', 'source-address 10.1.1.1', 'encoding encode-kvgpb', 'filter xpath /interfaces/interface/state/counters', 'update-policy periodic 10000' ] output = connection.send_config_set(config_commands) print(output) connection.disconnect() ``` What is the expected outcome of this script?

An engineer retrieves telemetry data from a Cisco IOS-XE device using RESTCONF and receives the following response: ```json { "ietf-interfaces:interfaces": { "interface": [ { "name": "GigabitEthernet1", "type": "iana-if-type:ethernetCsmacd", "enabled": true, "ipv4": { "address": [ { "ip": "192.168.1.1", "netmask": "255.255.255.0" } ] } } ] } } ``` What is the correct way to access the IP address of the interface using Python?

An Ansible playbook uses the cisco.ios.ios_telemetry module to configure a telemetry subscription: ```yaml --- - name: Configure telemetry subscription hosts: ios_xe gather_facts: no tasks: - name: Create telemetry subscription cisco.ios.ios_telemetry: state: present subscription_id: 300 receiver: ip: 10.1.1.100 port: 50051 protocol: grpc-tcp source_ip: 10.1.1.1 encoding: kvgpb filter: xpath: /interfaces/interface/state/counters update_policy: period: 10000 ``` What is the purpose of the 'state: present' parameter?

A network engineer uses the following Python code to subscribe to telemetry data from a Cisco IOS-XE device via NETCONF using the YANG module 'Cisco-IOS-XE-mdt-oper': ```python from ncclient import manager m = manager.connect( host='192.168.1.1', port=830, username='admin', password='cisco', hostkey_verify=False ) # Create a telemetry subscription subscription = ''' <config> <mdt-config-data xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-mdt-cfg"> <mdt-subscription> <subscription-id>400</subscription-id> <base> <stream>yang-push</stream> <encoding>encode-kvgpb</encoding> <period>5000</period> <xpath>/interfaces/interface/state/counters</xpath> </base> <mdt-receivers> <address>10.1.1.100</address> <port>50051</port> <protocol>grpc-tcp</protocol> </mdt-receivers> </mdt-subscription> </mdt-config-data> </config> ''' reply = m.edit_config(target='running', config=subscription) print(reply.xml) m.close_session() ``` What is the issue with this code?

Consider the following configuration snippet on a Cisco IOS-XE device: telemetry ietf subscription 100 encoding encode-kvgpb filter xpath /interfaces/interface/state/counters stream yang-push update-policy periodic 500 receiver ip address 10.1.1.1 50000 protocol grpc What is the effect of this configuration?

Examine the following telemetry configuration on a Cisco IOS-XE device: telemetry ietf subscription 200 encoding encode-kvgpb filter xpath /interfaces/interface[name='GigabitEthernet0/0/0']/state stream yang-push update-policy on-change receiver ip address 192.168.1.100 50001 protocol grpc Which statement is true about this configuration?

Review the following telemetry configuration snippet: telemetry ietf subscription 300 encoding encode-kvgpb filter xpath /interfaces/interface/state/counters stream yang-push update-policy periodic 100 receiver ip address 10.1.1.1 50000 protocol grpc What is missing or incorrect in this configuration?

Given this telemetry configuration on a Cisco IOS-XE device: telemetry ietf subscription 400 encoding encode-kvgpb filter xpath /interfaces/interface/state stream yang-push update-policy periodic 1000 receiver ip address 10.1.1.1 50000 protocol grpc source-interface Loopback0 What is the effect of the source-interface Loopback0 command?

Examine the following telemetry configuration: telemetry ietf subscription 500 encoding encode-kvgpb filter xpath /interfaces/interface/state/counters stream yang-push update-policy periodic 500 receiver ip address 10.1.1.1 50000 protocol grpc A network engineer wants to add a second receiver for redundancy. Which additional configuration is correct?

Consider the following telemetry configuration on a Cisco IOS-XE device: telemetry ietf subscription 600 encoding encode-kvgpb filter xpath /interfaces/interface/state stream yang-push update-policy on-change receiver ip address 10.1.1.1 50000 protocol grpc What is a potential issue with this configuration?

What is the default update interval for a Cisco IOS-XE telemetry subscription when using update-policy periodic without specifying a value?

Which of the following is a valid transport protocol for model-driven telemetry receivers on Cisco IOS-XE?

What is the purpose of the 'source-interface' command under a telemetry receiver configuration?

Drag and drop the steps of the gRPC dial-out telemetry subscription flow into the correct order, from first to last.

Drag and drop the steps of configuring NETCONF YANG-based telemetry with on-change subscription into the correct order, from first to last.

Drag and drop the steps of troubleshooting a model-driven telemetry subscription using CLI into the correct order, from first to last.

Drag and drop the steps of YANG push periodic vs on-change subscription into the correct order, from first to last.

Drag and drop the steps of gRPC dial-in telemetry session from collector into the correct order, from first to last.

Drag and drop the steps of Cisco IOS-XE mdt subscription via CLI configuration into the correct order, from first to last.

Drag and drop the steps of telemetry path validation using YANG DevKit into the correct order, from first to last.

Drag and drop the steps of OpenConfig interface counters subscription and decode into the correct order, from first to last.

Drag and drop the steps of YANG push periodic vs on-change subscription into the correct order, from first to last.

Drag and drop the steps of gRPC dial-in telemetry session from collector into the correct order, from first to last.

Drag and drop the steps of Cisco IOS-XE mdt subscription via CLI configuration into the correct order, from first to last.

Drag and drop the steps of telemetry path validation using YANG DevKit into the correct order, from first to last.

Drag and drop the steps of OpenConfig interface counters subscription and decode into the correct order, from first to last.

Drag and drop each telemetry protocol on the left to its matching transport on the right.

Drag and drop each YANG module on the left to its matching data category on the right.

Drag and drop each gRPC method on the left to its matching subscription type on the right.

Drag and drop each telemetry encoding on the left to its matching format on the right.

Drag and drop each streaming telemetry mode on the left to its matching trigger on the right.

Drag and drop each telemetry protocol on the left to its matching transport on the right.

Drag and drop each YANG module on the left to its matching data category on the right.

Drag and drop each gRPC method on the left to its matching subscription type on the right.

Drag and drop each telemetry encoding on the left to its matching format on the right.

Drag and drop each streaming telemetry mode on the left to its matching trigger on the right.

Which two statements about YANG data models in model-driven telemetry are true? (Choose two.)

Which two statements about telemetry subscription modes are true? (Choose two.)

Which three statements about encoding formats in model-driven telemetry are true? (Choose three.)

Which three statements about telemetry data collection intervals and on-change notifications are true? (Choose three.)

Which two statements about YANG data models and their role in model-driven telemetry are true? (Choose two.)

Which two statements about telemetry subscription types in model-driven telemetry are true? (Choose two.)

Which three statements about gRPC and gNMI in the context of model-driven telemetry are true? (Choose three.)

Which three statements about configuring model-driven telemetry on Cisco IOS-XE devices are true? (Choose three.)