Refer to the exhibits.
The Mule application does NOT define any global error handlers. The Validation component in the private flow throws an error. What response message is returned to a web client request to the main flow's HTTP Listener?
A. Child error
B. Parent error
C. Validation Error
D. Parent completed
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.
What execution model is used by For Each and Batch Job scopes?
A.
For Each is single-threaded and Batch Job is multi-threaded
B.
Both are single-threaded
C.
Both aremulti-threaded
D.
Batch Job is single-threaded and For Each Is multi-threaded
For Each is single-threaded and Batch Job is multi-threaded
Mule application contains ActiveMQ JMS dependency. Mule application was compiled and run successfully in Anypoint Studio. The mule application must now be exported from Anypoint Studio and shared with other developer. What export options should be selected to create the smallest JAR file that can be imported into other developer's Anypoint Studio and run successfully?
A. Select only Attach Project Sources only
B. Select both Attach Project Sources and Include project modules and dependencies option
C. Select the Include project modules and dependencies option only
D. De-select both Attach Project Sources and Include project modules and dependencies option
Explanation:
Correct answer is Select only Attach Project Sources only.
You must keep the Attach Project Sources option selected to be able to import the
packaged JAR file back into a Studio workspace.
Deselect the Include project modules and dependencies option.
This option skips bundling the actual modules and external dependencies required to run
the Mule application in a Mule runtime engine, creating a lightweight JAR file package that
does not include any dependencies specified in the Mule application’s pom.xml file.
The generated JAR file is not a functional deployable archive and cannot be deployed to a
Mule runtime engine, but instead offers a way to archive only the source files that make up
the Mule application. This is the same as using the -lightWeightPackage flag when
packaging using the Mule Maven Plugin and is useful if you want to distribute your project
to other Studio installations because it only keeps a reference to all its dependencies.
When you import a lightweight package into Studio, all your dependencies are
automatically downloaded.
Refer to the exhibit
A.
Option A
B.
Option B
C.
Option C
D.
Option D
Option B
According to Semantic Versioning, which version would you change for incompatible API changes?
A. No change
B. MINOR
C. MAJOR
D. PATCH
Explanation:
Correct answer is MAJOR
MAJOR version when you make incompatible API changes, MINOR version when you add
functionality in a backwards compatible manner, and PATCH version when you make
backwards compatible bug fixes.
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 exhibit.
The Mule application's connectors are configured with property placeholders whose values
are set in the config.yaml file.
What must be added to the Mule application to link the config.yaml file's values with the
property placeholders?
A. A configuration-properties element in the acme-app xml file
B. A dependency element in the pom xml file
C. A file-config element in the acrne-app xml file
D. A propertiesFile key/value pair in the mule-artifact json file
| Page 1 out of 29 Pages |
Contact Us - Privacy Policy ... Copyright © - All Rights Reserved