Salesforce Certified MuleSoft Platform Architect : Mule-Arch-201

An API has been updated in Anypoint exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the APIs public portal. The API endpoint does NOT change in the new version. How should the developer of an API client respond to this change?

• A. The API producer should be requested to run the old version in parallel with the new one
• B. The API client code only needs to be changed if it needs to take advantage of the new features
• C. The API clients need to update the code on their side and need to do full regression
• D. The API producer should be contacted to understand the change to existing functionality

What best explains the use of auto-discovery in API implementations?

• A. It enables Anypoint Analytics to gain insight into the usage of APIs
• B. It enables Anypoint Exchange to discover assets and makes them available for reuse
• C. It enables Anypoint Studio to discover API definitions configured in Anypoint Platform
• D. It makes API Manager aware of API implementations and hence enables it to enforce policies

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 manually updates the Process API POM file to include the System API as a dependency
• C. The Process API uses property YAML files to store the System API URLs and uses the HTTP Request Connector to invoke the Systerm API
• D. The Process APL uses the REST Connect Connector autogenerated in Exchange for the System API

What is a best practice when building System APIs?

• A. Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs
• B. Document the API using an easily consumable asset like a RAML definition
• C. Expose to API clients all technical details of the API implementation's interaction wifch the backend system
• D. Model all API resources and methods to closely mimic the operations of the backend system

A retail company is using an Order API to accept new orders. The Order API uses a JMS queue to submit orders to a backend order management service. The normal load for orders is being handled using two (2) CloudHub workers, each configured with 0.2 vCore. The CPU load of each CloudHub worker normally runs well below 70%. However, several times during the year the Order API gets four times (4x) the average number of orders. This causes the CloudHub worker CPU load to exceed 90% and the order submission time to exceed 30 seconds. The cause, however, is NOT the backend order management service, which still responds fast enough to meet the response SLA for the Order API. What is the MOST resource-efficient way to configure the Mule application's CloudHub deployment to help the company cope with this performance challenge?

• A. Permanently increase the number of CloudHub workers by four times (4x) to eight (8) CloudHub workers
• B. Use a vertical CloudHub autoscaling policy that triggers on CPU utilization greater than 70%
• C. Use a horizontal CloudHub autoscaling policy that triggers on CPU utilization greater than 70%
• D. Permanently increase the size of each of the two (2) CloudHub workers by at least four times (4x) to one (1) vCore