An organization is designing a mule application to support an all or nothing transaction between serval database operations and some other connectors so that they all roll back if there is a problem with any of the connectors Besides the database connector , what other connector can be used in the transaction.

• A.VM
• B.Anypoint MQ
• C.SFTP
• D.ObjectStore

Correct Answer: A

Correct answer is VM VM support Transactional Type. When an exception occur, The transaction rolls back to its original state for reprocessing. This feature is not supported by other connectors.
Here is additional information about Transaction management:

Comment: *

Name: *

Email: *

Verification: *

An organization will deploy Mule applications to Cloudhub, Business requirements mandate that all application logs be stored ONLY in an external splunk consolidated logging service and NOT in Cloudhub.
In order to most easily store Mule application logs ONLY in Splunk, how must Mule application logging be configured in Runtime Manager, and where should the log4j2 splunk appender be defined?

• A.Keep the default logging configuration in Runtime Manager
  Define the Splunk appender in EACH Mule application log4j2.xml file
• B.Disable Cloudhub logging in Runtime Manager
  Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manger to support at Mule application deployments.
• C.Disable Cloudhub logging in Runtime Manager
  Define the splunk appender in EACH Mule application's log4j2.xml file
• D.Keep the default logging configuration in RuntimeManager
  Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manager to support at Mule application deployments.

Comment: *

Name: *

Email: *

Verification: *

An organization uses one specific CloudHub (AWS) region for all CloudHub deployments. How are CloudHub workers assigned to availability zones (AZs) when the organization's Mule applications are deployed to CloudHub in that region?

• A.Workers belonging to a given environment are assigned to the same AZ within that region.
• B.AZs are selected as part of the Mule application's deployment configuration.
• C.Workers are randomly distributed across available AZs within that region.
• D.An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

Anypoint Platform supports role-based access control (RBAC) to features of the platform. An organization has configured an external Identity Provider for identity management with Anypoint Platform.
What aspects of RBAC must ALWAYS be controlled from the Anypoint Platform control plane and CANNOT be controlled via the external Identity Provider?

• A.Controlling the business group within Anypoint Platform to which the user belongs
• B.Assigning Anypoint Platform permissions to a role
• C.Assigning Anypoint Platform role(s) to a user
• D.Removing a user's access to Anypoint Platform when they no longer work for the organization

Comment: *

Name: *

Email: *

Verification: *

In a Mule Application, a flow contains two (2) JMS consume operations that are used to connect to a JMS broker and consume messages from two(2) JMS destination. The Mule application then joins the two JMS messages together.
The JMS broker does not implement high availability (HA) and periodically experiences scheduled outages of upto 10 mins for routine maintenance.
What is the most idiomatic (used for its intented purpose) way to build the mule flow so it can bestrecover from the expected outages?

• A.Consider a transaction for the JMS connector
• B.Configure a reconnection strategy for the JMS connector
• C.Enclose the two(2) JMSoperations in a Try scope with an Error Continue error handler
• D.Enclose the two(2) JMS operation in an Until Successful scope

Comment: *

Name: *

Email: *

Verification: *