MuleSoft Certified Platform Architect - Level 1 Exam (MCPA) - MuleSoft Actual Exam Questions
Last updated on May 01, 2026
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?
The API producer should be requested to run the old version in parallel with the new one
The API producer should be contacted to understand the change to existing functionality
The API client code only needs to be changed if it needs to take advantage of the new features
The API clients need to update the code on their side and need to do full regression
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon. This is the only downstream API dependency of that upstream API. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?
An SLA for the upstream API CANNOT be provided
The invocation of the downstream API will run to completion without timing out
A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
Refer to the exhibit. A developer is building a client application to invoke an API deployed to the STAGING environment that is governed by a client ID enforcement policy. What is required to successfully invoke the API?
The client ID and secret for the Anypoint Platform account owning the API in the STAGING environment
The client ID and secret for the Anypoint Platform account's STAGING environment
The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment
A valid OAuth token obtained from Anypoint Platform and its associated client ID and secret
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
Say, there is a legacy CRM system called CRM-Z which is offering below functions: 1. Customer creation 2. Amend details of an existing customer 3. Retrieve details of a customer 4. Suspend a customer
Implement a system API named customerManagement which has all the functionalities wrapped in it as various operations/resources
Implement different system APIs named createCustomer, amendCustomer, retrieveCustomer and suspendCustomer as they are modular and has seperation of concerns
Implement different system APIs named createCustomerInCRMZ, amendCustomerInCRMZ, retrieveCustomerFromCRMZ and suspendCustomerInCRMZ as they are modular and has seperation of concerns
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
Select the correct Owner-Layer combinations from below options
1. App Developers owns and focuses on Experience Layer APIs 2. Central IT owns and focuses on Process Layer APIs 3. LOB IT owns and focuses on System Layer APIs
1. Central IT owns and focuses on Experience Layer APIs 2. LOB IT owns and focuses on Process Layer APIs 3. App Developers owns and focuses on System Layer APIs
1. App Developers owns and focuses on Experience Layer APIs 2. LOB IT owns and focuses on Process Layer APIs 3. Central IT owns and focuses on System Layer APIs
to join the discussion
No discussions yet. Be the first to ask!
Delete Comment
Are you sure? This action cannot be undone.
Finish Practice?
Are you sure you want to finish? This will end your practice session.