Salesforce-MuleSoft-Platform-Architect Practice Test
Salesforce Spring 25 Release 152 Questions
A large organization with an experienced central IT department is getting started using MuleSoft. There is a project to connect a siloed back-end system to a new
Customer Relationship Management (CRM) system. The Center for Enablement is coaching them to use API-led connectivity.
What action would support the creation of an application network using API-led connectivity?
A. Invite the business analyst to create a business process model to specify the canonical data model between the two systems
B. Determine if the new CRM system supports the creation of custom: REST APIs, establishes 4 private network with CloudHub, and supports GAuth 2.0 authentication
C. To expedite this project, central IT should extend the CRM system and back-end systems to connect to one another using built in integration interfaces
D. Create a System API to unlock the data on the back-end system using a REST API
D. Create a System API to unlock the data on the back-end system using a REST API
Explanation:
API-led connectivity advocates exposing core data and functionality behind a System API, abstracting proprietary back-end interfaces into reusable, governed REST services. This layer “unlocks” data from the underlying system, providing a stable contract for higher-level Process and Experience APIs to orchestrate without coupling to silo-specific protocols or schemas. MuleSoft’s API-led connectivity model defines System APIs as the foundational layer that “unlock data from core systems of record”. By first creating a System API for the legacy system, central IT ensures a clean, versioned interface that can be extended by Process APIs for business logic or Experience APIs for UI channels, rather than creating a point-to-point integration that bypasses the API strategy.