Match each automation transport or interaction term to its most accurate description.
Drag a concept onto its matching description — or click a concept then click the description.
Encrypted transport commonly used for API communication
Architectural style often using HTTP methods
Structured data format commonly used in API payloads
Credential-like value often used to control API access
⚠ Common exam trap
Be careful not to confuse RESTCONF (stateless) with NETCONF (stateful). Also, remember that gRPC and SSH are stateful protocols.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
RESTCONF: A stateless, HTTP-based protocol that uses RESTful APIs and supports both XML and JSON data encoding.
Options A and B are correct. RESTCONF is a stateless, HTTP-based protocol that supports both XML and JSON encoding. NETCONF is a stateful, RPC-based protocol that uses XML encoding and operates over SSH or TLS. Option C is incorrect because gRPC is an RPC framework that can support both stateless and stateful interactions, but it is not stateless; it uses HTTP/2 and Protocol Buffers. Option D is incorrect because SSH is a stateful protocol that establishes an encrypted session for secure remote access and file transfers.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
RESTCONF: A stateless, HTTP-based protocol that uses RESTful APIs and supports both XML and JSON data encoding.
Why this is correct
RESTCONF is correctly described as stateless because each HTTP request carries all needed context and is processed independently, with no client session state retained on the server. It uses RESTful APIs over HTTP(S) and supports both XML and JSON payloads, making it a lightweight, programmable alternative to NETCONF for network automation. This operational model aligns with typical REST API behavior, similar to how a web browser fetches resources.
NETCONF: A stateful, RPC-based protocol that uses XML encoding and operates over SSH or TLS.
Why this is correct
NETCONF is accurately labeled stateful because it establishes a persistent, session-oriented connection—typically over SSH or TLS—where the client and server maintain a shared session context and lock datastores during transactions. It uses RPCs encoded in XML to perform operations like get, edit-config, and commit, and changes are staged in a candidate datastore before being applied. This stateful design supports transactionality and rollback, distinguishing it from stateless RESTCONF.
gRPC: A stateless, HTTP/2-based protocol that uses Protocol Buffers for data serialization.
Why it's wrong here
gRPC is mischaracterized as stateless; it is an RPC framework that can support both stateless and stateful interactions, and it runs over HTTP/2, which enables multiplexed streaming and persistent connections. Data serialization uses Protocol Buffers (protobuf), a compact binary format, not JSON or XML. Because HTTP/2 streams can maintain connection state and support bidirectional communication, calling gRPC stateless is inaccurate, even though individual calls may be independent.
When this WOULD be correct
A question asking: 'Which protocol uses HTTP/2 and Protocol Buffers for efficient, high-performance remote procedure calls?' would make gRPC the correct answer.
SSH: A stateless, secure shell protocol used for remote CLI access and file transfers.
Why it's wrong here
SSH is incorrectly described as stateless; it is a stateful protocol that begins with a handshake to negotiate encryption, authentication, and session keys, then maintains an encrypted session for the duration of the connection. The session includes state such as the established security context and remote command execution environment. While SSH is commonly used for remote CLI access and secure file transfers (e.g., SFTP), that doesn't make it stateless—each session carries state that persists across multiple command exchanges.
When this WOULD be correct
In a question asking 'Which protocol provides encrypted remote CLI access to network devices and supports secure file transfer using SCP or SFTP?', SSH would be the correct answer.
Option-by-option analysis
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The 200-301 exam frequently reuses these exact scenarios with slightly different constraints.
Why this is correct
RESTCONF is correctly described as stateless because each HTTP request carries all needed context and is processed independently, with no client session state retained on the server. It uses RESTful APIs over HTTP(S) and supports both XML and JSON payloads, making it a lightweight, programmable alternative to NETCONF for network automation. This operational model aligns with typical REST API behavior, similar to how a web browser fetches resources.
Why this is wrong here
gRPC is not stateless; it supports both stateless and stateful interactions, and it uses HTTP/2, not HTTP/1.1 or HTTP-based REST. The question asks for a stateless, HTTP-based protocol, which describes RESTCONF, not gRPC.
★ When this WOULD be the correct answer
A question asking: 'Which protocol uses HTTP/2 and Protocol Buffers for efficient, high-performance remote procedure calls?' would make gRPC the correct answer.
Why candidates choose this
Candidates may confuse gRPC's use of HTTP/2 with HTTP-based REST protocols, or mistakenly think gRPC is stateless due to its high-performance design, overlooking its support for stateful streams.
Why this is wrong here
SSH is not stateless; it establishes a persistent, stateful connection. It is also not primarily an automation transport for RESTful APIs or structured data encoding like XML/JSON, but rather a secure remote access protocol.
★ When this WOULD be the correct answer
In a question asking 'Which protocol provides encrypted remote CLI access to network devices and supports secure file transfer using SCP or SFTP?', SSH would be the correct answer.
Why candidates choose this
Candidates may confuse SSH's secure shell capabilities with automation transports, or mistakenly think SSH is stateless because it can be used for quick commands, overlooking its session-based stateful nature.
Analysis generated from the official 200-301blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
| Layer | Name | PDU | Key Protocols / Devices |
|---|---|---|---|
| 7 | Application | Data | HTTP, HTTPS, DNS, SMTP, FTP, SSH |
| 6 | Presentation | Data | TLS / SSL, JPEG, ASCII encoding |
| 5 | Session | Data | NetBIOS, RPC, SIP |
| 4 | Transport | Segment / Datagram | TCP, UDP |
| 3 | Network | Packet | IP, ICMP, OSPF — Routers |
| 2 | Data Link | Frame | Ethernet, Wi-Fi, PPP — Switches, Bridges |
| 1 | Physical | Bits | Cables, NICs, Hubs, Repeaters |
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: May 17, 2026
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.