Salesforce Certified MuleSoft Developer (Mule-Dev-201) Exam Practice Test

Answer : C

Scatter-Gather sends the event to each routes concurrently. Hence both route in this example will start in parallel. So total time to complete processing is 40 seconds

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.

Mule Ref Doc :https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

Answer : A

Note that private flow has error scope defined as On Error Continue . So when error occurs in private flow , it is handled by this On Error Continue scope which sends success response back to main flow and does not throw back an error. So main continues normally and payload is set to Success - main flow.

Hence correct answer isSuccess - main flow

1) HTTP listener received request

2) The Flow Reference calls the child flow

3) The Is Number validator creates an Error Object because the payload isn't an integer. Child Flow execution stops

#[error.description] = ''payload is not a valid INTEGER value''

#[error.errorType] = VALIDATION:INVALID_NUMBER

4) The On Error Continue handles the errorThe payload is set to ''Error -- Sub Flow''

5) ''Error -- Sub Flow'' is returned to the main flow as if the child flow was a success. The Set Payload is executed. The payload is reset to ''Success -- Finished Main Flow''

6) ''Success -- Main Flow'' is returned to the requestor in the body of the HTTP request. HTTP Status Code: 200

As you can see, in the above example, because the error was caught by an On Error Continue scope in the child flow (RED in, GREEN out) when the Mule Message returns to the parent flow, the parent flow knows none-the-different that there was a failure because the on error continue returns a 200 success message. Note that because, to the mainFlow, the childFlow appeared to succeed, the processing of mainFlow resumed after the flow reference.

Answer : A

Answer : C

Answer : A

Answer : B

Correct answer is String is not blank.

-------------------------------------------------------------------------------------------------------------------------------------------------

Here's specifically what is happening here:

1) Payload is successfully set to ''Start''

2) The Is Blank String validator creates an Error Object because the payload is string 'Start'. Execution stops

#[error.description] = ''String is not blank''

3) Because no error handler is defined, the Mule default error handler handles the error. Remember, at its heart, the Mule Default Error handler is an error handling scope with just an on error propagate

4) ''String is not blank'' is the error message returned to the requestor in the body of the HTTP requestHTTP Status Code: 500

Reference Diagram:

Answer : C