350-901 · Question #100
What is a consideration for using gRPC as the model-driven telemetry protocol on a Cisco IOS XE device?
The correct answer is B. works in dial-out mode. gRPC-based model-driven telemetry on Cisco IOS XE supports dial-out mode, where the device initiates the connection to the collector rather than waiting to be polled.
Question
Exhibit
Options
- AXML-based transmission format
- Bworks in dial-out mode
- Chuman-readable transmission format
- Dworks in call-out mode
How the community answered
(23 responses)- B87% (20)
- C9% (2)
- D4% (1)
Why each option
gRPC-based model-driven telemetry on Cisco IOS XE supports dial-out mode, where the device initiates the connection to the collector rather than waiting to be polled.
gRPC uses Protocol Buffers (protobuf) as its encoding format, which is a compact binary format - not XML. XML is associated with NETCONF-based telemetry.
gRPC on Cisco IOS XE operates in dial-out (also called dial-out subscription) mode, meaning the network device establishes the outbound TCP connection to the telemetry receiver. This is a key characteristic that distinguishes gRPC from NETCONF-based dial-in telemetry, where the collector initiates the session.
Protocol Buffers encoding used by gRPC is binary and not human-readable. Human-readable formats such as JSON or XML are associated with other telemetry encodings like NETCONF or RESTCONF.
'Call-out mode' is not a defined or valid telemetry operational mode in Cisco IOS XE documentation. The correct terminology is 'dial-out mode'.
Concept tested: gRPC model-driven telemetry dial-out mode on IOS XE
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/prog/configuration/1612/b_1612_programmability_cg/model_driven_telemetry.html
Topics
Community Discussion
No community discussion yet for this question.