Refer to the exhibits.


The Validation component in the Try scope throws an error.
What response message is returned to a client request to the main flow's HTTP Listener?
The Validation component in the Try scope throws an error. What response message is returned to a client request to the main flow's HTTP Listener?

• A.Success - main flow
• B.Error - main flow
• C.Error - Try scope
• D.Validation Error

Correct 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 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.

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibits. What payload is logged at the end of the main flow?

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

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibits. The Set Payload transformer in the addltem child flow uses DataWeave to create an order object.
What is the correct DataWeave code for the Set Payload transformer in the createOrder flow to use the addltem child flow to add a router call with the price of 100 to the order?

• A.lookup( "addltern", { price: "100", item: "router", itemType: "cable" } )
• B.addltem( { price: "100", item: "router", itemType: "cable" } )
• C.lookup( "addltem", { payload: { price: "100", item: "router", itemType: "cable" } > )
• D.addltem( { payload: { price: "100", item: "router", itemType: "cable" > } )

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

A Mule event is composed of a hierarchy of objects. Where in the hierarchy are variables stored?

• A.Mule event
• B.Mule message payload
• C.Mule message
• D.Mule message attributes

Correct Answer: A

Variables are stored under Mule event. Please refer to below image for the hierarchy .

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

What is the correct DataWeave expression for the Set Payload transformer to call the createCustomerObject flow with values for the first and last names of a new customer?

• A.createCustomerObject( { first: "Alice", last: "Green" > )
• B.createCustomerObject( "Alice", "Green")
• C.lookupC createCustomerObJect( "Alice", "Green- ) )
• D.lookupf "createCustomerObject", { first: "Alice", last: "Green" > )

Comment: *

Name: *

Email: *

Verification: *