Salesforce-MuleSoft-Platform-Architect Practice Test
Salesforce Spring 25 Release 152 Questions
A developer from the Central IT team has created an initial version of the RAML definition in Design Center for an OAuth 2.0-protected System API and published it
to Exchange. Another developer from LoB IT discovered the System API in Exchange and would like to leverage it in the Process API.
What is the MuleSoft-recommended approach for Process API to invoke the System API?
A. The Process API needs to import an CAuth 2.0 module from Exchange first and update it with OAuth 2.0 credentials before the System API can be invoked
B. The Process API uses property YAML files to store the System API URLs and uses the HTTP Request Connector to invoke the Systerm API
C. The Process APL uses the REST Connect Connector autogenerated in Exchange for the System API
D. The Process API manually updates the Process API POM file to include the System API as a dependency
C. The Process APL uses the REST Connect Connector autogenerated in Exchange for the System API
Explanation:
MuleSoft’s REST Connect in Exchange automatically generates a Mule connector from a published RAML or OAS specification, encapsulating all the HTTP operations and OAuth2 security details in a ready-to-use module. Rather than manually managing HTTP Request connectors or editing POM files, developers “Consume an API” by simply dragging the autogenerated connector into their application flow. The REST Connect Connector Generator transparently converts a REST API specification into a Mule connector, supporting OAuth2 client credentials and authorization code flows out of the box. This approach enforces consistent security handling, reduces boilerplate configuration, and accelerates development by leveraging Exchange metadata rather than property files or DIY HTTP calls.