Salesforce-MuleSoft-Developer-I Salesforce Certified MuleSoft Developer (Mule-Dev-201) Questions and Answers

Correct Answer: Response body: " Error " Default response status code: 200.

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

1) Payload is successfully set to “Success – Started Flow”

2) When HTTP Request throws an error, execution halts

#[error.description] = “ABC "

#[error.errorType] = " XYZ "

3) The On Error Continue scope handles the error. When On Error Continue scope is invoked, all the processors in error block are executed and success response is sent back to the client with payload which is set in error flow. In this case payload is set to " Error " value in error block.

4) “Error” is returned to the requestor in the body of the HTTP request with HTTP Status Code: 200 as On error continue always sendssuccess error code.

Reference Diagram:

Timeline Description automatically generated with medium confidence

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

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 triggersthat 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

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

Error in validation component will get processed by Processer level On Error Propagate block and thenerror will be rethrown which will get processed by flow level error handler which will set payload to " Error- main flow " . Hence correct answer is Error - main flow

1) Request is received by HTTP listener

2) Try scope gets executed

3) The validator component in the Try scope creates an Error Object because the payload is not null.

4) The On Error Propagate handles the error. The payload is set to “Error – Try scope”

6) “Error – Try scope” is returned to the ' On Error Continue ' block. Main flow execution stops. Payload is set to " Error - main flow "

7) “Error - main flow” is returned to the requestor in the body of the HTTP request. HTTP Status Code: 200

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

Reference Diagram though not exactly same, conditions are similar. They will help you answer any new question on error handling in real exam:

Timeline Description automatically generated

https://docs.mulesoft.com/mule-runtime/4.3/on-error-scope-concept#on-error-continue

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

Exchange is the odd man out here. Rest all are type of asset

Graphical user interface, application Description automatically generated

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 "

}

Correct answer is Publish the API to Anypoint Exchange

Anypoint Exchange makes this possible bymaking 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

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 scopewhich 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 Referencecalls 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 OnError 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

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

Rest all are mandatory.

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

Correctanswer is [[5, 10, 15, 20], 5]

Key thing to note here is that any changes made to payload in for each loop are not available outside for each scope where as variable value updated in for each loop is visible out side for each loop too.

In this example , sequence can be described as follows

1) Payload is set to the value [5, 10, 15, 20]

2) Variable is set to the value of 1

3) For each loop is executed four times and in each loop payload value is updated to append " Req " and variable is count is increased by 1

4) Once control comes out of for each , payload changes made within for each are not visible. Hence payload at this point of time is equal to payload available before entering for each loop which was  [5, 10, 15, 20]. Similarly variable value updated in for each loop is also available outside hence variable value is 5 as it was updated in loop.

5) Hence correct answer is [[5, 10, 15, 20], 5]

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 programming languages 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 because they are related to the entire message.

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

For non-Java collections, such as XML or JSON, use a DataWeave expression to split data. Use the Collection field for this purpose.

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

POM.xml contains info about the project and configurationn details used by Maven to build the project

Cloudhub exposeservices on port 8081 and override value in http.port with this one .

Sample log in Runtime Manager is below

21:15:53.148 08/08/2021 Worker-0 ArtifactDeployer.start.01 INFO

Listening for connections on ' http://0.0.0.0:8081 '

option 3 is the correct syntz to access application properties

Correct answer is Specify throttling , security and other policies

MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/2.x/api-gateway-capabilities-mule4

API Gateway isresponsible for below functions.

1) Determine which traffic is authorized

2) Meter the traffic

3) Logs transaction

4) Apply throttling and other policies (Not specifying. These are specified in API Manager)

Graphical user interface, text, application 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 as below. On complete phase only has access to batch job result statistics and payload is not available.

TotalRecordsProcessed:3

SuccessfulRecords:3

FailedRecords:0

On Complete

During this phase, you can optionally configure the runtime to create a report or summary of the records it processed for the particular batch job instance. This phase exists to give systemadministrators and developers some insight into which records failed to address any issues that might exist with the input data.

Sample output is as below

Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept#on-complete

WSDL is used to define the contract in case of SOAP . RAML/OAS is used to REST services

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

Diagram Description automatically generated

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

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

As can be seen in RAML, POST expects input in application/json format which eliminates two of the options as two options are in xml format.

Now out of the two remainingoptions, one has id field in request which is only mentioned for get response and not for POST request. Hence id field is not expected in POST request.

Hence correct answer is

{

" name " : " GoerdiLa Forge " ,

" address " : " 1 Westland CA " ,

" customer_since " : " 2014-01-04 " ,

" balance " : " 4829.29 " ,

" bank_agend_id " : " 12556 "

}

Creates reusable APIs and assets designed to beconsumed by other business units

Gold is not valid category for connector types.

MuleSoft Doc Ref :https://docs.mulesoft.com/mule-runtime/3.7/anypoint-connectors#connector-support-categories

Text Description automatically generated with medium confidence

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

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 : https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept#on-complete

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

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

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

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 : https://docs.mulesoft.com/mule-runtime/4.3/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

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

Correct answer is An Object containing all three Mule event Objects

The Scatter-Gather component is a routing 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 componentthen combines the Mule events returned by each processingroute 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.

Sample output is as below

Table Description automatically generated with low confidence

MuleSoft Documentation reference :https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept

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

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 request http://awesome-company.com/api/v1/account/mulesoft/main-contact

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

account/{accountId}/*: matches all path requests different from main-contact, such as http://awesome-company.com/api/v1/account/mulesoft/users, and save mulesoft as the value of accountId.

Mule Ref Doc : https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#paths

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

Graphical user interface Description automatically generated

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.

MuleSoft Documentation Reference : https://docs.mulesoft.com/db-connector/1.9/database-connector-select

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

Correct answer is A global element

Global error handlers are to be created in global element .

Quick note to remember here is Global error handlers come in to pictureonly when there are no error handlers specified as flow level.

Steps to create Global error handler

1) Click Global Elements to open Global Configuration Elements. Global Elements is located below the Studio canvas

2) In Global Configuration Elements,click Create to open the Choose Global Type dialog

Graphical user interface, text, application, chat or text message Description automatically generated

3) From the dialog, select Global Configuration -→ Configuration, and then click OK to open the Configuration dialog.

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

4) From the select Configuration dialog, select allErrorHandler for the Default Error Handler field, and click OK.

Correct answer is vars. " customer " . " firstName "

Please note that you can also access firstName using this syntax vars.customer.firstName.

Mule Ref Doc : Variables in Mule Apps | MuleSoft Documentation

First step in creating Modern API is to create an API specification and get feedback from stakeholders so that any future issues can be identified at early stage thereby reducing overall delivery time

APIKIt Creates a separate flow for each HTTP method

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 Products

Modern API has three features 1) Treated as products for easy consumption 2) Discoverable and accessible through self-service 3) Easily managed for security , scalability and performance