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

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 '

File is not updated when FTP read operations is performed.

MuleSoft Doc Ref : https://docs.mulesoft.com/file-connector/1.3/file-read

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

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

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

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

Graphical user interface, application Description automatically generated

option 3 is the correct syntz to access application properties

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

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

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.

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

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

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

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

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

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

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

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:

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

Organization Administrators can approve/revoke/delete SLA tier access requests via API Manager only

QUESTIONNO: 132

What is not true about application properties?

A. Application properties can be encrypted

B. Application properties can be overridden with system properties

C. Application properties can be defined in .yaml file only

D. Application properties provide easier way to manage configurable values

Answer: C

Application properties can be defined in .yaml or in .properties file.

MuleSoft Doc Ref :https://docs.mulesoft.com/mule-runtime/4.3/configuring-properties#supported_files

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

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

Flow Reference Component

Flow Reference routes the Mule event to another flow orsubflow, executes all processors in the referenced flow, and then routes the event back within the same Mule application. The following diagram shows the order of processing when one flow references another:

When the main flow is triggered, the Muleevent travels through and executes the flow until the event reaches the Flow Reference. The event then travels through and executes the referenced flow from beginning to end, and then returns to the main flow.

This process enables you to treat the entire referenced flow like a single component in your current flow.

Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/flowref-about

Correct answer is

payload

quantityvar

colorquery param

Correct answer is */status as it is the correct way to use wildcards while configuring path value in HTTP listener

Lets revise few concepts RAML which can help us to find the answer of this question.

URI Parameters

Lets have a look at below example.

/foos:

/{id}:

/name/{name}:

Here, the braces { } around property names define URI parameters. They represent placeholders in each URI and donot reference root-level RAML file properties as we saw above in the baseUri declaration. The added lines represent the resources /foos/{id} and /foos/name/{name}.

Query Parameters

Now we'll define a way to query the foos collection using query parameters.Note that query parameters are defined using the same syntax that we used above for data types:

/foos:

get:

description:ListallFoosmatching query criteria,ifprovided;

otherwise list allFoos

queryParameters:

name?:string

ownerName?:string

Based on the above information , below is the only option which defines storeid as uri parameter and department as query parameter.

/{storeId}:

get:

queryParameter:

department:

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.

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

C4E does not get directly involved in projects.

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

Subflow

A subflow processes messages synchronously (relative to the flowthat 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

The HTTP 415 Unsupported Media Type client error response code indicates 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. In this case as per RAML specification data is expected in application/json and in request Content-Type is set as "text/plain" which is incorrect. Hence solution is set the request Content-Type header to application/json

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/415

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.

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

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

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

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/dataweave-cookbook-map

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

1. SetPayload “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 ofForm

Top of Form

Option 2 is the correct answer as /api/* accespts everything starting with /api/

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

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

Correct answer is 0.1 vCores

MuleSoft Doc Ref :https://docs.mulesoft.com/runtime-manager/cloudhub-architecture#cloudhub-workers

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

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

Points toremember:

* 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 mapoperations 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 scriptdeclares 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 !

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

Attributes are replaced with new attributes from the HTTP Request response.

Attributes include everything apart from Payload/body. For ex: Headers, query parameters, URI parameters.

So, when outbound HTTP request is made, new attributes need to passthe outbound HTTP request and old attributes are replaced.

I have created below diagram to make it easy for you to understand:

Diagram Description automatically generated

Below are the Key performance indicators (KPIs), to measure and track the and success of the C4E and its activities, as well as thegrowth 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 managedby 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

Correct answer is ${training.host}

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

How to Configure Properties to Mule 4.X Platform?

1) Go to /src/main/resources project directory.

2) Create aconfiguration file with the name configuration.yaml inside the newly created config folder.

                                           Graphical user interface, application, Word Description automatically generated

3) Go To Project > Global Element > Create > General >select the configuration.yaml file create in step- 2)

                                             Graphical user interface, application Description automatically generated 

4) To verify develop a simple flow with HTTP listener which has above entries. Put the logger that prints the values on console.

                                               Graphical user interface, application Description automatically generated

5) Additional info: Similarly, when you want to access this port in DataWeave you need to use p function

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

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