Which statement about HTTP and HTTPS is true?

• A. HTTP transfers data in plaintext; HTTPS encrypts data in transit using TLS/SSL.
• B. HTTP uses UDP; HTTPS uses TCP.
• C. HTTP and HTTPS are the same protocol with no encryption difference.
• D. HTTPS uses the same port as HTTP and adds no encryption.

Answer: (A)

The key idea here is how encryption changes the safety of the data you send over the web. HTTP sends requests and responses in plain text, so anyone who can intercept the traffic can read the content. HTTPS layers TLS/SSL on top of HTTP to encrypt that data in transit, plus it provides server authentication and integrity checks. This means sensitive information like passwords or personal data is protected from eavesdroppers, tampering, and impersonation.

TLS/SSL works through a handshake that establishes a secure session and generates keys used to encrypt the communication. The server presents a certificate to prove its identity, helping you trust you’re talking to the real site. Because of this encryption, you’ll typically see HTTPS using a different default port (443) than HTTP (80), though configuration can vary.

Why the other statements don’t fit: HTTP uses TCP, not UDP, and so does HTTPS; the claim that they’re the same protocol with no encryption difference ignores the fundamental security difference. The claim that HTTPS uses the same port as HTTP and adds no encryption ignores both the common port distinction and the essential encryption provided by TLS/SSL.