An insurance company is implementing a MuleSoft API to get inventory details from the two vendors. Due to network issues, the invocations to vendor applications are getting timed-out intermittently. But the transactions are successful upon reprocessing What is the most performant way of implementing this requirement?

• A.Implement a scatter-gather scope to invoke the two vendorapplications on two different routeUse the Until-Successful scope to implement the retry mechanismfor timeout errors on each route
• B.Implement a Choice scope to invoke the two vendor applications on two different routeUse the try- catch scope to implement the retry mechanism for timeout errors on each route
• C.Implement a For-Each scope to invoke the two vendor applicationsUse until successful scope to implement the retry mechanism for the timeout errors
• D.Implement Round-Robin scope to invoke the two vendor applications on two different routesUse the Try-Catch scope to implement retry mechanism for timeout errors on each route

Comment: *

Name: *

Email: *

Verification: *

What aspects of a CI/CD pipeline for Mule applications can be automated using MuleSoft-provided Maven plugins?

• A.Compile, package, unit test, validate unit test coverage, deploy
• B.Compile, package, unit test, deploy, integration test (Incorrect)
• C.Compile, package, unit test, deploy, create associated API instances in API Manager
• D.Import from API designer, compile, package, unit test, deploy, publish to Anypoint Exchange

Comment: *

Name: *

Email: *

Verification: *

A large life sciences customer plans to use the Mule Tracing module with the Mapped Diagnostic Context (MDC) logging operations to enrich logging in its Mule application and to improve tracking by providing more context in the Mule application logs. The customer also wants to improve throughput and lower the message processing latency in its Mule application flows.
After installing the Mule Tracing module in the Mule application, how should logging be performed in flows in Mule applications, and what should be changed In the log4j2.xml files?

• A.In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.
  In log4j2.xml files, change the appender's pattern layout to use %MDC and then assign the appender to a Logger or Root element.
• B.In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.
  In log4j2.xmI files, change the appender's pattern layout to use the %MDC placeholder and then assign the appender to an AsyncLogger element.
• C.In the flows, wrap Logger components in Async scopes. In log4j2.xmI files, change the appender's pattern layout to use the %asyncLogger placeholder and then assign the appender to a Logger or Root element.
• D.In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.
  In log4j2.xmI files, change the appender''s pattern layout to use %asyncLogger placeholder and then assign the appender to an AsyncLogger element.

Comment: *

Name: *

Email: *

Verification: *

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?

• 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

Comment: *

Name: *

Email: *

Verification: *

A Mule application is synchronizing customer data between two different database systems.
What is the main benefit of using eXtended Architecture (XA) transactions over local transactions to synchronize these two different database systems?

• A.An XA transaction synchronizes the database systems with the least amount of Mule configuration or coding
• B.An XA transaction handles the largest number of requests in the shortest time
• C.An XA transaction automatically rolls back operations against both database systems if any operation falls
• D.An XA transaction writes to both database systems as fast as possible

Comment: *

Name: *

Email: *

Verification: *