A retailer is designing a data exchange interface to be used by its suppliers. The interface must support secure communication over the public…

The requirements are for secure, cross-platform, and internet-friendly communication. JSON/REST over HTTPS is the modern standard for web APIs, meeting all criteria. It's lightweight, platform-agnostic, and secured by HTTPS. SFTP (SSH File Transfer Protocol) is a widely used, secure method for file-based data exchange over the internet, also supported across various platforms. Both are excellent choices for exchanging data with a diverse group of external suppliers.

B: HOP (Hypertext Object Protocol) is not a widely adopted or standard internet protocol for this type of data exchange, reducing its suitability for a broad supplier base.

C: While functional, using a message broker like ActiveMQ creates a tighter coupling and higher barrier to entry for suppliers compared to standard web APIs or SFTP.

D: FTP (File Transfer Protocol) is inherently insecure as it transmits credentials and data in cleartext, making it unsuitable for communication over the public internet.

1. MuleSoft Documentation, "Secure Sockets Layer (SSL)". This document outlines the use of HTTPS and TLS for securing communications, a core requirement. (Reference: MuleSoft Docs -> Runtime Manager -> Secure Sockets Layer (SSL)).

2. MuleSoft Documentation, "SFTP Connector". This describes the use of SFTP for secure file transfers, which is a standard and secure method for data exchange. (Reference: MuleSoft Docs -> Connectors -> SFTP Connector).

3. MuleSoft Whitepaper, "API-led Connectivity". This paper advocates for using modern, standard-based APIs (like REST/JSON over HTTPS) for building reusable and accessible interfaces. (Reference: "The new IT operating model for enterprise connectivity" section).