Which protocol does REST API rely on to secure the communication channel?

Question

Options

• ATCP
• BHTTPS
• CSSH
• DHTTP

• A
  4% (1)
• B
  93% (25)
• C
  4% (1)

Explanation

REST API Security Protocol

HTTPS (Hypertext Transfer Protocol Secure) is the protocol REST APIs rely on to secure the communication channel, as it combines standard HTTP with TLS/SSL encryption to protect data in transit, ensuring confidentiality, integrity, and authentication between client and server.

Why the distractors are wrong:

• TCP (A) is a lower-level transport layer protocol that handles data transmission reliability but provides no encryption or security features on its own
• SSH (C) is a secure protocol used primarily for remote server access and command-line operations, not for REST API communication
• HTTP (D) is the foundation REST uses, but it transmits data in plain text with no encryption - essentially the unsecured version of HTTPS

Memory Tip: Think of the "S" in HTTPS as standing for "Secure" - whenever you see a REST API endpoint in documentation (e.g., https://api.example.com), that "S" signals the encrypted channel. A simple rule: HTTP = exposed, HTTPS = encrypted. REST APIs handling sensitive data must use HTTPS.

No community discussion yet for this question.