Free Salesforce Certified MuleSoft Developer (Mule-Dev-201) Exam Dumps July 2026

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:

PUT replaces the original version of the resource, whereas the PATCH method supplies a set of instructions to modify the resource

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 oneacceptExpressionand oneacceptPolicyattributes to filter records.

Use theacceptExpressionattribute 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 filtersout.

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

<batch:job jobName='batchJob'>

<batch:process-records >

<batch:step name='adultsOnlyStep' acceptExpression='#[payload.age > 21]'>

...

</batch:step>

</batch:process-records>

</batch:job>

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}

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 routing option. The effect is to add conditional processing to a flow, similar to anif/then/elsecode block in most programming languages.

Only one of the routes in the Choice router executes, meaning that the first expression that evaluates totruetriggers that route's execution and the others are not checked. If none of the expressions aretrue, then the default route executes.

Properties of <when>

PropertyDescription

Expression (expression)

Expression in DataWeave language to evaluate input. If the expression evaluates totrue, this routing option is used:

<when expression='#[vars.language == 'Spanish']' >

Mulesoft Doc Ref :https://docs.mulesoft.com/mule-runtime/4.3/choice-router-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.