Refer to the exhibits.
In the requestFlow an HTTP Request operation is configured to send an HTTP request with
an XML payload. The request is sent to the HTTP Listener in the transform Flow.
That flow transforms the incoming payload into JSON format and returns the response to
the HTTP request. The response of the request is storedin a target variable named the
Result.
What is the payload at the Logger component after the HTTP Request?
A.
A non-empty Java object
B.
The original XML payload
C.
null
D.
The returned JSON response
The original XML payload
What asset cannot be created using Design Center?
A. Mule Applications
B. API fragments
C. API specifications
D. API portals
Explanation: API portal are created by API Exchange and cannot be created by Design Center
Refer to the exhibits 
What payload and quantity arelogged at the end of the main flow?
A.
[[1,2,3,4], 14]
B.
[[order1, order2, order3, order4], 14]
C.
[[1,2,3,4], 10]
D.
[orderlorder2order3order4,14]
[[1,2,3,4], 14]
Refer to the exhibits.

A. Option A
B. Option B
C. Option C
D. Option D
Refer to the exhibits.
What DataWeave expression transforms the conductorIds array to the XML output?
A. 1. 1. trains:
2. 2. conductorIds map ((engId, index) ->
3. 3. train: {
4. 4. engineerId: engId
5. 5. }
6. 6. )
B. 1. 1. { trains:
2. 2.
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. }
C. 1. 1. trains:
2. 2. {(
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. )}
D. 1. 1. {( trains:
2. 2.
3. 3. conductorIds map ((engId, index) ->
4. 4. train: {
5. 5. engineerId: engId
6. 6. }
7. 7. )
8. 8. )}
Explanation:
Points to remember:
* XML must have a root element.
* XML only allows one root element
* To avoid multiple root issues, you must create a root element for the XML output,
whenever we transform output
* When mapping array elements (JSON or JAVA) to XML, wrap the map operations in {(..)}
-{ } are defining the object
( ) are transforming each element in the array as a key/value pair
* The transformation to XML would fail if the above mentioned considerations were not
taken into account.
* Thus the transformation script declares a root element as trains and wraps the data in “{(
)}“.
Whenever you see such type of question, always look out for root element followed by {( )}
wrapping map.
I call this a "Wrap The Map" scenario. Hope it would help you remember !
Refer to the exhibits.
The<when> expression for the Choice router needs to be written.
What is a valid <when> expression to route Mule events to the non-default flow?
A.
#['MuleSoft' == paytoad.company]
B.
#[ company = "MuleSoft" ]
C.
#[ if( company = "MuleSoft") ]
D.
#[ if('MuleSoff == payload.company) ]
#['MuleSoft' == paytoad.company]
What is the output type of the DataWeave map operator?
A.
String
B.
Array
C.
Map
D.
Object
Array
An API specification is designed using RAML. What is the next step to create a REST
Connector from this API specification?
A.
Download the API specification and build the interface using APIkit
B.
Publish the API specification to Any pointExchange
C.
Implement the API specification using flow designer in Design Center
D.
Add the specification to a Mule project's src/main/resources/api folder
Publish the API specification to Any pointExchange
| Page 1 out of 29 Pages |