Refer to the exhibits. 
A web client sends a POST request with thepayload {"oid": "1000", "itemid": "AC200", "qty":
"4" } to the Mule application. The File Write operation throws a FILE:CONNECTIVITY error.
What response message is returned to the web client?
A.
‘’FILE:CONNECnvnY'
B.
"ORDER:NOT_CREATED"
C.
"OTHER ERROR"
D.
"File written"
‘’FILE:CONNECnvnY'
Refer to the exhibits.
What payload and quantity are logged 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]
Refer to the exhibit.
How many private flows does APIKIT generate from the RAML specification?
A. 1
B. 2
C. 3
D. 4
Refer to the exhibit.
What is the correct syntax to add an employee ID as aURI parameter in an HTTP Listener
path?
A.
(employeelD)
B.
${emp!oyeelD}
C.
{employeelD}
D.
# [employeelD]
{employeelD}
According to Mulesoft, how are Modern APIs treated as?
A. Products
B. SOAP API's
C. Rest API's
D. Code
Explanation:
Correct answer is Products
Modern API has three features 1) Treated as products for easy consumption 2)
Discoverable and accessible through self-service 3) Easily managed for security ,
scalability and performance.
Refer to the exhibits.
The Validation component in the private flow throws an error. What response message is
returned to a client request to the main flow's HTTP Listener?
A.
Error - private flow
B.
Error - main flow
C.
Success - main flow
D.
Validation Error
Success - main flow
What is the difference between a subflow and a sync flow?
A. No difference
B. Subflow has no error handling of its own and sync flow does
C. Sync flow has no error handling of its own and subflow does
D. Subflow is synchronous and sync flow is asynchronous
Explanation:
Correct answer is Subflow has no error handling implementation where as sync flow has Subflow:
A subflow processes messages synchronously (relative to the flow that triggered its
execution) and always inherits both the processing strategy and exception strategy
employed by the triggering flow. While a subflow is running, processing on the triggering
flow pauses, then resumes only after the subflow completes its processing and hands the
message back to the triggering flow.
Synchronous Flow:
A synchronous flow, like a subflow, processes messages synchronously (relative to the
flow that triggered its execution). While a synchronous flow is running, processing on the
triggering flow pauses, then resumes only after the synchronous flow completes its
processing and hands the message back to the triggering flow. However, unlike a subflow,
this type of flow does not inherit processing or exception strategies from the triggering flow.
This type of flow processes messages along a single thread, which is ideally suited to
transactional processing.
There are three routes configured for Scatter-Gather and incoming event has a payload is an Array of three objects. How routing will take place in this scenario?
A. Incoming array objects would be split into three and each part would be sent to one route each in sequential manner
B. Incoming array objects would be split into three and each part would be sent to one route each in parallel
C. Entire event would be sent to each route sequentially
D. Entire event would be sent to each route in parallel
Explanation:
Entire event would be sent to each route in parallel.
Scatter-Gather works as follows :
- The Scatter-Gather component receives a Mule event and sends a reference of this Mule
event to each processing route.
- Each of the processing routes starts executing in parallel. After all processors inside a
route finish processing, the route returns a Mule event, which can be either the same Mule
event without modifications or a new Mule event created by the processors in the route as
a result of the modifications applied.
- 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.
| Page 1 out of 29 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved