HTTPS is used for secure web transactions and is not commonly replaced by SSH.
Users often want to log on to a remote computer. Unfortunately, most early implementations to meet that need were designed for a trusted network. Protocols/programs, such as TELNET, RSH, and rlogin, transmit unencrypted over the network, which allows traffic to be easily intercepted. Secure shell (SSH) was designed as an alternative to the above insecure protocols and allows users to securely access
resources on remote computers over an encrypted tunnel. SSH's services include remote
log-on, file transfer, and command execution. It also supports port forwarding, which
redirects other protocols through an encrypted SSH tunnel. Many users protect less secure
traffic of protocols, such as X Windows and VNC (virtual network computing), by forwarding
them through a SSH tunnel. The SSH tunnel protects the integrity of communication,
preventing session hijacking and other man-in-the-middle attacks. Another advantage of
SSH over its predecessors is that it supports strong authentication. There are several
alternatives for SSH clients to authenticate to a SSH server, including passwords and
digital certificates. Keep in mind that authenticating with a password is still a significant
improvement over the other protocols because the password is transmitted encrypted.
The following were wrong answers:
telnet is an incorrect choice. SSH is commonly used as an more secure alternative to
telnet. In fact Telnet should not longer be used today.
rlogin is and incorrect choice. SSH is commonly used as a more secure alternative to
rlogin.
RSH is an incorrect choice. SSH is commonly used as a more secure alternative to RSH.
Reference(s) used for this question:
Hernandez CISSP, Steven (2012-12-21). Official (ISC)2 Guide to the CISSP CBK, Third
Edition ((ISC)2 Press) (Kindle Locations 7077-7088). Auerbach Publications. Kindle
Edition.