nerdexam
Cisco

350-501 · Question #547

Refer to the exhibit. The networking team must design a solution to provide as much detail about the network as possible. The network has almost 2000 network devices, including firewalls and load…

The correct answer is B. Configure encoding self-describing-gpb under destination-group D. Configure protocol grpc no-tls under the destination-group. To provide detailed telemetry data from nearly 2000 devices without encryption, the team should configure gRPC as the protocol without TLS and use self-describing-gpb for efficient data encoding.

Automation and Assurance

Question

Refer to the exhibit. The networking team must design a solution to provide as much detail about the network as possible. The network has almost 2000 network devices, including firewalls and load balancers The team has decided to enable telemetry and monitor CPU usage on all devices. The log collector has been configured with IP address 172.41.41.1. and the process is running on port 8021. Due to open-source software limitations, the log collector does not support encryption. Which two configurations should the Team include in the configuration template to achieve this Goal? (Choose two)

Exhibit

350-501 question #547 exhibit

Options

  • AConfigure protocol tcp no-tls under the subscription
  • BConfigure encoding self-describing-gpb under destination-group
  • CConfigure encoding tls-gpb under the sensor-group
  • DConfigure protocol grpc no-tls under the destination-group
  • EConfigure encoding gpb-tls-self under the subscription

How the community answered

(32 responses)
  • A
    13% (4)
  • B
    78% (25)
  • C
    6% (2)
  • E
    3% (1)

Why each option

To provide detailed telemetry data from nearly 2000 devices without encryption, the team should configure gRPC as the protocol without TLS and use self-describing-gpb for efficient data encoding.

AConfigure protocol tcp no-tls under the subscription

TCP is a transport layer protocol, not an application layer protocol like gRPC or gNMI used for telemetry. Configuring protocol tcp no-tls is not a valid or standard option for telemetry subscriptions.

BConfigure encoding self-describing-gpb under destination-groupCorrect

The self-describing-gpb encoding is a highly efficient, compact, and extensible format for transmitting structured data, which is ideal for detailed telemetry from a large number of devices. This encoding allows the receiver to understand the data structure without prior knowledge.

CConfigure encoding tls-gpb under the sensor-group

The tls-gpb encoding specifies the use of Transport Layer Security (TLS) for encryption, which contradicts the requirement that the log collector does not support encryption.

DConfigure protocol grpc no-tls under the destination-groupCorrect

The gRPC no-tls protocol provides a high-performance, open-source universal RPC framework for data streaming, and the 'no-tls' option explicitly bypasses encryption, aligning with the log collector's limitation of not supporting encryption.

EConfigure encoding gpb-tls-self under the subscription

The gpb-tls-self encoding is not a standard or recognized encoding type for network telemetry subscriptions; standard options include gpb, self-describing-gpb, or json.

Concept tested: Network telemetry configuration (gRPC, encoding, no-TLS)

Source: https://www.cisco.com/c/en/us/td/docs/iosxr/cisco_iosxr_telemetry/xr-652/configure/telemetry-cg/b-telemetry-cg-652-ol/b-telemetry-cg-652-ol_chapter_01.html

Topics

#Network Telemetry#Model-Driven Telemetry#gRPC#GPB Encoding

Community Discussion

No community discussion yet for this question.

Full 350-501 Practice