Salesforce Salesforce-MuleSoft-Developer-I Dumps

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

Correct answer is APP: API RESOURCE NOT FOUND

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

1) A web client submits the request to the HTTP Listener.

2) The HTTP Request throws an "HTTP:NOT_FOUND" error, execution halts.

3) The On Error Propagate error Handler handles the error. In this case ,HTTP:NOT_FOUND error ismapped to custom error APP:API_RESOURCE_NOT_FOUND. This error processor sets payload to APP:API_RESOURCE_NOT_FOUND.

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

Reference Diagram:

Diagram Description automatically generated with medium confidence

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

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 String is not blank.

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

Here’s specifically what is happening here:

1) Payload is successfully set to “Start”

2) The Is Blank String validator createsan 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

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

Choice router finds the FIRST true condition, then distribute the event to the ONE matched route.

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

* 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 wayyou 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:

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

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

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.

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

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 anddo not 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:

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.

This question validates you knowledge on Batch Processing. Before we analyze the question , lets revise a bit about batchfilters.

Batch Filters

You can apply one or more filters as attributes to any number of batch steps.Imagine a batch job whose first batch step checks if a Salesforce contact exists for a record, and a second batch step that updates each existing Salesforce contact with new information. You can apply a filter to the second batch step to ensure it only processes records that didn’t fail during the first batch step.By having batch steps accept only some records for processing, you streamline the batch job sothe Mule runtime engine can focus only on the relevant data for a particular batch step.

A batch step uses two attributes to filter records:

acceptExpression

acceptPolicy

Each batch step can accept one acceptExpression and one acceptPolicy attributes to filter records.

Use the acceptExpression attribute to process only records that evaluate to true; if the record evaluates to false, the batch step skips the record and sends it to the next one. In other words, the records with an accept expression that resolves to false are the ones that Mule filters out.

The example below filters out all records where the age is less than 21; the batch step does not process those records.

21]">

...

Mule Ref Doc : Refining Batch StepsProcessing | MuleSoft Documentation

As we are clear with above concepts , now lets understand this solution step by step.

1) Batch Step (Less than 50)

Accept expression for this batch step is less than 50. Hence elements which will go in this batch step are amount value 40 and 2. Hence output of logger in first batch step is

{amount=140}

{amount=102}

2) Batch Step (Greater than 20)

Accept condition for this batch step is greater than 20. Note that input amount values for this batch step are 100 , 140 and102 (last two values have been updated in batch step less than 50)

As all values satisfy this condition out put of second logger is

{step2amount=100}

{step2amount=140}

{step2amount=102}

Hence correct answer to this question is

{amount=140}

{amount=102}

{step2amount=100}

{step2amount=140}

{step2amount=102}

2) Batch Step (Greater than 20)

Accept condition for this batch step is greater than 20. Note that input amount values for this batch step are 100 , 140 and 102 (last two values have been updated inbatch step less than 50)

As all values satisfy this condition out put of second logger is

{step2amount=100}

{step2amount=140}

{step2amount=102}

Hence correct answer to this question is

{amount=140}

{amount=102}

{step2amount=100}

{step2amount=140}

{step2amount=102}

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

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

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:

Its primary function is to design and develop fully functional Mule applications in a hosted development environment.

* When a client application is registered in Anypoint Platform, a pair of credentials consisting of a client ID and clientsecret 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 clientapplication for the API proxy

Correct answer is System layer

System APIs provide a means for insulating the data consumers from the complexity or changes to the underlying backend systems.

MuleSoft recommends three-layered approach to API-led connectivity, highlighting the three layers:

* System APIs

* Process APIs

* Experience APIs

System APIs are the core systems of record underlying core systems of record (e.g. ERPs, key customer and billing systems, databases, etc.). Process APIs allow you to define a common process which the organization can share, and these APIs perform specific functions, provide access to non-central data, and may be built by either Central IT or Line of Business IT. And finally, the Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source.

The three-layered structure allows for a seamless flow of data from systems of record to new experiences, and allows for reusability of assets rather than point to point connections. This approach provides a distributed and tailored approach to architecture, greater flexibility through loose coupling, and deeper operational visibility into what is being built.

Diagram Description automatically generated

Logs would look like:

INFO 2021-06-09 19:14:56,039[[MuleRuntime].uber.06: [validationtest].batch-job-validationtestBatch_Job-work-manager @6de10f3e] [processor:validationtestFlow/processors/1/route/0/route/0/aggregator/processors/0; event: bfb751e1-9939-11eb-9f69-02053763653a] org.mule.runtime.core.internal.processor.LoggerMessageProcessor:

[

“\”A\””,

“\”C\””,

“\”D\””

]

—-

INFO 2021-06-09 19:15:02,486 [[MuleRuntime].uber.06: [validationtest].batch-job-validationtestBatch_Job-work-manager @6de10f3e] [processor: validationtestFlow/processors/1/route/0/route/0/aggregator/processors/0; event: bfb751e1-9939-11eb-9f69-02053763653a] org.mule.runtime.core.internal.processor.LoggerMessageProcessor: [

“\”E\””

]

Batch aggregator value is 3. Hence in first time it will print [“A”, “C”, “D”] and in next iteration it will print [ “E” ]

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

Correct answer is [ “E” ]

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 :

The correct answer is To avoid duplicate processing of records in a database.

If a watermark column is provided, the values taken from that column are used to filter the contents of the next poll, so that only rows with a greater watermark value are returned. If an ID column is provided, this component automatically verifies that the same row is not picked twice by concurrent polls.

Mule doc reference :

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

Correct answer is as below. Attributes in the incoming xml payload are always accessed using @.Similarly *item is requiredas we have multiple items in the request

%dw 2.0

output application/csv

---

payload.sale.*item map ((value, index) -> {

index: index,

sale: value.@saleId,

itemName: value.desc,

itemPrice: (value.quantity) * (value.price),

item: value.@itemId

} )

QUESTIONNO: 96

Refer to the exhibits.

The main flow contains a Flow Reference to the child flow.

A web client sends a GET request to the main flow's HTTP Listener that includes a make query parameter.

What values are accessible in the child flow?

A. payload

B.payload

make query param

C. payload

model var

D. payload

make query param model var

Answer: D

MuleSoft Doc Ref :

Stepsto 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

Correct answer isArray.

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 ]

Correct answer is MAJOR

MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards compatible manner, and PATCH version when you make backwards compatible bug fixes.

For details refer to this documentation :

Correct answer is

%dw 2.0

output application/json

import modules::Utility

---

Utility::encryptString( "John Smith" )

DataWeave 2.0 functions are packaged in modules. Before you begin, note that DataWeave 2.0 is for Mule 4apps. For Mule 3 apps, refer to DataWeave Operators in the Mule 3.9 documentation. For other Mule versions, you can use the version selector for the Mule Runtime table of contents.

Functions in the Core (dw::Core) module are imported automatically into your DataWeave scripts. To use other 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:

import dw::core::Strings

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

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. For example, this import directive does not identify any functions to import from the String module, so it calls the pluralize function like this: Strings::pluralize("box").

Transform

%dw 2.0

import dw::core::Strings

output application/json

---

{ 'plural': Strings::pluralize("box") }

vars: Keyword for accessing a variable, for example, through aDataWeave expression in a Mule component, such as the Logger, or from an Input or Output parameter of an operation. If the name of your variable is myVar, you can access it like this: vars.myVar

Hence correct answer is Account Type: #[vars.accountType]

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 8 as events are processed in parallel in case of scatter gather router

Correct answer is Save the payload from the Database SELECT operation to a variable

Response from HTTP requestwill override the payload and hence response of database SELECT can be lost. Best way to preserve is to assign payload of first operation to variable using TransformMessage.

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

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

lookup(String,Any, Number)

This function enables you to execute a flow within a Mule app and retrieve the resulting payload.

It works in Mule apps that are running on Mule Runtime version 4.1.4 and later.

Similar to the Flow Reference component (recommended), the lookup function enables you to execute another flow within your app and to retrieve the resulting payload. It takes the flow’s name and an input payload as parameters. For example, lookup("anotherFlow", payload) executes a flow named anotherFlow.

Correct answeris

lookup( "createCustomerObject", {first: "Aice, last: "Green"})

MuleSoft Documentation Reference :

APIKIt Creates a separate flow for each HTTP method

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

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

Option 1 is the correct syntax

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.

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

Correct answer is Request access to the API in Anypoint Exchange. This way we can get clientId and Client secret which we can use to access the API

*Batch scope has filter criteria which says paylod mod 2 = 0 whch means only 2, 4 and 6 will be in batch scope.

* So payload for each of these will be incremented by 10.

* Aggregator has batch size defined as 2. So it will process in batch of two records.

* Hence option 3 is correct answer.

[20,40]

[60]

Behavior with aggregator configured with fixed size

In this scenario, the batch step sends the processed records to an aggregator, which starts processing the records and buffering them until the configuredaggregator’s size is reached. After that, the aggregator sends the aggregated records to the stepping queue.

Diagram Description automatically generated

The batch job builds record blocks of the configured block size and sends them to their corresponding batch step for processing. Each batch stepreceives one or more record blocks and starts processing them in parallel. After the batch step processes a record, the batch step sends the record to the aggregator for further processing. The aggregator continues processing records until the number of aggregated records reaches the configured aggregator’s size.

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

QUESTIONNO: 219

A Mule project contains a DataWeave module file WebStore dvA that defines a function named loginUser The module file is located in the projects src/main/resources/libs/dw folder

What is correct DataWeave code to import all of the WebStore.dwl file's functions and then call the loginUser function for the login "cindy.park@example.com"?

A)

B)

C)

D)

A. Option A

B. Option B

C. Option C

D. Option D

Answer: D

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

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