200-201 Security Monitoring Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  HTTPS 443

  Why this is correct

  HTTPS uses TLS over TCP port 443 to encrypt web traffic, satisfying the stem's requirement for a secure web protocol and port pair. Plain HTTP on port 80 provides no transport encryption, so 443 is the standard secure alternative.

• ✗

  FTP 21

  Why it's wrong here

  FTP on port 21 carries file transfers in cleartext, providing no transport encryption for web content. It is tempting because FTP does move data between hosts, but it is a file-transfer protocol, not an HTTP-based secure web protocol; HTTPS on 443 is the correct pairing.

• ✗

  HTTP 80

  Why it's wrong here

  HTTP on port 80 transmits web traffic unencrypted, so it fails the 'secure' requirement. It is tempting because HTTP is the web protocol, but confidentiality requires TLS wrapping; HTTPS on port 443 is the correct pairing for secure web traffic.

• ✗

  SSH 22

  Why it's wrong here

  SSH on port 22 secures remote shell sessions and tunnelling, not browser-based web traffic. It is tempting because SSH does encrypt its channel, but it is not an HTTP protocol; HTTPS on port 443 is the pairing that secures web requests between client and server.