URI parameter is basically used to identify a specific resource or resources

* Here we want to update details about specific department, so question is asking 'How to use URI

parameter' in RAML

* Correct answer is

/departments:

/{deptId}:

patch:

Reference: https://docs.mulesoft.com/design-center/design-common-problems-raml-10

:

:

MuleSoft Documentation Reference : https://docs.mulesoft.com/db-connector/1.9/databaseconnector-select

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 is Success - 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.

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/MuleSoft_MCD-Level-1/page_42_img_1.jpg

:

For Each Scope

The For Each scope splits a payload into elements and processes them one by one through the

components that you place in the scope. It is similar to a for-each/for loop code block in most

programming languages and can process any collection, including lists and arrays. The collection can

be any supported content type, such as application/json, application/java, or application/xml.

General considerations about the For Each scope:

By default, For Each tries to split the payload. If the payload is a simple Java collection, the For Each

scope can split it without any configuration. The payload inside the For Each scope is each of the split

elements. Attributes within the original message are ignored because they are related to the entire

message.

For Each does not modify the current payload. The output payload is the same as the input.

Mule Doc Reference : https://docs.mulesoft.com/mule-runtime/4.3/for-each-scope-concept

:

:

Correct answer is as below.

After all processing routes have finished execution, the Scatter-Gather component creates a new

Mule event that combines all resulting Mule events from each route, and then passes the new Mule

event to the next component in the flow.

{

"0": {

"attributes": ...,

"payload": "100"

},

"1": {

"attributes": ...,

"payload": "200"

}

}

Bottom of Form