MuleSoft MCD-Level-1 MuleSoft Certified Developer - Level 1 (Mule 4) Exam Practice Test

Correct answer is 200.1234 as String {format: ".0#"} . Rest all options are not syntactically correct.

Correct answer is Not needed as dw::core module is included by default. We don't need to include it explicitly

For such questions always look for Syntax:

I call it "Wrap the Map"

trains:

{(

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

Correct answer is System layer

System APIs provide a means for insulating the data consumers from the complexity or changes to the underlying backend systems.

MuleSoft recommends three-layered approach to API-led connectivity, highlighting the three layers:

* System APIs

* Process APIs

* Experience APIs

System APIs are the core systems of record underlying core systems of record (e.g. ERPs, key customer and billing systems, databases, etc.). Process APIs allow you to define a common process which the organization can share, and these APIs perform specific functions, provide access to non-central data, and may be built by either Central IT or Line of Business IT. And finally, the Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source.

The three-layered structure allows for a seamless flow of data from systems of record to new experiences, and allows for reusability of assets rather than point to point connections. This approach provides a distributed and tailored approach to architecture, greater flexibility through loose coupling, and deeper operational visibility into what is being built.

Diagram Description automatically generated

1. Set Payload “Start”

2. 'Is Balnk String' Creates an Error object with #[error.description] =“String is not blank”

3. Default Error Handler catches and Propagates error

4. 'On Error Propogate' is 'RED IN RED OUT'. It Returns Status Code : 500 & #[error.description]

--------------------------------------------------------------------------------------------------------------------------

Correct answer is String is not blank. Because validation component will throw an error as payload is not blank.

A picture containing timeline Description automatically generated

Bottom of Form

Top of Form

Correct answer is as below as concatenation operation works only with string and not with the objects. In this case payload is object.

"You called the function '++' with these arguments:

1: String ("INFO")

2: Object ({student: {name: "Anay" as String {class: "java.lang.String"},age

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

You can choose Attach Project Sources to include metadata that Studio requires to reimport the deployable file as an open Mule project into your workspace. You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace. But requirement here is to create smallest deployable archive that will successfully deploy to Cloudhub. Hence we can ignore this option.

We need to select Include project module and dependencies

As actual modules and external dependencies required to run the Mule application in a Mule runtime engine

Hence correct answer is

Select only below option 2) Include project module and dependencies

MuleSoft Doc Ref : https://docs.mulesoft.com/studio/7.5/import-export-packages#exporting-a-studio-project-to-a-deployable-mule-application

Option 3 is the only corect answer as it concatenates payload with String.

Below option wont work.

#["The payload is " ++ payload]

Concatenation function expects both arguments to be string. As the question says payload is json object , this will throw error while running it. You can try this in Anypoint Studio and you will get the same result which I mentioned.

hence correct answer is

The payload is: #[payload]

To compare, DataWeave syntax is #[payload == "FR"].

In this case only one = is used so it will give syntax error.

Hence the correct answer is A dataweave syntax error

Web Services Description Language. WSDL is used to describe SOAP based web services

Correct answer is Array.

Flatten turns a set of subarrays (such as [ [1,2,3], [4,5,[6]], [], [null] ]) into a single, flattened array (such as [ 1, 2, 3, 4, 5, [6], null ]).

This example defines three arrays of numbers, creates another array containing those three arrays, and then uses the flatten function to convert the array of arrays into a single array with all values.

Source

%dw 2.0

output application/json

var array1 = [1,2,3]

var array2 = [4,5,6]

var array3 = [7,8,9]

var arrayOfArrays = [array1, array2, array3]

---

flatten(arrayOfArrays)

Output

[ 1,2,3,4,5,6,7,8,9 ]

Correct answer is Publish the API to Anypoint Exchange

Anypoint Exchange makes this possible by making it discoverable in below ways

1) In private exchange for internal developers

2) In a public portal for external developers/clients

Here is diagram created by me to help you understand sequence:

Diagram Description automatically generated

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.

For details refer to this documentation : https://semver.org/

Metadata is stored in application-types.xml flle located under src/main/resources.

Mule 4 applications contain an application-types.xml file, which is where metadata around your data types is stored. For example, if you create a new CSV type, that metadata will be added to this file. This new file is easy to share, commit, and merge when conflicts arise, which enables you to do more metadata-driven development.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/intro-studio#metadata-storage

Correct answer is /accounts?account_type=retail&industry=finance

Query parameters are a defined set of parameters attached to the end of a url. They are extensions of the URL that are used to help define specific content or actions based on the data being passed. To append query params to the end of a URL, a ‘?’ Is added followed immediately by a query parameter.

To add multiple parameters, an ‘&’ is added in between each.

Allowed methods is an optional configuration. If nothing is specified then all HTTP methods are supported.

Rest all are mandatory.

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}

Correct answer is Save the payload from the Database SELECT operation to a variable

Response from HTTP request will override the payload and hence response of database SELECT can be lost. Best way to preserve is to assign payload of first operation to variable using TransformMessage.

In General > Request > Query Parameters, click the plus icon (+) to add a parameter to a request. Type a name and value for the parameter or use a DataWeave expression to define the name and value.

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

This is a trick question.

You can call only flows from DataWeave using lookup function. Note that lookup function does not support calling subflows.

A subflow needs a parent context to inherit behaviors from such as exception handling, which a flow does not need

Hence correct answer is Not possible in Mule 4

Option1 is correct syntax to configure HTTP Listener endpoint

Pick First is not valid type. Rest all are valid type of event processor.

Choice : https://docs.mulesoft.com/mule-runtime/4.3/choice-router-concept

Round Robin : https://docs.mulesoft.com/mule-runtime/4.3/round-robin

First Successful : https://docs.mulesoft.com/mule-runtime/4.3/first-successful

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:

The current version of the RAML specification is 1.0

You can check RAML version in RAML definition by referring to first comment. See highlighted part in below image.

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

By default, Debugger listens for incoming TCP connections on localhost port 6666 You can change this in a project's run configuration.

MuleSoft Doc Ref : https://docs.mulesoft.com/studio/7.5/visual-debugger-concept

Correct answer is Creates and manages discoverable assets to be consumed by line of business developers.

C4E does not get directly involved in projects.

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

MuleSoft Doc Ref : https://docs.mulesoft.com/studio/7.8/import-export-packages

Choice router finds the FIRST true condition, then distribute the event to the ONE matched route.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.1/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.

Diagram Description automatically generated

Its primary function is to design and develop fully functional Mule applications in a hosted development environment.

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.

A picture containing timeline Description automatically generated

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.

Diagram Description automatically generated

Lets revise few concepts RAML which can help us to find the answer of this question.

URI Parameters

Lets have a look at below example.

• /foos:
• /{id}:
• /name/{name}:

Here, the braces { } around property names define URI parameters. They represent placeholders in each URI and do not reference root-level RAML file properties as we saw above in the baseUri declaration. The added lines represent the resources /foos/{id} and /foos/name/{name}.

Query Parameters

Now we'll define a way to query the foos collection using query parameters. Note that query parameters are defined using the same syntax that we used above for data types:

• /foos:
• get:
• description: List all Foos matching query criteria, if provided;
• otherwise list all Foos
• queryParameters:
• name?: string
• ownerName?: string

Based on the above information , below is the only option which defines storeid as uri parameter and department as query parameter.

• /{storeId}:
• get:
• queryParameter:
• department:

Keyword to ad function in Dataweave transformation is fun. Hence option 2 and 4 are invalid. Also parameters needs to be passed exactly in same order as defined in function definition. Hence correct answer is'

fun addKV( object: Object, key: String, value: Any) =

object ++ {(key):(value)}

---

addKV ( {"hello': "world"}, "hola", "mundo" )

MuleSoft Documentation Reference : https://docs.mulesoft.com/mule-runtime/4.3/dataweave-functions

DataWeave Function Definition Syntax

To define a function in DataWeave use the following syntax:

fun myFunction(param1, param2, ...) =

The fun keyword starts the definition of a function.

myFunction is the name you define for the function.

Function names must be valid identifiers.

(param1, param2, … , paramn) represents the parameters that your function accepts.

You can specify from zero to any number of parameters, separated by commas (,) and enclosed in parentheses.

The = sign marks the beginning of the code block to execute when the function is called.

represents the actual code that you define for your function.