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

Correct answer is below as it follows the correct syntax.

/customers:

/{customerId}:

get:

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

Scatter-Gather Router

The Scatter-Gather component is arouting event processor that processes a Mule event through different parallel processing routes that contain different event processors. Each route receives a reference to the Mule event and executes a sequence of one or more event processors. Each of these routes uses a separate thread to execute the event processors, and the resulting Mule event can be either the same Mule event without modifications or a new Mule event with its own payload, attributes, and variables. The Scatter-Gather component then combines the Mule events returned by each processing route into a new Mule event that is passed to the next event processor only after every route completes successfully.

The Scatter-Gather component executes each route in parallel, not sequentially. Parallel execution of routes can greatly increase the efficiency of your Mule application and may provide more information than sequential processing.

Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

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

QUESTIONNO: 232

Refer to the exhibit. This RAML fragment defines a Book data type that is used in a RAML API specification.

An API implementation is created for this RAML API specification.

What is valid JSON input for a request from a web client to an implementation of this RAML API specification?

A.

B.

C.

D.

Answer: B

The HTTP 415 Unsupported Media Type client error response codeindicates 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. Asper RAML input is expected in application/xml.

Hence correct answer is Set a request header with the name Content-Type to a

URI parameter (Path Param) is basically used to identify a specific resource or resources . For eg : the URL to get employee details on the basis of employeeID will be GET/employees/{employeeID} where employees is resource and {employeeID} is URI parameter. Hence option 1is the correct answer

Correct answer is ${training.host}

Correct answer is Add required headers to RAML specification and redeploy new API proxy

MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/2.x/tutorial-manage-an-api

Steps are as below :

Add the Required RAML Snippet

SLA-based rate limiting requires adding a RAML or OAS snippet to your API. This procedure demonstrates adding a RAML snippet.

Specify the client ID and secret as query parameters.

Add a section called traits: at the RAML root level to define query parameters:

traits:

-client-id-required:

queryParameters:

client_id:

type: string

client_secret:

type: string

Add the client-id-required trait to every method that requires these query parameters:

/users:

get:

is: [client-id-required]

description: Gets a list of JSONPlaceholder users.

Step 2 : Add the SLA Tier in API Manager

Step 3 : Apply the policy and redeploy

Option 1 is the correct syntax

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 FunctionDefinition 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 namesmust 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 thecode block to execute when the function is called.

represents the actual code that you define for your function.