A flow has a JMS Publish consume operation followed by a JMS Publish operation. Both of these operations have the default configurations. Which operation is asynchronous and which one is synchronous?

• A.Publish consume: Synchronous. Publish: Asynchronous.
• B.Publish consume: Asynchronous. Publish: Synchronous
• C.Publish consume: Asynchronous. Publish: Asynchronous
• D.Publish consume: Synchronous. Publish: Synchronous

Comment: *

Name: *

Email: *

Verification: *

A Scatter-Gather processes three separate HTTP requests. Each request returns a Mule event with a JSON payload. What is the final output of the Scatter-Gather?

• A.An Array of the three Mule event Objects
• B.An Object containing all three Mule event Objects
• C.An Array of the three JSON payload Objects
• D.An Object containing all three JSON payload Objects

Correct Answer: B

Correct answer is An Object containing all three Mule event Objects
The Scatter-Gather component is a routing event processor that processes a Mule event through different parallel processing routes that contain different event processors. Each route receives a reference to the Mule event and executes a sequence of one or more event processors. Each of these routes uses a separate thread to execute the event processors, and the resulting Mule event can be either the same Mule event without modifications or a new Mule event with its own payload, attributes, and variables. The Scatter-Gather component then combines the Mule events returned by each processing route into a new Mule event that is passed to the next event processor only after every route completes successfully.
The Scatter-Gather component executes each route in parallel, not sequentially. Parallel execution of routes can greatly increase the efficiency of your Mule application and may provide more information than sequential processing.
Sample output is as below

MuleSoft Documentation reference : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibits.


What payload and quantity are logged at the end of the main flow?

• A.[orderlorder2order3order4,14]
• B.[[1,2,3,4], 10]
• C.[[order1, order2, order3, order4], 14]
• D.[[1,2,3,4], 14]

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibits.

This main mule application calls a separate flow called as ShippingAddress which returns the address corresponding to the name of the user sent to it as input. Output of this ShippingAddress is stored in a target variable named address.
Next set of requirement is to have a setPayload transformer which will set below two values
1) orderkey which needs to set to be equal to the order element received in the original request payload.
2) addressKey which needs to be set to be equal to the address received in response of ShippingAddress flow What is the straightforward way to properly configure the Set Payload transformer with the required data?


A mule application is being developed which will process POST requests coming from clients containing the name and order information. Sample request is as below

• A.1. 1. {
  2. 2. orderkey: "payload.order",
  3. 3. addresskey: "vars.address"
  4. 4. }
• B.1. 1. {
  2. 2. orderkey: "attributes.shippingaddress.order",
  3. 3. addresskey: "payload"
  4. }
• C.1. 1. {
  2. 2. orderkey: "payload.order",
  3. 3. addresskey: "address"
  4. }
• D.1. 1. {
  2. 2. orderkey: "attributes.order",
  3. 3. addresskey: "vars.address"
  4. }

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibits.

What is valid text to set the field in the Database connector configuration to the username value specified in the config.yaml file?

• A.${db.username>
• B.#[db.username]
• C.#[db:username]
• D.${db:username>

Comment: *

Name: *

Email: *

Verification: *