An XA transaction Is being configured that involves a JMS connector listening for Incoming JMS messages. What is the meaning of the timeout attribute of the XA transaction, and what happens after the timeout expires?

• A.The time that is allowed to pass between committing the transaction and the completion of the Mule flow After the timeout, flow processing triggers an error
• B.The time that Is allowed to pass between receiving JMS messages on the same JMS connection After the timeout, a new JMS connection Is established
• C.The time that Is allowed to pass without the transaction being ended explicitly After the timeout, the transaction Is forcefully rolled-back
• D.The time that Is allowed to pass for state JMS consumer threads to be destroyed After the timeout, a new JMS consumer thread is created

Correct Answer: C

* Setting a transaction timeout for the Bitronix transaction manager
Set the transaction timeout either
- In wrapper.conf
- In CloudHub in the Properties tab of the Mule application deployment
* The default is 60 secs. It is defined as
mule.bitronix.transactiontimeout = 120
* This property defines the timeout for each transaction created for this manager.
If the transaction has not terminated before the timeout expires it will be automatically rolled back.
--------------------------------------------------------------------------------------------------------------------- Additional Info around Transaction Management:
Bitronix is available as the XA transaction manager for Mule applications
* To use Bitronix, declare it as a global configuration element in the Mule application
<bti:transaction-manager />
* Each Mule runtime can have only one instance of a Bitronix transaction manager, which is shared by all Mule applications
* For customer-hosted deployments, define the XA transaction manager in a Mule domain
- Then share this global element among all Mule applications in the Mule runtime

Comment: *

Name: *

Email: *

Verification: *

A company is planning to migrate its deployment environment from on-premises cluster to a Runtime Fabric (RTF) cluster. It also has a requirement to enable Mule applications deployed to a Mule runtime instance to store and share data across application replicas and restarts.
How can these requirements be met?

• A.Install the object store pod on one of the cluster nodes
• B.Configure Persistent Gateway at the RTF
• C.Configure Persistence Gateway in any of the servers using Mule Object Store
• D.Anypoint object store V2 to share data between replicas in the RTF cluster

Comment: *

Name: *

Email: *

Verification: *

A Mule application is running on a customer-hosted Mule runtime in an organization's network. The Mule application acts as a producer of asynchronous Mule events. Each Mule event must be broadcast to all interested external consumers outside the Mule application. The Mule events should be published in a way that is guaranteed in normal situations and also minimizes duplicate delivery in less frequent failure scenarios.
The organizational firewall is configured to only allow outbound traffic on ports 80 and 443. Some external event consumers are within the organizational network, while others are located outside the firewall.
What Anypoint Platform service is most idiomatic (used for its intended purpose) for publishing these Mule events to all external consumers while addressing the desired reliability goals?

• A.CloudHub VM queues
• B.Anypoint MQ
• C.Anypoint Exchange
• D.CloudHub Shared Load Balancer

Comment: *

Name: *

Email: *

Verification: *

An integration Mute application consumes and processes a list of rows from a CSV file. Each row must be read from the CSV file, validated, and the row data sent to a JMS queue, in the exact order as in the CSV file.
If any processing step for a row falls, then a log entry must be written for that row, but processing of other rows must not be affected.
What combination of Mute components is most idiomatic (used according to their intended purpose) when Implementing the above requirements?

• A.Scatter-Gather component On Error Continue scope
• B.VM connector first Successful scope On Error Propagate scope
• C.For Each scope On Error Continue scope
• D.Async scope On Error Propagate scope

Correct Answer: C

* On Error Propagate halts execution and sends error to the client. In this scenario it's mentioned that "processing of other rows must not be affected" so Option B and C are ruled out.
* Scatter gather is used to club multiple responses together before processing. In this scenario, we need sequential processing. So option A is out of choice.
* Correct answer is For Each scope & On Error Continue scope Below requirement can be fulfilled in the below way
1) Using For Each scope , which will send each row from csv file sequentially. each row needs to be sent sequentially as requirement is to send the message in exactly the same way as it is mentioned in the csv file
2) Also other part of requirement is if any processing step for a row fails then it should log an error but should not affect other record processing . This can be achieved using On error Continue scope on these set of activities. so that error will not halt the processing. Also logger needs to be added in error handling section so that it can be logged.
* Attaching diagram for reference. Here it's try scope, but similar would be the case with For Each loop.

Comment: *

Name: *

Email: *

Verification: *

Customer has deployed mule applications to different customer hosted mule run times. Mule applications are managed from Anypoint platform.
What needs to be configured to monitor these Mule applications from Anypoint monitoring and what sends monitoring data to Anypoint monitoring?

• A.By default, Anypoint monitoring agent will be installed on each Mule run time Anypoint Monitoring agent automatically sends monitoring data from the Mule applications to Anypoint monitoring
• B.Anypoint monitoring agent on each mule runtime
  Anypoint monitoring agent sends monitoring data from the mule applications to Anypoint monitoring
• C.Install runtime manager agent on each mule runtime
  Runtime manager agent since monitoring data from the mule applications to Anypoint monitoring
• D.Enable monitoring of individual applications from runtime manager application settings Runtime manager agent sends monitoring data from the mule applications to Anypoint monitoring

Comment: *

Name: *

Email: *

Verification: *