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?

• A.Increase throughput
• B.Simplifies communincation
• C.Ensure consistency
• D.Reduce latency

Comment: *

Name: *

Email: *

Verification: *

A Mule application is being designed to do the following:
Step 1: Read a SalesOrder message from a JMS queue, where each SalesOrder consists of a header and a list of SalesOrderLineltems.
Step 2: Insert the SalesOrder header and each SalesOrderLineltem into different tables in an RDBMS.
Step 3: Insert the SalesOrder header and the sum of the prices of all its SalesOrderLineltems into a table In a different RDBMS.
No SalesOrder message can be lost and the consistency of all SalesOrder-related information in both RDBMSs must be ensured at all times.
What design choice (including choice of transactions) and order of steps addresses these requirements?

• A.Read the JMS message (NOT in an XA transaction)
  2) Perform EACH DB insert in a SEPARATE DB transaction
  3) Acknowledge the JMS message
• B.Read the JMS message in an XA transaction
  2) In the SAME XA transaction, perform BOTH DB inserts but do NOT acknowledge the JMS message
• C.Read the JMS message (NOT in an XA transaction)
  2) Perform BOTH DB inserts in ONE DB transaction
  3) Acknowledge the JMS message
• D.Read and acknowledge the JMS message (NOT in an XA transaction)
  2) In a NEW XA transaction, perform BOTH DB inserts

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

A Mule application is being designed to be deployed to several CIoudHub workers. The Mule application's integration logic is to replicate changed Accounts from Satesforce to a backend system every 5 minutes.
A watermark will be used to only retrieve those Satesforce Accounts that have been modified since the last time the integration logic ran.
What is the most appropriate way to implement persistence for the watermark in order to support the required data replication integration logic?

• A.Persistent Anypoint MQ Queue
• B.Persistent Cache Scope
• C.Persistent VM Queue
• D.Persistent Object Store

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.
A Mule application is being designed to expose a SOAP web service to its clients.
What language is typically used inside the web service's interface definition to define the data structures that the web service Is expected to exchange with its clients?

• A.WSDL
• B.RAMI
• C.JSON Schema
• D.XSD

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

A Mule application is deployed to a cluster of two customer-hosted Mute runtimes. The Mute application has a flow that polls a database and another flow with an HTTP Listener.
HTTP clients send HTTP requests directly to individual cluster nodes.
What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has railed, but before that node is restarted?

• A.Database polling continues All HTTP requests continue to be accepted, but requests to the failed node Incur increased latency
• B.Database polling continues Only HTTP requests sent to the remaining node continue to be accepted
• C.Database polling stops All HTTP requests continue to be accepted
• D.Database polling stops All HTTP requests are rejected

Comment: *

Name: *

Email: *

Verification: *