Drag and drop the protocols/technologies on the left to the descriptions on the right.
Drag a concept onto its matching description — or click a concept then click the description.
Uses XML-encoded RPCs over SSH for network device configuration
Uses HTTP/HTTPS methods (GET, POST, PUT, DELETE) with JSON or XML
Data modeling language that defines the structure of configuration and state data
High-performance RPC framework using Protocol Buffers and HTTP/2
Vendor-neutral YANG data models for network configuration and monitoring
⚠ Common exam trap
Candidates often think Telnet is secure because it also provides remote access, but Telnet transmits data in plaintext. SSH uses encryption, making it the only secure option among these.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
SSH: Provides secure remote access to network devices using encryption, typically on TCP port 22.
SSH (Secure Shell) provides encrypted remote access to network devices, typically using TCP port 22. It is the secure alternative to Telnet. Telnet (port 23) is unencrypted and insecure. HTTP (port 80) is used for web traffic, not remote access. FTP (port 21) is for file transfers and is not designed for remote shell access. Therefore, only SSH matches the description of secure remote access.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
SSH: Provides secure remote access to network devices using encryption, typically on TCP port 22.
Why this is correct
SSH (Secure Shell) is the correct protocol for secure remote administration because it encrypts both authentication and session data, protecting credentials and commands from interception. It operates over TCP port 22 by default, using cryptographic algorithms like AES and key exchange methods such as Diffie-Hellman. Unlike Telnet or HTTP, SSH provides integrity verification and resistance to eavesdropping, man-in-the-middle, and session hijacking attacks, making it the standard for managing network devices such as routers and switches securely.
Telnet: Provides secure remote access to network devices using encryption, typically on TCP port 23.
Why it's wrong here
Telnet is incorrect because, while it does provide remote CLI access to network devices on TCP port 23, it transmits all data—including usernames and passwords—in plaintext. This lack of encryption allows any attacker with packet capture capabilities to read credentials and commands directly, compromising the device and network. Telnet has no built-in authentication security or integrity checks, and modern best practices mandate disabling it in favor of SSH, making this option's claim of secure remote access fundamentally false.
HTTP: Provides secure remote access to network devices using encryption, typically on TCP port 80.
Why it's wrong here
HTTP is not a protocol for remote device access at all; it is an application-layer protocol designed for transferring hypertext documents, such as web pages, over TCP port 80. Although some routers and switches expose a web-based GUI over HTTP for configuration, HTTP provides no encryption, so login credentials sent via HTTP forms are trivially captured. The statement incorrectly assigns 'secure remote access' to HTTP, which is insecure by default—secure web management would require HTTPS (TCP 443) with TLS encryption, not HTTP.
FTP: Provides secure remote access to network devices using encryption, typically on TCP port 21.
Why it's wrong here
FTP (File Transfer Protocol) is used exclusively for transferring files between clients and servers, using TCP port 21 for control and port 20 for data transfer, and it has no capability for interactive remote shell or device configuration. Crucially, FTP also transmits credentials and data in plaintext, making it entirely unsuitable for secure operations, and secure variants like SFTP (SSH File Transfer Protocol) or FTPS are needed for any encrypted file transfer. Therefore, this option is wrong both functionally—FTP does not provide remote access—and in its claim of encryption, which standard FTP lacks.
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
SSH (Secure Shell) is the correct protocol for secure remote administration because it encrypts both authentication and session data, protecting credentials and commands from interception. It operates over TCP port 22 by default, using cryptographic algorithms like AES and key exchange methods such as Diffie-Hellman. Unlike Telnet or HTTP, SSH provides integrity verification and resistance to eavesdropping, man-in-the-middle, and session hijacking attacks, making it the standard for managing network devices such as routers and switches securely.
Why this is wrong here
Telnet is unencrypted, not secure. The description incorrectly attributes encryption to Telnet.
Why candidates choose this
Candidates may confuse Telnet with SSH because both are used for remote CLI access, but Telnet lacks security.
Why this is wrong here
HTTP uses port 80 and is unencrypted; it is not designed for secure remote access.
Why candidates choose this
Candidates might think HTTP can be used for device management (e.g., web interface) but forget that HTTPS is the secure version.
Why this is wrong here
FTP is for file transfer, not remote CLI access, and lacks encryption.
Why candidates choose this
Candidates may associate FTP with remote access because it requires authentication, but it is not used for device administration.
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?”
Go deeper
Learn chapter
Agentic AI in Network Operations
Key term
TCP
TCP (Transmission Control Protocol) is a core internet protocol that ensures data is sent reliably and in order between devices over a network.
Key term
Secure Shell
Secure Shell (SSH) is a network protocol that provides a secure, encrypted way to access and manage remote computers over an unsecured network.
About these practice questions
One of 1,389 original 200-301 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.