Free MCD-LEVEL1 Exam Dumps Preview

Correct answer is Anypoint Visualizer MuleSoft Doc Ref :
https://docs.mulesoft.com/visualizer/
Anypoint Visualizer provides a real-time, graphical representation of the APIs, and Mule applications that are running and discoverable. It also displays third-party systems that are invoked by a Mule API, proxy, or application within your application network. The data displayed in the graph is dynamically updated and does not require prior configuration. Additionally, the data displayed is secure, as only users with the proper permissions can view the application network graph.

The First Successful router iterates through a list of configured processing routes until one of the routes executes successfully. This is sequential execution. In all other options mentioned in the question ,we can achieve parallel execution.

Transform Message Add write_date is coverting payload in JSON format and same JSON payload is avaialble to file write processor. However, if the payload is a different format (for example, not CSV) , you can place the transformation inside the Write operation to generate content that will be written without producing a side effect on the message in transit. This is not done in this case. By default, the connector writes whatever is in the message payload. Hence JSON payload will be written to file.

Root element is always required while creating XML response in DataWeave transformation

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 is Success - 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.

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

* To use custom modules, you need to import the module or functions you want to use by adding the import directive to the head of your DataWeave script, for example:
1) Does not identify any functions to import from the String module:
import dw::core::Strings
2) To identify a specific function to import from the String module:
import camelize, capitalize from dw::core::Strings 3) To import all functions from the String module:
import * from dw::core::Strings

The way you import a module impacts the way you need to call its functions from a DataWeave script. If the directive does not list specific functions to import or use * from to import all functions from a function module, you need to specify the module when you call the function from your script.
* In given scenario, it's mentioned to import all of the WebStore.dwl So correct answer is:
References:
https://docs.mulesoft.com/mule-runtime/4.3/dw-functions

Mule applications can be scaled vertically by changing worker size. Mule applications can be scaled horizontally by adding more workers.

Exchange is the odd man out here. Rest all are type of asset

Correct answer is as below. On complete phase only has access to batch job result statistics and payload is not available.
Total Records Processed: 3
Successful Records: 3
Failed Records: 0

Mule Ref Doc :
https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept#on-complete

API Exchange creates REST conenctor automtaically once API is published. Hence correct answer is Publish the API specification to Any point Exchange

In case of an error , batch job completes in flight steps and stops further processing. MuleSoft Doc Ref : Handling Errors During Batch Job | MuleSoft Documentation The default is all processing will stop but we can change it by Max Failed Record field. General -> Max Failed Records: Mule has three options for
handling a record-level error: Finish processing, Continue processing and Continue processing until the batch job accumulates a maximum number of failed records. This behavior can be controlled by Max Failed Records.
The default value is Zero which corresponds to Finish processing.
The value -1, corresponds to Continue processing.
The value +ve integer, corresponds to Continue processing until the batch job accumulates a maximum number of failed records

WSDL is used to define the contract in case of SOAP . RAML/OAS is used to REST services

Empty array is returned when no rows are matched.
MuleSoft Doc Ref :
https://docs.mulesoft.com/db-connector/1.9/database-connector-select

Debugger can be used to debug applications to see event data movine from one flow to other

In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues.

Database always return rows as an array.
Array is the correct answer

The HTTP 415 Unsupported Media Type client error response code indicates that the server refuses to accept the request because the payload format is in an unsupported format. The format problem might be due to the request's indicated Content-Type or Content-Encoding , or as a result of inspecting the data directly. In this case as per RAML specification data is expected in application/json and in request Content-
Type is set as "text/plain" which is incorrect. Hence solution is set the request Content-Type header to application/json

Correct answer is [[5, 10, 15, 20], 5]
Key thing to note here is that any changes made to payload in for each loop are not available outside for each scope where as variable value updated in for each loop is visible out side for each loop too.

API portal are created by API Exchange and cannot be created by Design Center

Correct answer is Patients from year 2021.
The thing to note here is that year is not a query parameter and not the uri parameter. Hence it will filter all the patients and return the ones for whom year is 2021

The List operation returns an array of messages in which: Each message holds the file's content in its payload. The file's attributes section carries the file's metadata (such as name, creation time, and size).
The payload is empty if the element is a folder.

To include property. To keep the API definition concise, you can include external content, such as documentation, schemas, and frequently used patterns outside the definition itself. The parser interprets
!include as if the content of the externally-hosted file or a URL were declared in-line.
To use the fragments in RAML you have to include the exact path(copy the path) of that fragment you want to use as shown below Option 3 is the correct as correct syntax is examples: !include examples/StudentExample.raml
References:
https://docs.mulesoft.com/api-manager/1.x/tutorial-design-an-api

Core (dw::Core) This module contains core DataWeave functions for data transformations.
It is automatically imported into any DataWeave script.