Salesforce Salesforce-MuleSoft-Developer-I Salesforce Certified MuleSoft Developer (Mule-Dev-201) Exam Practice Test

As can be seen in error message , SOAP service findFlights expects the SOAP paylaod. This can be set using transform message processor which forms SOAP payload before the Consume operation that contains the destination query parameter

Only one of the routes in the Choice router executes, meaning that the first expression that evaluates to true triggers that route1 execution and the others are not checked. If none of the expressions are true, then thedefault route executes. Hence only Route1 will be executed as it is the first expression. hence output of logger is Route1.

MuleSoft Doc Ref :

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

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

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 :

API portal are created by API Exchange and cannot be created by Design Center

Paths

The pathof an HTTP listener can be static, which requires exact matches, or feature placeholders. Placeholders can be wildcards (*), which match against anything they are compared to, or parameters ({param}), which not only match against anything but also capturethose values on a URI parameters map.

Take the following example paths for three listeners using a configuration that establishes api/v1 as the base path:

account/mulesoft/main-contact: only match the exact path

account/{accountId}/main-contact: matches all path requests structured similarly, such and save salesforce as the value of accountId.

account/{accountId}/*: matches all path requests different from main-contact, such and save mulesoft as the value of accountId.

Mule Ref Doc

URL parameters are always accessed using { } like => {customerID}

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

Correct answer is Change the method attributes value to "POST".

It can be fixed in either of the two ways as below.

1) Changing method attribute to POST in ClientRequestFlow

2) Setting allowedMethods as PUT in ShippingFlow (but doesn't fit as question mentions about changing ClientRequestFlow)

The current version of the RAML specification is 1.0

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

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

Database always return rows as an array.

Array is the correct answer

QUESTIONNO: 111

Refer to the exhibits.

A web client submits a request to below flow. What is the output at the end of the flow?

Diagram Description automatically generated

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

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

A. String

B. Object

C. Java

D. XML

Answer: A

String is the correct answer as XML is of an Object type String

Variables are stored under Mule event. Please refer to below image for the hierarchy .

Graphical user interface Description automatically generated

Correct answer is 0.1 vCores

MuleSoft Doc Ref

CloudHub Workers

Workers are dedicated instances of Mule runtime engine that run your integration applications on CloudHub. The memory capacity and processing power of a worker depends on how you configure it at the application level.

Worker sizes have different compute, memory, and storage capacities. You can scale workers vertically by selecting one of the available worker sizes:

Table Description automatically generated

File is not updated when FTP read operations is performed.

MuleSoft Doc Ref :

Mule event is correct answer. Mule event has two parts which are as follows

1) Message (which contains payload and attributes like headers and query/uri parameters

2) Variables

Diagram Description automatically generated

Correct answer is The city is #[payload.City]

Answer can get confused with the option #["The city is" ++ payload.City] But note that this option will not print the space between is and city name. This will print The city isPune

This kind of questions are best solved with filtering technique. Key thing to note here is XML attributes are always access by @ notation. So in thisexample orderId can be accessed as @OrderId which makes option 3 and option 4 false. Now difference in optin and option 2 is in mapping of lineItemPrice. Correct syntax to format a String in Numbse is value.price as Number. Hence option 2 is correct

Process section is must to get compiles. Process section must have one or more processors

Diagram Description automatically generated

Correct answer is as below.After all processing routes have finished execution, the Scatter-Gathercomponent creates a new Mule event that combines all resulting Mule events from each route, and then passes the new Mule event to the next component in the flow.

{

"0": {

"attributes": ...,

"payload": "100"

},

"1": {

"attributes": ...,

"payload": "200"

}

}

Bottom of Form

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

Here’s specifically what is happening here:

1) Payload is successfully set to “Before”

2) Is null validation is used which will pass the message only if payload is null. In this case as payload is not null, it creates an Error Object. Flow execution stops

#[error.description] = “Validation error”

3)Because no error handler is defined, the Mule default error handler handles the error

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

Reference diagram:

A picture containing timeline Description automatically generated

Core (dw::Core) This module contains core DataWeave functions for data transformations. It is automatically imported into any DataWeave script.

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

Rest all are mandatory.

This is a trcik question. On complete phase pyalod consists of summary of records processed which gives insight on which records failed or passed. Hence option 4 is correct answer

MuleSoft Documentation Reference :

To include property. To keep the API definition concise, you can include external content, such as documentation, schemas, and frequently used patterns outside the definition itself. Theparser interprets !include as if the content of the externally-hosted file or a URL were declared in-line.

To use the fragments in RAML you have to include the exact path(copy the path) of that fragment you want to use as shown below

Option 3 is the correct as correct syntax is

examples: !include examples/StudentExample.raml

Correct answer is Validation modules Is Number operation.

Mule 4 does not use filters anymore. The functionality provided by filters in Mule 3 can be achieved by using the Validation Module.

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

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.

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 eachelement in the array as a key/value pair

Correct answer is as below as concatenation operation worksonly 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

In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues.

Hence correct answer is

The mule application start successfully

Web client requests can  be received at URI on port 2222 and on port 3333.

Lets check why other options are incorrect

1) The mule application fails to start. There isURL path conflict because both HTTP Listeners are configured with same path  ---- This is incorrect as port value is different in both listeners

2) The mule application start successfully. Web client requests can only be received at URI on port 2222 but not on port 3333  --- This is incorrect as there is no reason for not receiving requests on port 3333

3) The mule application fails to start because of the port binding conflict as HTTP request also use same port i.e. 3333 --- Port binding conflict will nothappen in this case. It would have if both listener configurations would have been on same port . But that is not the case here.

Mule Ref Doc : HTTPListener Reference - Mule 4 | MuleSoft Documentation

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

MuleSoft Doc Ref :

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

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

C4E does not get directly involved in projects.

Gold is not valid category for connector types.

MuleSoft Doc Ref

Text Description automatically generated with medium confidence

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.

Hence coming back to question, endpoint would return Patients with name as John and (and is very important here) surname as Bell

APIKIt Creates a separate flow for each HTTP method

Correct answer is API manager

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

Anypoint Exchange provided a way to publish , share and search API's.

MuleSoft Doc Ref :

In General > Request > Query Parameters, click theplus 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

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

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

* Correct answer is

/departments:

/{deptId}:

patch:

Correct answer is as below. In this case address will be stored in a variable. Hence payload will not be overwritten and will contain order details

{

orderkey: "payload.order",

addresskey: "vars.address"

}

option 3 is the correct syntz to access application properties

Centre for Enablement (C4E) is an IT operating model that enables an enterprise to build reusable assets, accumulate API’s, leveragebest practices and knowledge to enable self service and efficient delivery in the organization and implement new solutions faster

Returns an array that is the result of applying a transformation function (lambda) to each of the elements.

MuleSoft Doc Ref :

Themap operator is a function in Dataweave which iterates over the items in an array and outputs them into a new array. It basically accepts input as a list of items in an array and manipulates the items in the array in order to form a new array as an output.

I have created below chart for your easier understanding:

Table Description automatically generated

Correct answer is an operation. For each method of the RAML specification , REST connect module provide an operation.

Please refer to the belowscreenshot.

Option1 is correct syntax to configure HTTP Listener endpoint

Entire event would be sent to each route in parallel.

Scatter-Gather works as follows :

- TheScatter-Gather component receives a Mule event and sends a reference of this Mule event to each processing route.

- Each of the processing routes starts executing in parallel. After all processors inside a route finish processing, the route returns a Muleevent, which can be either the same Mule eventwithout modifications or a new Mule event created by the processors in the route as a result of the modifications applied.

- After all processing routes have finished execution, the Scatter-Gather component creates a new Mule event that combines all resulting Mule events from each route, and then passes the new Mule event to the next component in the flow.

Diagram Description automatically generated

For Each Scope

The For Each scope splits a payload into elements and processes them one by one through the components that you place in the scope. It is similar to a for-each/for loop code block in most programminglanguages and can process any collection, including lists and arrays. The collection can be any supported content type, such as application/json, application/java, or application/xml.

General considerations about the For Each scope:

By default, For Each tries to split the payload. If the payload is a simple Java collection, the For Each scope can split it without any configuration. The payload inside the For Each scope is each of the split elements. Attributes within the original message are ignored becausethey are related to the entire message.

For Each does not modify the current payload. The output payload is the same as the input.

Mule Doc Reference

In case ofan error , batch job completes in flight steps and stops further processing.

MuleSoft Doc Ref : Handling Errors During Batch Job | MuleSoft Documentation

The default is all processing will stop but we can change it by Max Failed Record field.

General -> Max Failed Records: Mule has three options for handling a record-level error: Finish processing, Continue processing and Continue processing until the batch job accumulates a maximum number of failed records. This behavior can be controlled by Max Failed Records.

The default value is Zero which corresponds to Finish processing.

The value -1, corresponds to Continue processing.

The value +ve integer, corresponds to Continue processing until the batch job accumulates a maximum number of failed records

client-id-required enforces clients to add client_id and client_secret.

Please refer to below steps.

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

traits:

- client-id-required:

queryParameters:

client_id:

type: string

client_secret:

type: string

2) Reference the trait in each of the methods to specify that each of the methods require these queryparameters. After each method in the RAML file, add is: [client-id-required]. For example:

/users:

get:

is: [client-id-required]

description: Gets a list of JSONPlaceholder users.

The flow can be described asbelow. 1) First HTTP POST requets is made in which paylaod is set to 1 and it gets returned to our mail flow. 2) Second call is initiated for JMS Publish Consume JMS: num1 which add 1 to the payload which makes it as 2. Note that pubih consume is a synchronous operation. Hence paylaod is returned to main flow. 3) Third call is initiated for JMS Publish JMS: num2 which add 1 to the payload . Note that pubih is asynchronous operation. Hence paylaod is never returned to main flow. So payload in main flow is still 2. 4) Finally Set Payload increments payload by 1 making payload as 3 which is returned by the flow. Hence option 3 is the correct answer.