An administrator wants to permit SSH management access but block Telnet access to a device. Which statement best reflects that design goal?
Trap 1: Telnet is preferred because it provides stronger confidentiality…
Telnet transmits credentials and session data in cleartext, so it cannot provide confidentiality at all; SSH encrypts the session, which is why the design goal blocks Telnet. The option inverts the actual protocol behaviour. Telnet would only be chosen where encryption is irrelevant, such as an isolated lab segment carrying no sensitive management traffic.
Trap 2: SSH can be used only on Layer 2 switches and not routers
SSH and Telnet are transport protocols available on both routers and switches; the platform type does not determine support. It is tempting because Layer 2 switches commonly run SSH for in-band management, yet the design goal concerns protocol selection, not device role, so this statement misstates the capability.
Trap 3: Blocking Telnet automatically disables all AAA functions
Telnet and AAA are independent features; disabling the Telnet server leaves authentication, authorisation and accounting intact for SSH and console access. It is tempting because both concern management-plane access control, but the design goal is simply to permit SSH while denying Telnet, which AAA configuration does not affect.
- A
SSH is preferred because it provides encrypted remote administration, unlike Telnet
SSH encrypts the entire management session, including credentials and commands, whereas Telnet transmits them in cleartext. Permitting SSH while blocking Telnet therefore meets the design goal of secure remote administration without exposing credentials to interception on the management path.
- B
Telnet is preferred because it provides stronger confidentiality than SSH
Why it fails: Telnet transmits credentials and session data in cleartext, so it cannot provide confidentiality at all; SSH encrypts the session, which is why the design goal blocks Telnet. The option inverts the actual protocol behaviour. Telnet would only be chosen where encryption is irrelevant, such as an isolated lab segment carrying no sensitive management traffic.
- C
SSH can be used only on Layer 2 switches and not routers
Why it fails: SSH and Telnet are transport protocols available on both routers and switches; the platform type does not determine support. It is tempting because Layer 2 switches commonly run SSH for in-band management, yet the design goal concerns protocol selection, not device role, so this statement misstates the capability.
- D
Blocking Telnet automatically disables all AAA functions
Why it fails: Telnet and AAA are independent features; disabling the Telnet server leaves authentication, authorisation and accounting intact for SSH and console access. It is tempting because both concern management-plane access control, but the design goal is simply to permit SSH while denying Telnet, which AAA configuration does not affect.