Salesforce-MuleSoft-Developer-I Salesforce Certified MuleSoft Developer (Mule-Dev-201) Free Practice Exam Questions (2025 Updated)

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

Publish consume: Synchronous. Publish: Asynchronous.

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

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 sothe 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.

21]">

...

Mule Ref Doc : Refining Batch StepsProcessing | 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 and102 (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 inbatch 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 as below. Attributes in the incoming xml payload are always accessed using @.Similarly *item is requiredas we have multiple items in the request

%dw 2.0

output application/csv

---

payload.sale.*item map ((value, index) -> {

index: index,

sale: value.@saleId,

itemName: value.desc,

itemPrice: (value.quantity) * (value.price),

item: value.@itemId

} )

QUESTIONNO: 96

Refer to the exhibits.

The main flow contains a Flow Reference to the child flow.

A web client sends a GET request to the main flow's HTTP Listener that includes a make query parameter.

What values are accessible in the child flow?

A. payload

B.payload

make query param

C. payload

model var

D. payload

make query param model var

Answer: D

Correct answer is ${training.host}

Correct answer is APP: API RESOURCE NOT FOUND

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

1) A web client submits the request to the HTTP Listener.

2) The HTTP Request throws an "HTTP:NOT_FOUND" error, execution halts.

3) The On Error Propagate error Handler handles the error. In this case ,HTTP:NOT_FOUND error ismapped to custom error APP:API_RESOURCE_NOT_FOUND. This error processor sets payload to APP:API_RESOURCE_NOT_FOUND.

4) “APP:API_RESOURCE_NOT_FOUND. ” is the error message returned to the requestor in the body of the HTTP request with HTTP Status Code: 500

Reference Diagram:

Diagram Description automatically generated with medium confidence

Option 1 is the only correct choice due to two reasons. 1) Concatenation is always with ++ sign and not with + sign which makes option 2 and 3 wrong2) hearders can be accessed with attributes. headers and not with only headers which makes option 4 incorrect

In this case as outbound call is made using HTTP: POST /child , all attributes will be replacedby this invocation. Hence query parameter will not be accessible at logger.

This is a trick question.

You can callonly 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

Choice Router

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 routingoption. 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 thatroute’s execution and the others are not checked. If none of the expressions are true, then the default route executes.

Properties of

PropertyDescription

Expression (expression)

Expression in DataWeave language to evaluate input.If the expressionevaluates to true, this routing option is used:

Mulesoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/choice-route r-concept

With respect to above information ,

Option 1 is the correct syntax as others are incorrect because of below reasons

* Single = is not the correct syntax to validate the condition. It should be ==

* If keyword is not required in when condition.

Setting Breakpoints

To set breakpoints, right-click a building block, then select Toggle Breakpoint.

Studio applies a red dot to the building block’s icon on the canvas.

When you run your application in Debug mode, Studio stops the flow execution at the breakpoint you have set, allowing you to check the Mule Event content in the Mule Debugger View.

Mule Ref Doc : Setting Breakpoints | MuleSoft Documentation