Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
A manufacturing company is planning to deploy Mule applications to its own Azure Kubernetes Service infrastructure.
The organization wants to make the Mule applications more available and robust by deploying each Mule application to an isolated Mule runtime in a Docker container while managing all the Mule applications from the MuleSoft-hosted control plane.
What is the most idiomatic (used for its intended purpose) choice of runtime plane to meet these organizational requirements?
A Mule application is synchronizing customer data between two different database systems.
What is the main benefit of using XA transaction over local transactions to synchronize these two database system?
* XA transaction add tremendous latency so 'Reduce Latency' is incorrect option XA transactions define 'All or No' commit protocol.
* Each local XA resource manager supports the A.C.I.D properties (Atomicity, Consistency, Isolation, and Durability).
---------------------------------------------------------------------------------------------------------------------
So correct choice is 'Ensure consistency'
Refer to the exhibit.
A business process involves two APIs that interact with each other asynchronously over HTTP. Each API is implemented as a Mule application. API 1 receives the initial HTTP request and invokes API 2 (in a fire and forget fashion) while API 2, upon completion of the processing, calls back into API l to notify about completion of the asynchronous process.
Each API Is deployed to multiple redundant Mule runtimes and a separate load balancer, and is deployed to a separate network zone.
In the network architecture, how must the firewall rules be configured to enable the above Interaction between API 1 and API 2?
* If your API implementation involves putting a load balancer in front of your APIkit application, configure the load balancer to redirect URLs that reference the baseUri of the application directly. If the load balancer does not redirect URLs, any calls that reach the load balancer looking for the application do not reach their destination.
* When you receive incoming traffic through the load balancer, the responses will go out the same way. However, traffic that is originating from your instance will not pass through the load balancer. Instead, it is sent directly from the public IP address of your instance out to the Internet. The ELB is not involved in that scenario.
* The question says ''each API is deployed to multiple redundant Mule runtimes'', that seems to be a hint for self hosted Mule runtime cluster. Set Inbound allowed for the LB, outbound allowed for runtime to request out.
* Hence correct way is to enable communication from each API's Mule Runtimes and Network zone to the load balancer of the other API. Because communication is asynchronous one
Which productivity advantage does Anypoint Platform have to both implement and manage an AP?
Mule application muleA deployed in cloudhub uses Object Store v2 to share data across instances. As a part of new requirement , application muleB which is deployed in same region wants to access this Object Store.
Which of the following option you would suggest which will have minimum latency in this scenario?
V2 Rest API is recommended for on premise applications to access Object Store. It also comes with overhead of encryption and security of using rest api. With Object Store v2, the API call is localized to the same data center as the Runtime Manager app.
But in this case requirement is to access the OS of other mule application and not the same mule application.
You can configure a Mule app to use the Object Store REST API to store and retrieve values from an object store in another Mule app.
However, Object Store v2 is not designed for app-to-app communication.
Refer to the exhibit.
An organization deploys multiple Mule applications to the same customer -hosted Mule runtime. Many of these Mule applications must expose an HTTPS endpoint on the same port using a server-side certificate that rotates often.
What is the most effective way to package the HTTP Listener and package or store the server-side certificate when deploying these Mule applications, so the disruption caused by certificate rotation is minimized?
In this scenario, both A & C will work, but A is better as it does not require repackage to the domain project at all.
Correct answer is Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION.
What is Mule Domain Project?
* A Mule Domain Project is implemented to configure the resources that are shared among different projects. These resources can be used by all the projects associated with this domain. Mule applications can be associated with only one domain, but a domain can be associated with multiple projects. Shared resources allow multiple development teams to work in parallel using the same set of reusable connectors. Defining these connectors as shared resources at the domain level allows the team to: - Expose multiple services within the domain through the same port. - Share the connection to persistent storage. - Share services between apps through a well-defined interface. - Ensure consistency between apps upon any changes because the configuration is only set in one place.
* Use domains Project to share the same host and port among multiple projects. You can declare the http connector within a domain project and associate the domain project with other projects. Doing this also allows to control thread settings, keystore configurations, time outs for all the requests made within multiple applications. You may think that one can also achieve this by duplicating the http connector configuration across all the applications. But, doing this may pose a nightmare if you have to make a change and redeploy all the applications.
* If you use connector configuration in the domain and let all the applications use the new domain instead of a default domain, you will maintain only one copy of the http connector configuration. Any changes will require only the domain to the redeployed instead of all the applications.
You can start using domains in only three steps:
1) Create a Mule Domain project
2) Create the global connector configurations which needs to be shared across the applications inside the Mule Domain project
3) Modify the value of domain in mule-deploy.properties file of the applications
Use a certificate defined in already deployed Mule domain Configure the certificate in the domain so that the API proxy HTTPS Listener references it, and then deploy the secure API proxy to the target Runtime Fabric, or on-premises target. (CloudHub is not supported with this approach because it does not support Mule domains.)
Exam domains verified against: Official Salesforce MuleSoft-Integration-Architect-I exam guide, last checked September 2026.
Differentiate between functional and non-functional requirements and select Anypoint Platform features for designing and managing APIs. This foundation covers the deployment options available across both control plane and runtime plane.
Sample question from this domain above: Q4
Create high-level architectures using API-led connectivity, web APIs, HTTP, and event-driven approaches. Learn to apply common messaging patterns and technologies to design integration solutions.
Work with Mule application properties, core routers, and common connector features including the Salesforce Connector. Master metadata sources in Transform Message and design applications using a Common/Canonical Data Model with proper data validation methods.
Sample question from this domain above: Q5
Design solutions using VM queues, Object Stores, and stateful components configured for all deployment options. Understand when and how to apply persistence patterns across different runtime environments.
Analyze Mule runtime clusters, CloudHub deployment features, and domain-shared configuration. Work with the Mule 4 class loader isolation model and reactive event processing to design appropriate solutions.
Design unit test suites using MUnit and Studio features. Identify when integration testing or performance testing better addresses specific test requirements.
Choose between local transactions, XA transactions, and alternatives like Until Successful scope and reconnection strategies. Distinguish between disaster recovery and high availability approaches.
Sample question from this domain above: Q2
Design solutions using VM queues, Object Stores, and stateful components configured for all deployment options. Understand when and how to apply persistence patterns across different runtime environments.
Design secure Anypoint Platform access, implement Anypoint Security edge access, and identify security vulnerabilities in Mule applications. Understand audit logging capabilities across the platform.
Create CI/CD pipelines using MuleSoft Maven plugins and automate platform interactions. Design logging configurations for all deployment options and use Anypoint Monitoring features.
Common questions about the exam itself
