Drag and drop the streaming telemetry use cases from the left onto the subscription type categories on the right.

Question

Explanation

This question tests knowledge of Model-Driven Streaming Telemetry (MDT) subscription types - specifically which use cases belong to 'dial-in' (dynamic) subscriptions versus 'dial-out' (configured/persistent) subscriptions. Understanding who initiates the connection and why determines the correct mapping.

Approach. Streaming telemetry has two subscription models defined by who initiates the transport connection. Dial-in (dynamic) subscriptions: the collector reaches into the device - best for ad-hoc troubleshooting, temporary monitoring sessions, and on-demand data collection where no persistent device config is desired. Dial-out (configured/static) subscriptions: the device initiates the push to the collector - best for always-on production monitoring, compliance data retention, survivability across collector restarts, and scenarios where the collector may be behind a NAT or firewall. Map each use case by asking: 'Is this temporary/on-demand (dial-in) or persistent/always-on (dial-out)?' Dial-in loses data if the collector disconnects; dial-out continues pushing regardless of collector state.

Concept tested. Model-Driven Telemetry (MDT) subscription types: Dial-in (dynamic) vs. Dial-out (configured) - including which scenarios each type is suited for, who initiates the gRPC/NETCONF transport session, and the operational trade-offs between on-demand visibility and persistent data streaming.

Reference. Cisco Model-Driven Telemetry documentation; CCNP/CCIE Enterprise Infrastructure - Streaming Telemetry (gRPC dial-in vs. dial-out); RFC 8641 (YANG Push Subscription)

No community discussion yet for this question.