Pass the MuleSoft Certified Developer MCD-Level-1 Questions and answers with ValidTests

* 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:

Correct answer is Attributes.

Query parameters , URI parameters and headers are some of examples which are part of attributes.

Diagram Description automatically generated

Bottom of Form

Top of Form

APIKIt Creates a separate flow for each HTTP method. Hence 4 private flows would be generated.

MuleSoft Documentation Referrence : https://docs.mulesoft.com/mule-runtime/4.3/build-application-from-api

This question validates you knowledge on Batch Processing. Before we analyze the question , lets revise a bit about batch filters.

Batch Filters

You can apply one or more filters as attributes to any number of batch steps.Imagine a batch job whose first batch step checks if a Salesforce contact exists for a record, and a second batch step that updates each existing Salesforce contact with new information. You can apply a filter to the second batch step to ensure it only processes records that didn’t fail during the first batch step.By having batch steps accept only some records for processing, you streamline the batch job so the Mule runtime engine can focus only on the relevant data for a particular batch step.

A batch step uses two attributes to filter records:

acceptExpression

acceptPolicy

Each batch step can accept one acceptExpression and one acceptPolicy attributes to filter records.

Use the acceptExpression attribute to process only records that evaluate to true; if the record evaluates to false, the batch step skips the record and sends it to the next one. In other words, the records with an accept expression that resolves to false are the ones that Mule filters out.

The example below filters out all records where the age is less than 21; the batch step does not process those records.

...

Mule Ref Doc : Refining Batch Steps Processing | MuleSoft Documentation

As we are clear with above concepts , now lets understand this solution step by step.

1) Batch Step (Less than 50)

Accept expression for this batch step is less than 50. Hence elements which will go in this batch step are amount value 40 and 2. Hence output of logger in first batch step is

{amount=140}

{amount=102}

2) Batch Step (Greater than 20)

Accept condition for this batch step is greater than 20. Note that input amount values for this batch step are 100 , 140 and 102 (last two values have been updated in batch step less than 50)

As all values satisfy this condition out put of second logger is

{step2amount=100}

{step2amount=140}

{step2amount=102}

Hence correct answer to this question is

{amount=140}

{amount=102}

{step2amount=100}

{step2amount=140}

{step2amount=102}

2) Batch Step (Greater than 20)

Accept condition for this batch step is greater than 20. Note that input amount values for this batch step are 100 , 140 and 102 (last two values have been updated in batch step less than 50)

As all values satisfy this condition out put of second logger is

{step2amount=100}

{step2amount=140}

{step2amount=102}

Hence correct answer to this question is

{amount=140}

{amount=102}

{step2amount=100}

{step2amount=140}

{step2amount=102}

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.

URI parameter is basically used to identify a specific resource or resources

* Here we want to update details about specific department, so question is asking 'How to use URI parameter' in RAML

* Correct answer is

/departments:

/{deptId}:

patch:

As dependency is not present in Mulesoft Maven repository, we need to install the dependency on computer's local Maven repository.

https://docs.mulesoft.com/mule-runtime/4.3/maven-reference

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

Graphical user interface, text, application, chat or text message Description automatically generated

3) From the dialog, select Global Configuration -→ Configuration, and then click OK to open the Configuration dialog.

Graphical user interface, text, application, email Description automatically generated

4) From the select Configuration dialog, select allErrorHandler for the Default Error Handler field, and click OK.