Quick Answer

The correct match is that HTTP is not a standard telemetry transport, while gRPC uses HTTP/2, gNMI uses gRPC, NETCONF uses SSH, and RESTCONF uses HTTPS. This distinction arises because telemetry protocols are designed for efficient, streaming data collection rather than simple request-response interactions; gRPC leverages HTTP/2 for bidirectional streaming, gNMI builds on gRPC for network device management, NETCONF relies on SSH for secure session-based configuration, and RESTCONF uses HTTPS for stateless RESTful operations. On the ENCOR 350-401 exam, this drag-and-drop task tests your ability to differentiate between model-driven telemetry transports and common management protocols, with a common trap being to assume HTTP is a valid telemetry transport when it lacks the streaming and multiplexing capabilities required. Remember the hierarchy: gNMI rides on gRPC, which rides on HTTP/2, while NETCONF and RESTCONF are separate—SSH and HTTPS respectively. A useful memory tip is to think of the acronym “G2H” for gNMI, gRPC, and HTTP/2 as a chain, and note that plain HTTP is the odd one out because it is not a standard telemetry transport.