Why is SSH preferred over Telnet as a method of accessing a network device to alter or view the configuration?

Question

Options

• ATelnet encrypts only the login information, not the entire transmission.
• BSSH requires fewer network resources and no additional configuration.
• CTelnet is more difficult to use and configure than SSH.
• DSSH encrypts the login and session information.

• A
  9% (5)
• B
  4% (2)
• C
  2% (1)
• D
  86% (49)

Explanation

SSH encrypts all communication between the client and the network device - including the login credentials, commands, and all session data - making it secure against eavesdropping and man-in-the-middle attacks. Telnet transmits everything, including passwords, in plaintext, which means anyone on the network can capture the entire session with a packet sniffer.

Why the distractors are wrong:

• A is backwards - it's actually Telnet that encrypts nothing, not just some portions. SSH encrypts everything; Telnet encrypts nothing.
• B is false - SSH actually requires more resources (CPU for encryption) and additional configuration (key generation, enabling SSH on the device) compared to Telnet.
• C is false - if anything, Telnet is simpler and easier to use; SSH is slightly more complex to set up, which is a tradeoff worth making for security.

Memory tip: Think "SSH = Secure Session" - both the login and everything after it are protected. Telnet is like sending a postcard (anyone can read it); SSH is like a sealed, locked envelope.

No community discussion yet for this question.