An organization's IT team follows an API-led connectivity approach and must use Anypoint Platform to implement a System API that securely accesses…

The primary objective is to reduce development time for a System API connecting to Salesforce. The Anypoint Connector for Salesforce is specifically designed for this purpose. It abstracts the complexities of Salesforce's underlying APIs (SOAP, REST, Bulk, Streaming) and provides pre-built operations for common tasks like querying, creating, and updating records. This pre-built functionality, along with simplified authentication handling, significantly accelerates development compared to using a generic connector or an indirect data access method. This aligns directly with the principles of API-led connectivity, where System APIs provide a simplified, reusable interface to a system of record.

A. Using FTP involves an indirect, batch-oriented process with data extracts, which adds complexity, introduces data latency, and increases development effort compared to a direct API connection.

C. The generic HTTP connector requires manual configuration of authentication (OAuth), request/response handling, and endpoint URLs, which is significantly more time-consuming than using the purpose-built Salesforce connector.

D. Connecting to a database copy introduces data synchronization challenges and maintenance overhead. The System API should connect directly to the authoritative system of record, which is Salesforce.

1. MuleSoft Documentation, "Salesforce Connector": The documentation states, "Anypoint Connector for Salesforce (Salesforce Connector) provides access to the Salesforce API... The connector exposes methods for accessing Salesforce functionality, which reduces the complexity of interacting with the Salesforce API." This highlights its role in simplifying and accelerating development.

Source: MuleSoft Docs, Salesforce Connector Overview, "About the Salesforce Connector" section.

2. MuleSoft Documentation, "API-led Connectivity": Official documentation on API-led connectivity explains that System APIs are responsible for "exposing backend systems of record (such as SAP, Salesforce, and databases) through a standard and controlled interface (typically RESTful APIs)." Using the dedicated connector is the most efficient way to achieve this.

Source: MuleSoft Docs, "API-led Connectivity", "System APIs" section.

3. MuleSoft Documentation, "HTTP Connector": The HTTP Connector is described as a tool to "send and receive HTTP requests and to handle HTTP responses from a web service." Its generic nature contrasts with the specialized, time-saving features of the Salesforce Connector.

Source: MuleSoft Docs, HTTP Connector Overview, "About the HTTP Connector" section.