Free Access to Salesforce.MuleSoft-Integration-Architect-I.v2026-07-22.q100 with Valid Practice Test (Page 10)

Question 41

A company is implementing a new Mule application that supports a set of critical functions driven by a rest API enabled, claims payment rules engine hosted on oracle ERP. As designed the mule application requires many data transformation operations as it performs its batch processing logic.
The company wants to leverage and reuse as many of its existing java-based capabilities (classes, objects, data model etc.) as possible What approach should be considered when implementing required data mappings and transformations between Mule application and Oracle ERP in the new Mule application?

A.Create a new metadata RAML classes in Mule from the appropriate Java objects and then perform transformations via Dataweave
B.From the mule application, transform via theXSLT model
C.Transform by calling any suitable Java class from Dataweave
D.Invoke any of the appropriate Java methods directly, create metadata RAML classes and then perform required transformations via Dataweave

Question 42

Refer to the exhibit.
A Mule application is deployed to a multi-node Mule runtime cluster. The Mule application uses the competing consumer pattern among its cluster replicas to receive JMS messages from a JMS queue. To process each received JMS message, the following steps are performed in a flow:
Step l: The JMS Correlation ID header is read from the received JMS message.
Step 2: The Mule application invokes an idempotent SOAP webservice over HTTPS, passing the JMS Correlation ID as one parameter in the SOAP request.
Step 3: The response from the SOAP webservice also returns the same JMS Correlation ID.
Step 4: The JMS Correlation ID received from the SOAP webservice is validated to be identical to the JMS Correlation ID received in Step 1.
Step 5: The Mule application creates a response JMS message, setting the JMS Correlation ID message header to the validated JMS Correlation ID and publishes that message to a response JMS queue.
Where should the Mule application store the JMS Correlation ID values received in Step 1 and Step 3 so that the validation in Step 4 can be performed, while also making the overall Mule application highly available, fault-tolerant, performant, and maintainable?

A.Both Correlation ID values should be stored in a persistent object store
B.Both Correlation ID values should be stored In a non-persistent object store
C.The Correlation ID value in Step 1 should be stored in a persistent object storeThe Correlation ID value in step 3 should be stored as a Mule event variable/attribute
D.Both Correlation ID values should be stored as Mule event variable/attribute

Question 43

An organization has decided on a cloud migration strategy to minimize the organization's own IT resources.
Currently the organization has all of its new applications running on its own premises and uses an on- premises load balancer that exposes all APIs under the base URL (https://api.rutujar.com).
As part of migration strategy, the organization is planning to migrate all of its new applications and load balancer CloudHub.
What is the most straightforward and cost-effective approach to Mule application deployment and load balancing that preserves the public URL's?

A.Deploy the Mule application to Cloudhub
Create a CNAME record for base URL( httpsr://api.rutujar.com) in the Cloudhub shared load balancer that points to the A record of theon-premises load balancer Apply mapping rules in SLB to map URLto their corresponding Mule applications
B.Deploy the Mule application to Cloudhub
Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the Cloudhub dedicated load balancer Apply mapping rules in DLB to map URLto their corresponding Mule applications
C.Deploy the Mule application to Cloudhub
Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub shared load balancer Apply mapping rules in SLB to map URLto their corresponding Mule applications
D.For each migrated Mule application, deploy an API proxy application to Cloudhub with all traffic to the mule applications routed through a Cloud Hub Dedicated load balancer (DLB) Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub dedicated load balancer Apply mapping rules in DLB to map each API proxy application who is responding new application

Correct Answer: C

For an organization migrating its Mule applications and load balancer to CloudHub while preserving its public URL, the most straightforward and cost-effective approach involves leveraging CloudHub's shared load balancer (SLB). Here's how to do it:
* Deploying Mule Applications to CloudHub:
* First, deploy your Mule applications to CloudHub. This involves packaging your Mule applications and using the Anypoint Platform to deploy them to CloudHub.
* DNS Configuration:
* Update your DNS settings to ensure the base URL (https://api.rutujar.com) points to the CloudHub shared load balancer. Specifically, create or update a CNAME record for api.rutujar.
com to point to the CloudHub SLB's A record.
* Configuring Shared Load Balancer (SLB):
* In CloudHub, configure the SLB to handle incoming traffic and route it to the appropriate Mule applications.
* Apply mapping rules in the SLB to map the base URL and its paths to the corresponding Mule applications. This ensures that requests to https://api.rutujar.com are correctly routed to the specific Mule application endpoints.
* Steps to Apply Mapping Rules:
* In Anypoint Platform, navigate to the Runtime Manager and select the application deployed on CloudHub.
* Configure the SLB settings by defining the domain and URL mappings. For instance, set rules that map requests from https://api.rutujar.com/app1 to the corresponding Mule application app1.
* Benefits of Using SLB:
* Cost-Effective: The shared load balancer is a more economical option compared to a dedicated load balancer (DLB).
* Simplicity: Using SLB simplifies the deployment process, as it requires less configuration and management compared to setting up and maintaining a dedicated load balancer.
* Consistency: Preserves the public-facing URL structure, ensuring a seamless transition for users and clients accessing the APIs.
References:
* MuleSoft Documentation on CloudHub Deployment
* MuleSoft Documentation on Shared Load Balancer
By following these steps, the organization can effectively migrate its applications to CloudHub, ensuring minimal disruption and preserving the existing public URL structure.

Question 44

A Mule application currently writes to two separate SQL Server database instances across the internet using a single XA transaction. It is 58. proposed to split this one transaction into two separate non-XA transactions with no other changes to the Mule application.
What non-functional requirement can be expected to be negatively affected when implementing this change?

A.Throughput
B.Consistency
C.Response time
D.Availability

Question 45

According to MuleSoft, what Action should an IT organization take regarding its technology assets in order to close the IT delivery.

A.Create weekly meetings that all members of IT attend to present justification and request approval to use existing assets
B.Hire additional staff to meet the demand for asset creation required for approved projects and timelines
C.Focus project delivery efforts on custom assets that meet the specific requirements of each individual line of business
D.Make assets easily discoverable via a central repository

Question 41

Question 42

Question 43

Question 44

Question 45

Download PDF File