200-301 · Question #601
Which protocol is used for secure remote CLI access?
The correct answer is D. SSH. SSH (Secure Shell) is the industry-standard protocol for secure remote command-line interface (CLI) access because it encrypts all communication, protecting data integrity and confidentiality.
Question
Options
- AHTTPS
- BHTTP
- CTelnet
- DSSH
How the community answered
(33 responses)- A3% (1)
- B3% (1)
- C6% (2)
- D88% (29)
Why each option
SSH (Secure Shell) is the industry-standard protocol for secure remote command-line interface (CLI) access because it encrypts all communication, protecting data integrity and confidentiality.
HTTPS is used for secure web-based access and management, not typically for direct command-line interface access.
HTTP is an insecure protocol used for web-based access and management; it is not typically used for direct command-line interface access and does not provide encryption.
Telnet is an insecure protocol for command-line interface access as it transmits all data, including usernames and passwords, in plaintext, making it vulnerable to interception.
SSH (Secure Shell) provides robust encryption for both authentication credentials and the entire data exchange during a remote CLI session. This ensures that sensitive information is protected from eavesdropping and tampering, making it the secure choice for managing network devices remotely.
Concept tested: Secure remote CLI access protocols
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/security/d1_v/sec-d1-v-cr-book/sec-ssh-cr.html
Topics
Community Discussion
No community discussion yet for this question.