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

Correct answer is 8 as events are processed in parallel in case of scatter gather router

1. Set Payload “Start”

2. 'Is Balnk String' Creates an Error object with #[error.description] =“String is not blank”

3. Default Error Handler catches and Propagates error

4. 'On Error Propogate' is 'RED IN RED OUT'. It Returns Status Code : 500 & #[error.description]

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

Correct answer is String is not blank. Because validation component will throw an error as payload is not blank.

A picture containing timeline Description automatically generated

Bottom of Form

Top of Form

Correct answer is Array.

Flatten turns a set of subarrays (such as [ [1,2,3], [4,5,[6]], [], [null] ]) into a single, flattened array (such as [ 1, 2, 3, 4, 5, [6], null ]).

This example defines three arrays of numbers, creates another array containing those three arrays, and then uses the flatten function to convert the array of arrays into a single array with all values.

Source

%dw 2.0

output application/json

var array1 = [1,2,3]

var array2 = [4,5,6]

var array3 = [7,8,9]

var arrayOfArrays = [array1, array2, array3]

---

flatten(arrayOfArrays)

Output

[ 1,2,3,4,5,6,7,8,9 ]

Mule applications can be scaled vertically by changing worker size. Mule applications can be scaled horizontally by adding more workers.

As dependency is not present in Mulesoft Maven repository, we need to install the dependency on computer's local Maven repository.

https://docs.mulesoft.com/mule-runtime/4.3/maven-reference

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

Database always return rows as an array.

Array is the correct answer

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

Transform Message Add write_date is coverting payload in JSON format and same JSON payload is avaialble to file write processor. However, if the payload is a different format (for example, not CSV) , you can place the transformation inside the Write operation to generate content that will be written without producing a side effect on the message in transit. This is not done in this case. By default, the connector writes whatever is in the message payload. Hence JSON payload will be written to file.

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

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

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

Correct answer is String is not blank.

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

Here’s specifically what is happening here:

1) Payload is successfully set to “Start”

2) The Is Blank String validator creates an Error Object because the payload is string "Start". Execution stops

#[error.description] = “String is not blank”

3) Because no error handler is defined, the Mule default error handler handles the error. Remember, at its heart, the Mule Default Error handler is an error handling scope with just an on error propagate

4) “String is not blank” is the error message returned to the requestor in the body of the HTTP requestHTTP Status Code: 500

Reference Diagram:

A picture containing diagram Description automatically generated

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 Nothing needs to be changed in the other APIs or their associated applications

This is the benefit of having separate interface layer. As there are no changes to interface , no changes are required on the API's which consumes this API in context

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

Metadata is stored in application-types.xml flle located under src/main/resources.

Mule 4 applications contain an application-types.xml file, which is where metadata around your data types is stored. For example, if you create a new CSV type, that metadata will be added to this file. This new file is easy to share, commit, and merge when conflicts arise, which enables you to do more metadata-driven development.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/intro-studio#metadata-storage

Empty array is returned when no rows are matched.

MuleSoft Doc Ref : https://docs.mulesoft.com/db-connector/1.9/database-connector-select

Correct answer is Modify the API implementation to use auto-discovery to register with API Manager

API Autodiscovery

Configuring autodiscovery allows a deployed Mule runtime engine (Mule) application to connect with API Manager to download and manage policies and to generate analytics data. Additionally, with autodiscovery, you can configure your Mule applications to act as their own API proxy.

When autodiscovery is correctly configured in your Mule application, you can say that your application’s API is tracked by (green dot) or paired to API Manager. You can associate an API in a Mule setup with only one autodiscovery instance at a given time.

MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept

Sequence can be described as follows.

* When web client sends the request , it sends payload as Blue (mentioned in question)

* In first iteration this will go to default choice , which sets payload to Red

* Via default route , flow will call itself with payload as Red

* In second iteration , as payload is Red , it will go to first route in choice router which will set payload to Blk and second iteration will end returning back payload as Blk to first iteration.

* This Blk will be again set to payload and first iteration will end returning back response as Blk

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

Below are the Key performance indicators (KPIs), to measure and track the and success of the C4E and its activities, as well as the growth and health of the application network. Most of the metrics can be extracted automatically, through REST APIs, from Anypoint Platform.

• # of assets published to Anypoint Exchange

• # of interactions with Anypoint Exchange assets

• # of APIs managed by Anypoint Platform

• # of System APIs managed by Anypoint Platform

• # of API clients registered for access to APIs

• # of API implementations deployed to Anypoint Platform

• # of API invocations

• # or fraction of lines of code covered by automated tests in CI/CD pipeline

• Ratio of info/warning/critical alerts to number of API invocations

* To use custom modules, you need to import the module or functions you want to use by adding the import directive to the head of your DataWeave script, for example:

1) Does not identify any functions to import from the String module:

import dw::core::Strings

2) To identify a specific function to import from the String module:

import camelize, capitalize from dw::core::Strings

3) To import all functions from the String module:

import * from dw::core::Strings

The way you import a module impacts the way you need to call its functions from a DataWeave script. If the directive does not list specific functions to import or use * from to import all functions from a function module, you need to specify the module when you call the function from your script.

* In given scenario, it's mentioned to import all of the WebStore.dwl

So correct answer is:

Correct answer is as below.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.

{

"0": {

"attributes": ...,

"payload": "100"

},

"1": {

"attributes": ...,

"payload": "200"

}

}

Bottom of Form

You can define your own DataWeave functions using the fun declaration in the header of a DataWeave script. Sample is as below. ----------------------------------------

%dw 2.0

output application/json

fun toUpper(aString) = upper(aString)

---

toUpper("hello")

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.1/dataweave-functions

MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/2.x/policy-mule3-tutorial-manage-an-api#to-add-the-tier

Steps to create SLA Tier are as follows:

1) In API Manager, in API Administration, click a version.

2) Check that the API supports resource-level policies: On the API version details page, in Status, click Configure Endpoint, and check that Type is RAML.

3) Choose the SLA Tiers, and click Add SLA Tier. Set up limit on SLA tier

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 is URL 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 not happen 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 : HTTP Listener Reference - Mule 4 | MuleSoft Documentation

Creates reusable APIs and assets designed to be consumed by other business units

Option1 is correct syntax to configure HTTP Listener endpoint

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

Correct answer is Subflow has no error handling implementation where as sync flow has.

Subflow

A subflow processes messages synchronously (relative to the flow that triggered its execution) and always inherits both the processing strategy and exception strategy employed by the triggering flow. While a subflow is running, processing on the triggering flow pauses, then resumes only after the subflow completes its processing and hands the message back to the triggering flow.

Synchronous Flow

A synchronous flow, like a subflow, processes messages synchronously (relative to the flow that triggered its execution). While a synchronous flow is running, processing on the triggering flow pauses, then resumes only after the synchronous flow completes its processing and hands the message back to the triggering flow. However, unlike a subflow, this type of flow does not inherit processing or exception strategies from the triggering flow.

This type of flow processes messages along a single thread, which is ideally suited to transactional processing

* When a client application is registered in Anypoint Platform, a pair of credentials consisting of a client ID and client secret is generated.

* When the client application requests access to an API, a contract is created between the application and that API.

* An API that is protected with a Client ID Enforcement policy is accessible only to applications that have an approved contract.

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

Correct Answer: In the organization's public API portal in Anypoint Exchange, from an approved client application for the API proxy

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

The flow can be described as below. 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.

Correct answer is as below. On complete phase only has access to batch job result statistics and payload is not available.

• Total Records Processed: 3
• Successful Records: 3
• Failed Records: 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 system administrators 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

Correct answer is 200.1234 as String {format: ".0#"} . Rest all options are not syntactically correct.

Scatter-Gather sends the event to each routes concurrently. Hence both route in this example will start in parallel. So total time to complete processing is 40 seconds

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

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

Properties of

PropertyDescription

Expression (expression)

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

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.

Correct answer is /accounts?account_type=retail&industry=finance

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.

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

Points to remember:

* XML must have a root element.

* XML only allows one root element

* To avoid multiple root issues, you must create a root element for the XML output, whenever we transform output

* When mapping array elements (JSON or JAVA) to XML, wrap the map operations in {(..)}

-{ } are defining the object

( ) are transforming each element in the array as a key/value pair

* The transformation to XML would fail if the above mentioned considerations were not taken into account.

* Thus the transformation script declares a root element as trains and wraps the data in “{( )}“.

Whenever you see such type of question, always look out for root element followed by {( )} wrapping map.

I call this a "Wrap The Map" scenario. Hope it would help you remember !

Web Services Description Language. WSDL is used to describe SOAP based web services

Paths

The path of 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 capture those 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

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

Root element is always required while creating XML response in DataWeave transformation

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