QUESTION: 109

A Mule application contains a Batch Job scope with several Batch Step scopes. The Batch Job scope is configured with a batch block size of 25.

A payload with 4,000 records is received by the Batch Job scope.

When there are no errors, how does the Batch Job scope process records within and between the Batch Step scopes?

The Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed in parallel All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope
The Batch Job scope processes each record block sequentially, one at a time Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed sequentially, one at a time
All 4000 records must be completed before the blocks of records are available to the next Batch Step scope
The Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed sequentially, one record at a time
All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope
The Batch Job scope processes multiple record blocks in parallel Each Batch Step scope is invoked with a batch of 25 records in the payload of the received Mule event
For each Batch Step scope, all 4000 records are processed in parallel Individual records can jump ahead to the next Batch Step scope before the rest of the records finish processing in the current Batch Step scope

Answer(s): A

Reference:

https://docs.mulesoft.com/mule-runtime/4.4/batch-processing-concept

Reveal Solution Next Question

QUESTION: 110

To implement predictive maintenance on its machinery equipment, ACME Tractors has installed thousands of IoT sensors that will send data for each machinery asset as sequences of JMS messages, in near real-time, to a JMS queue named SENSOR_DATA on a JMS server. The Mule application contains a JMS Listener operation configured to receive incoming messages from the JMS servers SENSOR_DATA JMS queue. The Mule application persists each received JMS message, then sends a transformed version of the corresponding Mule event to the machinery equipment back-end systems.

The Mule application will be deployed to a multi-node, customer-hosted Mule runtime cluster. Under normal conditions, each JMS message should be processed exactly once.

How should the JMS Listener be configured to maximize performance and concurrent message processing of the JMS queue?

Set numberOfConsumers = 1
Set primaryNodeOnly = false
Set numberOfConsumers = 1
Set primaryNodeOnly = true
Set numberOfConsumers to a value greater than one
Set primaryNodeOnly = true
Set numberOfConsumers to a value greater than one
Set primaryNodeOnly = false

Answer(s): D

Reference:

https://docs.mulesoft.com/jms-connector/1.8/jms-performance

Reveal Solution Next Question

QUESTION: 111

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?

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

Answer(s): B

Reference:

https://docs.oracle.com/middleware/1213/wls/PERFM/llrtune.htm#PERFM997

Reveal Solution Next Question

QUESTION: 112

An organization has implemented a continuous integration (CI) lifecycle that promotes Mule applications through code, build, and test stages. To standardize the organization's CI journey, a new dependency control approach is being designed to store artifacts that include information such as dependencies, versioning, and build promotions.

To implement these process improvements, the organization will now require developers to maintain all dependencies related to Mule application code in a shared location.

What is the most idiomatic (used for its intended purpose) type of system the organization should use in a shared location to standardize all dependencies related to Mule application code?

A MuleSoft-managed repository at repository.mulesoft.org
A binary artifact repository
API Community Manager
The Anypoint Object Store service at cloudhub.io

Answer(s): C

Reveal Solution Next Question

Free MuleSoft-Integration-Architect-I Exam Braindumps (page: 28)

QUESTION: 109

Reference:

QUESTION: 110

Reference:

QUESTION: 111

Reference:

QUESTION: 112