[Dec 12, 2025] 100% Latest Most updated MuleSoft-Platform-Architect-I Questions and Answers [Q31-Q55]

NEW QUESTION 31
True or False. We should always make sure that the APIs being designed and developed are self-servable even if it needs more man-day effort and resources.

FALSE

TRUE

NEW QUESTION 32
A Platinum customer uses the U.S. control plane and deploys applications to CloudHub in Singapore with a default log configuration.
The compliance officer asks where the logs and monitoring data reside?

Logs are held in:Singapore and monitoring data is held in the United States

Logs and monitoring data are held in the United States

Logs are held in the United States and monitoring data is held in Singapore

Logs and monitoring data are held in Singapore

NEW QUESTION 33
A circuit breaker strategy is planned in order to meet the goal of improved response time and demand on a downstream API.
* Circuit Open: More than 10 errors per minute for three minutes
* Circuit Half-Open: One error per minute
* Circuit Closed: Less than one error per minute for five minutes
Out of several proposals from the engineering team, which option will meet this goal?

Create a custom policy that implements the circuit breaker and includes policy template expressions for the required settings

Create Anypoint Monitoring alerts for Circuit Open/Closed configurations, and then implement a retry strategy for Circuit Half-Open configuration

Add the Circuit Breaker policy to the API instance, and configure the required settings

Implement the strategy in a Mule application, and provide the settings in the YAML configuration

Understanding Circuit Breaker Policy:
A circuit breaker is a design pattern used to detect failures and prevent an application from continually trying to execute a failing operation. In this case, it will help improve response time and reduce demand on the downstream API.
The specified configuration includes conditions for opening, half-opening, and closing the circuit based on error rates over time:
Circuit Open: Triggered if there are more than 10 errors per minute for three consecutive minutes.
Circuit Half-Open: The circuit transitions to half-open if there is one error per minute.
Circuit Closed: The circuit closes if the error rate is less than one error per minute for five minutes.
Evaluating the Options:
Option A: Creating a custom policy with template expressions could work, but it would require custom development. Since the Anypoint Platform already has a Circuit Breaker policy available, this would be a less efficient and more complex solution.
Option B: Anypoint Monitoring alerts can be used for monitoring the API, but they do not provide circuit-breaking functionality. Additionally, implementing a retry strategy for the half-open state is not sufficient to achieve the required circuit breaker behavior.
Option C (Correct Answer): Adding the Circuit Breaker policy to the API instance on Anypoint Platform allows you to set up circuit-breaking conditions directly. This approach uses the built-in Circuit Breaker policy, where you can configure parameters such as error thresholds and time intervals to match the requirements. This solution is efficient, reliable, and leverages Anypoint’s out-of-the-box capabilities.
Option D: Implementing the strategy within a Mule application with a YAML configuration could be complex and less manageable. Additionally, it does not leverage Anypoint Platform’s built-in Circuit Breaker policy, which is more suited to this scenario.
Conclusion:
Option C is the correct choice, as it leverages Anypoint Platform’s Circuit Breaker policy. This solution allows for configuring thresholds and time intervals as specified, improving response time and reducing demand on the downstream API while utilizing Anypoint’s managed policy feature.
Refer to MuleSoft’s documentation on implementing the Circuit Breaker policy in API Manager for detailed configuration guidance.

NEW QUESTION 34
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

NEW QUESTION 35
Refer to the exhibit.

what is true when using customer-hosted Mule runtimes with the MuleSoft-hosted Anypoint Platform control plane (hybrid deployment)?

Anypoint Runtime Manager initiates a network connection to a Mule runtime in order to deploy Mule applications

The MuleSoft-hosted Shared Load Balancer can be used to load balance API invocations to the Mule runtimes

API implementations can run successfully in customer-hosted Mule runtimes, even when they are unable to communicate with the control plane

Anypoint Runtime Manager automatically ensures HA in the control plane by creating a new Mule runtime instance in case of a node failure

NEW QUESTION 36
The implementation of a Process API must change.
What is a valid approach that minimizes the impact of this change on API clients?

Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition

Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version

Implement required changes to the Process API implementation so that whenever possible, the Process API’s RAML definition remains unchanged

Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 – Moved Permanently to inform API clients they should be calling the new API implementation

NEW QUESTION 37
What is a typical result of using a fine-grained rather than a coarse-grained API deployment model to implement a given business process?

A decrease in the number of connections within the application network supporting the business process

A higher number of discoverable API-related assets in the application network

A better response time for the end user as a result of the APIs being smaller in scope and complexity

An overall tower usage of resources because each fine-grained API consumes less resources

NEW QUESTION 38
In which layer of API-led connectivity, does the business logic orchestration reside?

System Layer

Experience Layer

Process Layer

NEW QUESTION 39
The responses to some HTTP requests can be cached depending on the HTTP verb used in the request. According to the HTTP specification, for what HTTP verbs is this safe to do?

PUT, POST, DELETE

GET, HEAD, POST

GET, PUT, OPTIONS

GET, OPTIONS, HEAD

NEW QUESTION 40
A Platform Architect inherits a legacy monolithic SOAP-based web service that performs a number of tasks, including showing all policies belonging to a client. The service connects to two back-end systems – a life-insurance administration system and a general-insurance administration system – and then queries for insurance policy information within each system, aggregates the results, and presents a SOAP-based response to a user interface (UI).
The architect wants to break up the monolithic web service to follow API-led conventions.
Which part of the service should be put into the process layer?

Combining the insurance policy information from the administration systems

Presenting the SOAP-based response to the UI

Authenticating and maintaining connections to each of the back-end administration systems

Querying the data from the administration systems

NEW QUESTION 41
Refer to the exhibit.

What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs?
A) Handle customizations for the end-user application at the Process API level rather than the Experience API level

B) Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs

C) Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs)

D) Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs

Option A

Option B

Option C

Option D

NEW QUESTION 42
Several times a week, an API implementation shows several thousand requests per minute in an Anypoint Monitoring dashboard, Between these bursts, the dashboard shows between two and five requests per minute. The API implementation is running on Anypoint Runtime Fabric with two non-clustered replicas, reserved vCPU 1.0 and vCPU Limit 2.0.
An API consumer has complained about slow response time, and the dashboard shows the 99 percentile is greater than 120 seconds at the time of the complaint. It also shows greater than 90% CPU usage during these time periods.
In manual tests in the QA environment, the API consumer has consistently reproduced the slow response time and high CPU usage, and there were no other API requests at this time. In a brainstorming session, the engineering team has created several proposals to reduce the response time for requests.
Which proposal should be pursued first?

Increase the vCPU resources of the API implementation

Modify the API client to split the problematic request into smaller, less-demanding requests

Increase the number of replicas of the API implementation

Throttle the APT client to reduce the number of requests per minute

NEW QUESTION 43
What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?

When it Is required to make ALL applications highly available across multiple data centers

When it is required that ALL APIs are private and NOT exposed to the public cloud

When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data

When ALL backend systems in the application network are deployed in the organization’s intranet

NEW QUESTION 44
A company requires Mule applications deployed to CloudHub to be isolated between non-production and production environments. This is so Mule applications deployed to non-production environments can only access backend systems running in their customer-hosted non-production environment, and so Mule applications deployed to production environments can only access backend systems running in their customer-hosted production environment. How does MuleSoft recommend modifying Mule applications, configuring environments, or changing infrastructure to support this type of per-environment isolation between Mule applications and backend systems?

Modify properties of Mule applications deployed to the production Anypoint Platform environments to prevent access from non-production Mule applications

Configure firewall rules in the infrastructure inside each customer-hosted environment so that only IP addresses from the corresponding Anypoint Platform environments are allowed to communicate with corresponding backend systems

Create non-production and production environments in different Anypoint Platform business groups

Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments

NEW QUESTION 45
A company is using an on-prem cluster in the data center as a runtime plane and MuleSoft-hosted control plane.
How can the company monitor the detailed performance metrics on the Mule applications deployed to the cluster from the control plane?

The settings of the Monitoring section in the control plane must be updated to enable detailed logging on the metrics to be captured

Monitoring Agent must be installed on each node in the cluster

Due to the potential performance impact on the runtime nodes, the Monitoring agent should be installed on a separate server

There is no action needed as the on-prem runtime automatically sends the performance data to the control plane

NEW QUESTION 46
A company stores financial transaction data in two legacy systems. For each legacy system, a separate, dedicated System API (SAPI) exposes data for that legacy system. A Process API (PAPI) merges the data retrieved from ail of the System APIs into a common format. Several API clients call the PAPI through its public domain name.
The company now wants to expose a subset of financial data to a newly developed mobile application that uses a different Bounded Context Data Model. The company wants to follow MuleSoft’s best practices for building out an effective application network.
Following MuleSoft’s best practices, how can the company expose financial data needed by the mobile application in a way that minimizes the impact on the currently running API clients, API implementations, and support asset reuse?

Add two new Experience APIs (EAPI-i and EAPI-2}.
Add Mobile PAPI-2 to expose the Intended subset of financial data as requested.
Both PAPIs access the Legacy Systems via SAPI-1 and SAP]-2.

Create a new mobile Experince API (EAPI) chat exposes that subset of PAPI endpoints.
Add transformtion login to the mobile Experince API implementation to make mobile data compatible with the required PAPIs.

Develop and deploy is new PAPI implementation with data transformation and … login to support this required endpoints of both mobile and web clients.
Deploy an API Proxy with an endpoint from API Manager that redirect the existing PAPI endpoints to the new PAPI.

To achieve the goal of exposing financial data to a new mobile application while following MuleSoft’s best practices, the company should follow an API-led connectivity approach. This approach ensures minimal disruption to existing clients, maximizes reusability, and respects the separation of concerns across API layers.
of Solution:
Experience APIs for Client-Specific Requirements:
Create two new Experience APIs (EAPI-1 and EAPI-2) for the mobile application, tailored to meet the specific data and format requirements of the mobile application. These APIs encapsulate the client-specific needs and provide a custom interface without impacting other clients.
Process API Layer for Data Transformation:
By adding Mobile PAPI-2, we allow the mobile application to access the required subset of data, formatted according to the mobile application’s requirements. This approach ensures that data transformation and aggregation are handled in the Process layer, maintaining consistency and reusability across different applications.
Reuse of System APIs:
Both the new Mobile PAPI-2 and existing PAPI-1 access data from System APIs (SAPI-1 and SAPI-2), which continue to expose data from each legacy system in a consistent, reusable manner. This avoids duplicating logic and ensures that data access remains centralized and manageable.
Why Option A is Correct:
Option A aligns with MuleSoft’s best practices by isolating client-specific requirements in the Experience layer, utilizing Process APIs for data orchestration and transformation, and maintaining reusable System APIs for backend access.
This approach also ensures that the current API clients are not impacted, as new clients (e.g., the mobile app) interact with newly defined Experience APIs without modifying the existing API setup.
of Incorrect Options:
Option B: This option seems similar but lacks clarity on the separation of mobile-specific requirements and does not explicitly mention data transformation, which is essential in this scenario.
Option C: Creating a single mobile Experience API that exposes a subset of PAPI endpoints directly adds unnecessary complexity and may violate the separation of concerns, as transformation logic should not be in the Experience layer.
Option D: Deploying a new PAPI and using an API Proxy to redirect existing endpoints would add unnecessary complexity, disrupt the current API clients, and increase maintenance efforts.
Reference
For additional guidance, refer to MuleSoft documentation on API-led connectivity best practices and best practices for structuring Experience, Process, and System APIs.

NEW QUESTION 47
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

NEW QUESTION 48
An enterprise is embarking on the API-led digital transformation journey, and the central IT team has started to define System APIs. Currently there is no Enterprise Data Model being defined within the enterprise, and the definition of a clean Bounded Context Data Model requires too much effort.
According to MuleSoft’s recommended guidelines, how should the System API data model be defined?

If there are misspellings of the data fields in the back-end system, Systerm APIs should not correct it, and expose it as-is to mirror the back-end systems

The data model of the System APIs should make use of data types that approximately mirror those from the back-end systems

The data model should define its own naming convention, and not follow the same naming as the back-end systems

The System APIs should expose all back-end system fields

NEW QUESTION 49
A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity.
The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms.
If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API’s desired SLA?

Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries

Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete

No timeout is possible to meet the upstream API’s desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds

NEW QUESTION 50
A customer has an ELA contract with MuleSoft. An API deployed to CloudHub is consistently experiencing performance issues. Based on the root cause analysis, it is determined that autoscaling needs to be applied.
How can this be achieved?

Configure a policy so that when the number of HTTP requests reaches a certain threshold the number of workers/replicas increases (horizontal scaling)

Configure two separate policies: When CPU and memory reach certain threshold, increase the worker/replica type (vertical sealing) and the number of workers/replicas (horizontal sealing)

Configure a policy based on CPU usage so that CloudHub auto-adjusts the number of workers/replicas (horizontal scaling)

Configure a policy so that when the response time reaches a certain threshold the worker/replica type increases (vertical scaling)

NEW QUESTION 51
What API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?

OAuth 2.0 access token enforcement

Client ID enforcement

JSON threat protection

IPwhitellst

NEW QUESTION 52
What is the most performant out-of-the-box solution in Anypoint Platform to track transaction state in an asynchronously executing long-running process implemented as a Mule application deployed to multiple CloudHub workers?

Redis distributed cache

java.util.WeakHashMap

Persistent Object Store

File-based storage

NEW QUESTION 53
An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft).
What best describes each modern API in relation to this new IT operating model?

Each modern API has its own software development lifecycle, which reduces the need for documentation and automation

Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)

Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT D

Each modern API must be REST and HTTP based

NEW QUESTION 54
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

NEW QUESTION 55
When using CloudHub with the Shared Load Balancer, what is managed EXCLUSIVELY by the API implementation (the Mule application) and NOT by Anypoint Platform?

The assignment of each HTTP request to a particular CloudHub worker

The logging configuration that enables log entries to be visible in Runtime Manager

The SSL certificates used by the API implementation to expose HTTPS endpoints

The number of DNS entries allocated to the API implementation

Leave a Reply Cancel reply