MCD - Level 1: MuleSoft Certified Developer - Level 1 (Mule 4)
MuleSoft
This study guide should help you understand what to expect on the exam and includes a summary of the topics the exam might cover and links to additional resources. The information and materials in this document should help you focus your studies as you prepare for the exam.
Related questions
Refer to the exhibit. The main flow contains an HTTP Request in the middle of the flow. The HTTP Listeners and HTTP request use default configurations.
<a target='_blank' href='http://local:801/order?color=red'>What values are accessible to the Logger at the end of the flow after a web client submit request to http://local:801/order?color=red?</a>
Explanation:
In this case as outbound call is made using HTTP: POST /child , all attributes will be replaced by this invocation. Hence query parameter will not be accessible at logger.
As a part of project requirement , you want to build an API for a legacy client. Legacy client can only consume SOAP webservices. Which type the interface documentation can be prepared to meet the requirement?
Explanation:
Web Services Description Language. WSDL is used to describe SOAP based web services
A Mule project contains a DataWeave module like WebStore.dwl that defines a function named loginUser. The module file is located in the project's src/main/resources/libs/etl folder.
What is correct DataWeave code to import all of the WebStore.dwl file's functions and then call the loginUser function for the login '[email protected]'?
A Mule application contains a global error handler configured to catch any errors.
Where must the global error handler be specified so that the global error handler catches all errors from flows without their own error handlers?
Explanation:
Correct answer is A global element
Global error handlers are to be created in global element .
Quick note to remember here is Global error handlers come in to picture only when there are no error handlers specified as flow level.
Steps to create Global error handler
1) Click Global Elements to open Global Configuration Elements. Global Elements is located below the Studio canvas
2) In Global Configuration Elements, click Create to open the Choose Global Type dialog
3) From the dialog, select Global Configuration - Configuration, and then click OK to open the Configuration dialog.
4) From the select Configuration dialog, select allErrorHandler for the Default Error Handler field, and click OK.
Refer to the exhibits.
What payload and quantity are logged at the end of the main flow?
Refer to the exhibits. The webClient flow sends requests to the mockServer Row's HTTP Listener.
An HTTP: METHOD_NOT ALLOWED error is thrown each time the webClient flow executes.
What attribute value must be changed in the webClient flow's HTTP Request operation to prevent this error from being thrown?
Refer to the exhibits.
The my-app xml file contains an Error Handier scope named 'global-error-handler'
The Error Handler scope needs to be set to be the default error handler for every flow in the Mule application
Where and how should the value 'global-error-handler' be added in the Mule project so that the Error Handler scope is the default error handler of the Mule application?
A Scatter-Gather processes three separate HTTP requests. Each request returns a Mule event with a JSON payload. What is the final output of the Scatter-Gather?
Explanation:
Correct answer isAn Object containing all three Mule event Objects
The Scatter-Gather component is a routing event processor that processes a Mule event through different parallel processing routes that contain different event processors. Each route receives a reference to the Mule event and executes a sequence of one or more event processors. Each of these routes uses a separate thread to execute the event processors, and the resulting Mule event can be either the same Mule event without modifications or a new Mule event with its own payload, attributes, and variables. The Scatter-Gather component then combines the Mule events returned by each processing route into a new Mule event that is passed to the next event processor only after every route completes successfully.
The Scatter-Gather component executes each route in parallel, not sequentially. Parallel execution of routes can greatly increase the efficiency of your Mule application and may provide more information than sequential processing.
Sample output is as below
MuleSoft Documentation reference : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept
Refer to the exhibits.
All three of the conditions for the Choice router are true. What messages are written in the application log?
Explanation:
Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggers that route1 execution and the others are not checked. If none of the expressions are true, then the default route executes. Hence only Route1 will be executed as it is the first expression. hence output of logger is Route1.
MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/choice-router-concept
The Choice router dynamically routes messages through a flow according to a set of DataWeave expressions that evaluate message content. Each expression is associated with a different routing option. The effect is to add conditional processing to a flow, similar to an if/then/else code block in most programming languages.
Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggers that route's execution and the others are not checked. If none of the expressions are true, then the default route executes.
Refer to the exhibit.
The API needs to be updated using the company-wide standard for the Plan data type. The Object data type has already been published in Anypoint Exchange with the global reference . ACME/DataTypes/PlanDataType.raml.
What is a valid RAML specification that reuses the Plan data type?
A)
B)
C)
D)
Explanation:
As can be seen in RAML, POST expects input in application/json format which eliminates two of the options as two options are in xml format.
Now out of the two remaining options, one has id field in request which is only mentioned for get response and not for POST request. Hence id field is not expected in POST request.
Hence correct answer is
{
'name': 'GoerdiLa Forge',
'address': '1 Westland CA',
'customer_since': '2014-01-04',
'balance': '4829.29',
'bank_agend_id': '12556'
}
Question