Refer to the exhibits.
Each route in the Scatter-Gather sets the payload to the number shown in the label. What response is returned to a web client request to the HTTP Listener?
A)
B)
C)
D)
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
Which out of below is not an asset?
Exchange is the odd man out here. Rest all are type of asset
In the execution of scatter gather, the "sleep 2 sec" Flow Reference takes about 2 sec to complete, and the "sleep 8 sec" Flow Reference takes about 8 sec to complete.
About how many sec does it take from the Scatter-Gather is called until the "Set Payload" transformer is called?
Correct answer is 8 as events are processed in parallel in case of scatter gather router
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?
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.
A company has defined two RAML fragments, Book Data Type and Book Example to be used in APIs.
What would be valid RAML to use these fragments ?
* RAML file contains lot of information that could be considered as 'not API-describing'. Sort of 'economy-class' members.
Equally important, but not necessarily part of the main RAML file.
* Through !includes, RAML allows us to build file-distributed API definitions, which is not only useful to encourage code reuse but also improves readability.
* We can create RAML fragments with such code and then include them in main RAML project using !include like:
types:
Book: !include bookDataType.raml and
examples:
input: !include bookExample.raml
* Additionally for
----------------------------------------------------------------------------------------------------------------------------------------
Correct Answer: D
Dorothy
1 days agoLera
9 days agoNovella
23 days agoLuisa
1 months agoSanjuana
1 months agoCeola
2 months agoLorita
2 months agoMicaela
3 months agoAileen
4 months agoAlishia
4 months agoDustin
4 months agoJoesph
5 months agoHobert
5 months agoArleen
5 months agoDelisa
6 months agoLashaunda
6 months agoTheron
6 months agoElsa
6 months agoFelicia
6 months agoMargret
7 months agoBerry
7 months agoLarue
7 months agoWai
7 months agoKatlyn
7 months agoWhitley
8 months agoAlline
8 months agoJolene
8 months agoElinore
8 months agoEvette
8 months agoLeatha
8 months agoRene
9 months agoLindsey
9 months agoAnnmarie
9 months agoGayla
9 months agoAron
10 months agoErick
10 months agoYuki
10 months agoJeannetta
10 months agoHeike
10 months agoMollie
11 months agoBenton
12 months agoDelmy
12 months agoBette
1 years agoLang
1 years agoMarget
1 years agoCeola
1 years agoDelisa
1 years agoParis
1 years ago