11.11 Special 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: save70

Download Latest MuleSoft-Integration-Architect-I Questions

Salesforce Certified MuleSoft Integration Architect 1 (SU24) Exam Questions and Answers

Question 57

An organization is designing Mule application which connects to a legacy backend. It has been reported that backend services are not highly available and experience downtime quite often. As an integration architect which of the below approach you would propose to achieve high reliability goals?

Options:

A.

Alerts can be configured in Mule runtime so that backend team can be communicated when services are down

B.

Until Successful scope can be implemented while calling backend API's

C.

On Error Continue scope to be used to call in case of error again

D.

Create a batch job with all requests being sent to backend using that job as per the availability of backend API's

Question 58

The retrieveBalances flow in the Mule application is designed to use an operation in a connector to the Finance system (the Finance operation) that

can only look up one account record at a time, and a operation from a different connector to the Audit system (the Audit operation) that can only

insert one account record at a time.

To best meet the performance-related requirements, what scope or scopes should be used and how should they be used to incorporate the Finance

operation and Audit operation into the retrieveBalances flow?

Options:

A.

Wrap the Finance operation in a Parallel For-Each scope. Wrap the Audit operation in a Async scope.

B.

Wrap the Finance operation in a Until-Successful scope. Wrap the Audit operation in a Try-Catch scope.

C.

Wrap both connector operations in a Async scope.

D.

Wrap both connector operations in a For-Each scope.

Question 59

What Is a recommended practice when designing an integration Mule 4 application that reads a large XML payload as a stream?

Options:

A.

The payload should be dealt with as a repeatable XML stream, which must only be traversed (iterated-over) once and CANNOT be accessed randomly from DataWeave expressions and scripts

B.

The payload should be dealt with as an XML stream, without converting it to a single Java object (POJO)

C.

The payload size should NOT exceed the maximum available heap memory of the Mute runtime on which the Mule application executes

D.

The payload must be cached using a Cache scope If It Is to be sent to multiple backend systems

Question 60

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?

Options:

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 store

The 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