350-401 Practice Question: Is a valid transport protocol for model-driven…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  HTTP

  Why it's wrong here

  HTTP is a request-response protocol; model-driven telemetry pushes continuous streams, which HTTP cannot sustain. It is tempting because HTTP carries YANG-model data in RESTCONF, but that is configuration retrieval, not streaming telemetry. The valid transports are gRPC and NETCONF.

• ✓

  gRPC

  Why this is correct

  gRPC is a valid transport for model-driven telemetry on Cisco IOS-XE, carrying dial-out subscriptions over HTTP/2 with protobuf-encoded data. It satisfies the stem's receiver requirement, unlike NETCONF or RESTCONF, which are configuration and retrieval protocols rather than telemetry transports.

• ✗

  FTP

  Why it's wrong here

  FTP transfers files and provides no subscription or streaming mechanism for telemetry data. It is tempting because it is a familiar transport for moving bulk data between systems, but model-driven telemetry receivers expect gRPC or NETCONF, not file transfer.

• ✗

  SNMP

  Why it's wrong here

  SNMP is a poll-based protocol using OIDs and MIBs, not a transport for YANG-model-driven telemetry streams. It is tempting because SNMP has long been the standard monitoring mechanism on Cisco devices, but model-driven telemetry requires gRPC or NETCONF subscriptions instead.

Go deeper

Related to this question