Model-Driven Telemetry practice questions

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?

Trap 1: Use a periodic subscription with a sample-interval of 0

A sample-interval of 0 is invalid; periodic subscriptions require a positive integer for the interval.

Trap 2: Set the suppress-repetition flag in a periodic subscription

The suppress-repetition flag reduces duplicate updates but still sends data at the periodic interval, not only on change.

Trap 3: Use a dynamic subscription with a sample-interval of 1 second

A dynamic subscription with a sample-interval sends data periodically, not only on change.

A
Use a periodic subscription with a sample-interval of 0
Why wrong: A sample-interval of 0 is invalid; periodic subscriptions require a positive integer for the interval.
B
Configure an on-change subscription
An on-change subscription sends updates only when the monitored data changes, which matches the requirement.
C
Set the suppress-repetition flag in a periodic subscription
Why wrong: The suppress-repetition flag reduces duplicate updates but still sends data at the periodic interval, not only on change.
D
Use a dynamic subscription with a sample-interval of 1 second
Why wrong: A dynamic subscription with a sample-interval sends data periodically, not only on change.

Open the full BGP breakdown →

Question 2mediummultiple choice

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?

Trap 1: NETCONF

NETCONF uses SSH/TCP and is primarily for configuration management, not streaming telemetry.

Trap 2: RESTCONF

RESTCONF uses HTTP/TCP and is used for configuration and data retrieval, not streaming telemetry.

Trap 3: SNMP

SNMP uses UDP but is not model-driven telemetry; it uses MIBs, not YANG models.

A
gRPC
gRPC is the standard transport for model-driven telemetry on Cisco Nexus switches, though it uses TCP, not UDP. It is the only option that supports YANG data models.
B
NETCONF
Why wrong: NETCONF uses SSH/TCP and is primarily for configuration management, not streaming telemetry.
C
RESTCONF
Why wrong: RESTCONF uses HTTP/TCP and is used for configuration and data retrieval, not streaming telemetry.
D
SNMP
Why wrong: SNMP uses UDP but is not model-driven telemetry; it uses MIBs, not YANG models.

Question 3hardmultiple choice

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?

Trap 1: The YANG models specified are not supported on IOS-XE

Both 'Cisco-IOS-XE-process-cpu-oper' and 'Cisco-IOS-XE-memory-oper' are supported on IOS-XE.

Trap 2: The collector is blocking UDP traffic from the router

gRPC uses TCP, not UDP, so UDP blocking is irrelevant.

Trap 3: The engineer must enable 'ip http secure-server' for telemetry to…

HTTP secure-server is not required for gRPC telemetry; it is used for RESTCONF.

A
The YANG models specified are not supported on IOS-XE
Why wrong: Both 'Cisco-IOS-XE-process-cpu-oper' and 'Cisco-IOS-XE-memory-oper' are supported on IOS-XE.
B
The telemetry subscription is missing the 'source-interface' configuration
Without a source-interface, the router may use an unreachable IP address, causing the collector to drop the connection or not receive data.
C
The collector is blocking UDP traffic from the router
Why wrong: gRPC uses TCP, not UDP, so UDP blocking is irrelevant.
D
The engineer must enable 'ip http secure-server' for telemetry to work
Why wrong: HTTP secure-server is not required for gRPC telemetry; it is used for RESTCONF.

Question 4hardmultiple choice

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?

Trap 1: The engineer configured a sample-interval in addition to on-change,…

On-change subscriptions do not accept a sample-interval; if configured, it would be ignored or cause an error.

Trap 2: The collector is overwhelmed and sending back-pressure signals…

Back-pressure from the collector would not cause the device to send more updates; it might cause dropped data.

Trap 3: The engineer used JSON encoding instead of GPB, causing larger…

Encoding format affects payload size and CPU usage for encoding, but not the frequency of updates.

A
The engineer configured a sample-interval in addition to on-change, causing both periodic and on-change updates
Why wrong: On-change subscriptions do not accept a sample-interval; if configured, it would be ignored or cause an error.
B
The YANG paths include high-frequency changing leafs like interface counters or CPU load
On-change subscriptions trigger updates for any change in the monitored data, so including frequently changing leafs causes excessive updates.
C
The collector is overwhelmed and sending back-pressure signals causing retransmissions
Why wrong: Back-pressure from the collector would not cause the device to send more updates; it might cause dropped data.
D
The engineer used JSON encoding instead of GPB, causing larger payloads and more CPU usage
Why wrong: Encoding format affects payload size and CPU usage for encoding, but not the frequency of updates.

Open the full BGP breakdown →

Question 5mediummultiple choice

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?

Trap 1: Configure IPsec between the router and the collector

IPsec is a separate security layer and not natively supported for gRPC telemetry on IOS-XE.

Trap 2: Use SSH tunneling for the gRPC connection

SSH tunneling is not a standard method for securing gRPC telemetry; gRPC uses TLS natively.

Trap 3: Configure DTLS on the telemetry receiver

DTLS is used for UDP-based telemetry, not for gRPC which uses TCP.

A
Configure IPsec between the router and the collector
Why wrong: IPsec is a separate security layer and not natively supported for gRPC telemetry on IOS-XE.
B
Enable TLS on the gRPC connection by configuring a trustpoint and using the 'transport grpc tls' command
TLS provides encryption for gRPC telemetry, and IOS-XE supports it with proper trustpoint configuration.
C
Use SSH tunneling for the gRPC connection
Why wrong: SSH tunneling is not a standard method for securing gRPC telemetry; gRPC uses TLS natively.
D
Configure DTLS on the telemetry receiver
Why wrong: DTLS is used for UDP-based telemetry, not for gRPC which uses TCP.

Open the full VLAN trunking answer →

Question 6hardmultiple choice

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?

Trap 1: The engineer forgot to configure a 'source-interface' under the…

A source-interface is recommended but not mandatory; the switch will use the management interface by default.

Trap 2: The YANG models for VLAN and STP are not supported in the native…

Nexus supports YANG models for VLAN and STP in the native telemetry protocol.

Trap 3: The engineer used GPB encoding instead of JSON, and the collector…

Encoding mismatch would cause parsing issues, but the collector would still receive data; the issue is that no data is received at all.

A
The engineer forgot to configure a 'source-interface' under the destination-group
Why wrong: A source-interface is recommended but not mandatory; the switch will use the management interface by default.
B
The engineer did not create a 'policy' that binds the sensor-group and destination-group
On Nexus, a telemetry policy is required to link the sensor and destination groups; without it, no data is streamed.
C
The YANG models for VLAN and STP are not supported in the native telemetry protocol
Why wrong: Nexus supports YANG models for VLAN and STP in the native telemetry protocol.
D
The engineer used GPB encoding instead of JSON, and the collector only accepts JSON
Why wrong: Encoding mismatch would cause parsing issues, but the collector would still receive data; the issue is that no data is received at all.

Question 7mediummultiple choice

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?

Trap 1: The collector's firewall is blocking the connection from the router

If the firewall were blocking, the error would likely be 'No route to host' or timeout, not 'Connection refused'.

Trap 2: The telemetry subscription is missing the 'encoding' configuration

Missing encoding would not cause a connection refusal; the router would still attempt to connect.

Trap 3: The router's source-interface is not configured, causing the router…

If the source IP were unreachable, the error would be 'No route to host' or timeout, not 'Connection refused'.

A
The collector's firewall is blocking the connection from the router
Why wrong: If the firewall were blocking, the error would likely be 'No route to host' or timeout, not 'Connection refused'.
B
The gRPC server on the collector is not running or is listening on a different port
'Connection refused' occurs when the TCP SYN reaches the host but no application is listening on the specified port.
C
The telemetry subscription is missing the 'encoding' configuration
Why wrong: Missing encoding would not cause a connection refusal; the router would still attempt to connect.
D
The router's source-interface is not configured, causing the router to use an unreachable IP
Why wrong: If the source IP were unreachable, the error would be 'No route to host' or timeout, not 'Connection refused'.

Question 8hardmultiple choice

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?

Trap 1: Use only periodic subscriptions with long sample intervals to…

While reducing data volume helps, it does not address the fundamental scalability of the collector infrastructure.

Trap 2: Configure all devices to use the same YANG model to simplify the…

Using the same YANG model is not feasible for different device types and does not address scalability.

Trap 3: Use a single transport protocol (gRPC) for all devices to reduce…

Nexus devices may use native UDP telemetry, and forcing gRPC may not be supported or optimal; this does not solve scalability.

A
Use only periodic subscriptions with long sample intervals to reduce data volume
Why wrong: While reducing data volume helps, it does not address the fundamental scalability of the collector infrastructure.
B
Deploy a hierarchical collector architecture with load balancers to distribute telemetry streams across multiple collectors
This design allows horizontal scaling and prevents any single collector from being a bottleneck.
C
Configure all devices to use the same YANG model to simplify the collector configuration
Why wrong: Using the same YANG model is not feasible for different device types and does not address scalability.
D
Use a single transport protocol (gRPC) for all devices to reduce complexity
Why wrong: Nexus devices may use native UDP telemetry, and forcing gRPC may not be supported or optimal; this does not solve scalability.

Review the full OSPF breakdown →

Question 9easymultiple choice

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?

Trap 1: The subscription is configured with both on-change and periodic…

On-change subscriptions do not support periodic updates; if both are configured, it would be an error.

Trap 2: The collector is sending acknowledgments that cause the router to…

gRPC does not use acknowledgments for telemetry data; it is a one-way stream.

Trap 3: The engineer used JSON encoding which causes larger payloads and…

Encoding does not cause duplicate updates; fragmentation would not create duplicates.

A
The subscription is configured with both on-change and periodic updates
Why wrong: On-change subscriptions do not support periodic updates; if both are configured, it would be an error.
B
The YANG path includes multiple leafs that change together, each triggering a separate update
On-change subscriptions send an update for each leaf that changes, so multiple leaf changes from a single event cause duplicate updates.
C
The collector is sending acknowledgments that cause the router to resend data
Why wrong: gRPC does not use acknowledgments for telemetry data; it is a one-way stream.
D
The engineer used JSON encoding which causes larger payloads and fragmentation
Why wrong: Encoding does not cause duplicate updates; fragmentation would not create duplicates.

Question 10mediummultiple choice

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?

Trap 1: The hostkey_verify=False is insecure and should be set to True.

While insecure, this is common in lab environments and not the primary issue.

Trap 2: The interface name should be 'GigabitEthernet0/0' to match Cisco…

The interface name in OpenConfig is typically 'GigabitEthernet1' and is not the cause of the error.

Trap 3: The filter XML uses the wrong namespace for interfaces.

The namespace http://openconfig.net/yang/interfaces is correct for OpenConfig.

A
The filter is passed as a string instead of a tuple with filter type.
ncclient requires filter=('subtree', filter_xml) to specify the filter type.
B
The hostkey_verify=False is insecure and should be set to True.
Why wrong: While insecure, this is common in lab environments and not the primary issue.
C
The interface name should be 'GigabitEthernet0/0' to match Cisco naming.
Why wrong: The interface name in OpenConfig is typically 'GigabitEthernet1' and is not the cause of the error.
D
The filter XML uses the wrong namespace for interfaces.
Why wrong: The namespace http://openconfig.net/yang/interfaces is correct for OpenConfig.

Read the full Ansible explanation →

Question 11hardmultiple choice

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?

Trap 1: The 'encoding encode-kvgpb' should be 'encoding encode-json'.

KVGPB (Key-Value Google Protocol Buffers) is a valid encoding for MDT.

Trap 2: The 'update-policy periodic 5000' should be 'update-policy periodic…

The period is in milliseconds, so 5000 is correct.

Trap 3: The 'filter xpath' path is invalid for IOS-XE.

The XPath /interfaces/interface/state/counters is valid for OpenConfig.

A
The playbook is missing the 'source-address' command under the receiver.
The receiver must include a source-address to specify the IP address from which telemetry data is sent.
B
The 'encoding encode-kvgpb' should be 'encoding encode-json'.
Why wrong: KVGPB (Key-Value Google Protocol Buffers) is a valid encoding for MDT.
C
The 'update-policy periodic 5000' should be 'update-policy periodic 5000 milliseconds'.
Why wrong: The period is in milliseconds, so 5000 is correct.
D
The 'filter xpath' path is invalid for IOS-XE.
Why wrong: The XPath /interfaces/interface/state/counters is valid for OpenConfig.

Question 12easymultiple choice

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?

Trap 1: The response shows the interface has 1,000,000 packets received and…

The fields are in-octets and out-octets, which count bytes, not packets.

Trap 2: The response indicates the interface has errors, so it is…

in-errors and out-errors are both 0, indicating no errors.

Trap 3: The response is invalid because the namespace should be…

The namespace 'ietf-interfaces' is correct for the interfaces model.

A
The response indicates the interface has 1,000,000 bytes received and 500,000 bytes transmitted.
in-octets is received bytes, out-octets is transmitted bytes.
B
The response shows the interface has 1,000,000 packets received and 500,000 packets transmitted.
Why wrong: The fields are in-octets and out-octets, which count bytes, not packets.
C
The response indicates the interface has errors, so it is malfunctioning.
Why wrong: in-errors and out-errors are both 0, indicating no errors.
D
The response is invalid because the namespace should be 'ietf-interfaces:interfaces-state'.
Why wrong: The namespace 'ietf-interfaces' is correct for the interfaces model.

Question 13easymultiple choice

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?

Trap 1: The device is critical and needs immediate attention.

A score of 85 is not critical; critical is below 50.

Trap 2: The device has 85% memory usage.

Memory usage is 50% as shown in the response.

Trap 3: The device has 85% CPU usage.

CPU usage is 25% as shown in the response.

A
The device is healthy with a score of 85 out of 100.
A health score of 85 is in the 'good' range (75-90) per DNA Center documentation.
B
The device is critical and needs immediate attention.
Why wrong: A score of 85 is not critical; critical is below 50.
C
The device has 85% memory usage.
Why wrong: Memory usage is 50% as shown in the response.
D
The device has 85% CPU usage.
Why wrong: CPU usage is 25% as shown in the response.

Question 14mediummultiple choice

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?

Trap 1: It specifies the IP address of the telemetry receiver.

The receiver IP is specified in the 'receiver ip address' command.

Trap 2: It enables the device to receive telemetry data from the receiver.

This is a dial-out configuration, so the device sends data, not receives.

Trap 3: It specifies the IP address of the network management station.

The receiver is the management station, but this command sets the source, not the destination.

A
It specifies the IP address of the telemetry receiver.
Why wrong: The receiver IP is specified in the 'receiver ip address' command.
B
It specifies the source IP address for the telemetry stream.
The source-address defines the IP address used as the source in the telemetry packets.
C
It enables the device to receive telemetry data from the receiver.
Why wrong: This is a dial-out configuration, so the device sends data, not receives.
D
It specifies the IP address of the network management station.
Why wrong: The receiver is the management station, but this command sets the source, not the destination.

Question 15mediummultiple choice

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?

Trap 1: The script will fail because 'telemetry ietf subscription' is not a…

This is a valid command on IOS-XE 16.6+.

Trap 2: The script will fail because 'send_config_set' requires a list of…

The commands are already in a list, which is correct.

Trap 3: The script will fail because the device_type should be 'cisco_xe'.

Both 'cisco_ios' and 'cisco_xe' are accepted for IOS-XE devices.

A
The script will configure the telemetry subscription and print the configuration output.
The script uses correct Netmiko syntax and valid IOS-XE commands.
B
The script will fail because 'telemetry ietf subscription' is not a valid command.
Why wrong: This is a valid command on IOS-XE 16.6+.
C
The script will fail because 'send_config_set' requires a list of strings.
Why wrong: The commands are already in a list, which is correct.
D
The script will fail because the device_type should be 'cisco_xe'.
Why wrong: Both 'cisco_ios' and 'cisco_xe' are accepted for IOS-XE devices.

Question 16mediummultiple choice

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?

Trap 1: data['interface'][0]['ipv4']['address']['ip']

Missing the top-level key 'ietf-interfaces:interfaces'.

Trap 2: data['interfaces']['interface']['ipv4']['address']['ip']

The key is 'ietf-interfaces:interfaces', not 'interfaces', and the interface list requires index.

Trap 3: data['ietf-interfaces:interfaces']['interface']['ipv4']['address'][0…

Missing the list index for 'interface'; it should be [0].

A
data['ietf-interfaces:interfaces']['interface'][0]['ipv4']['address'][0]['ip']
This correctly navigates the nested JSON structure.
B
data['interface'][0]['ipv4']['address']['ip']
Why wrong: Missing the top-level key 'ietf-interfaces:interfaces'.
C
data['interfaces']['interface']['ipv4']['address']['ip']
Why wrong: The key is 'ietf-interfaces:interfaces', not 'interfaces', and the interface list requires index.
D
data['ietf-interfaces:interfaces']['interface']['ipv4']['address'][0]['ip']
Why wrong: Missing the list index for 'interface'; it should be [0].

Read the full Ansible explanation →

Question 17easymultiple choice

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?

Trap 1: It checks if the subscription is currently active.

state: present does not check activity; it ensures configuration exists.

Trap 2: It removes the subscription if it exists.

That would be state: absent.

Trap 3: It displays the current subscription configuration.

state: present modifies configuration, not displays it.

A
It ensures the subscription is present in the running configuration.
state: present creates or updates the subscription to match the desired state.
B
It checks if the subscription is currently active.
Why wrong: state: present does not check activity; it ensures configuration exists.
C
It removes the subscription if it exists.
Why wrong: That would be state: absent.
D
It displays the current subscription configuration.
Why wrong: state: present modifies configuration, not displays it.

Question 18hardmultiple choice

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?

Trap 1: The XML namespace is incorrect; it should be…

The namespace is for configuration, not operational data.

Trap 2: The xpath is invalid; it should be…

The xpath is correct for OpenConfig counters.

Trap 3: The subscription-id should be a string, not an integer.

The YANG model defines subscription-id as an integer.

A
The code uses target='running' which may not be writable; it should use target='candidate' and then commit.
IOS-XE NETCONF typically requires candidate configuration and commit.
B
The XML namespace is incorrect; it should be 'http://cisco.com/ns/yang/Cisco-IOS-XE-mdt-oper'.
Why wrong: The namespace is for configuration, not operational data.
C
The xpath is invalid; it should be '/interfaces/interface/state/counters'.
Why wrong: The xpath is correct for OpenConfig counters.
D
The subscription-id should be a string, not an integer.
Why wrong: The YANG model defines subscription-id as an integer.

Question 19mediummultiple choice

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?

Trap 1: It streams interface counter data every 500 seconds to the…

The update-policy periodic value is in milliseconds, not seconds.

Trap 2: It streams the entire YANG model for interfaces to the collector,…

The filter xpath restricts the data to /interfaces/interface/state/counters only.

Trap 3: It uses the NETCONF protocol to send data to the collector.

The receiver specifies protocol grpc, not NETCONF.

A
It streams interface counter data every 500 milliseconds to the collector at 10.1.1.1:50000 using gRPC.
The update-policy periodic 500 sets the interval to 500 ms, and the receiver uses gRPC on port 50000.
B
It streams interface counter data every 500 seconds to the collector at 10.1.1.1:50000 using gRPC.
Why wrong: The update-policy periodic value is in milliseconds, not seconds.
C
It streams the entire YANG model for interfaces to the collector, not just counters.
Why wrong: The filter xpath restricts the data to /interfaces/interface/state/counters only.
D
It uses the NETCONF protocol to send data to the collector.
Why wrong: The receiver specifies protocol grpc, not NETCONF.

Question 20mediummultiple choice

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?

Trap 1: Data is pushed every 200 seconds to the collector.

There is no periodic interval; on-change is event-driven.

Trap 2: The subscription uses JSON encoding.

The encoding is encode-kvgpb (KVPB), not JSON.

Trap 3: The filter selects all interfaces, not just GigabitEthernet0/0/0.

The filter includes an XPath predicate that selects only the interface with name GigabitEthernet0/0/0.

A
Data is pushed only when a change occurs in the state of GigabitEthernet0/0/0.
The update-policy on-change triggers updates only on state changes for that interface.
B
Data is pushed every 200 seconds to the collector.
Why wrong: There is no periodic interval; on-change is event-driven.
C
The subscription uses JSON encoding.
Why wrong: The encoding is encode-kvgpb (KVPB), not JSON.
D
The filter selects all interfaces, not just GigabitEthernet0/0/0.
Why wrong: The filter includes an XPath predicate that selects only the interface with name GigabitEthernet0/0/0.