Salesforce-MuleSoft-Developer-I Sample Questions Answers

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 do 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: List all Foos matching query criteria, if provided;
• otherwise list all Foos
• 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:

Debugger can be used to debug applications to see event data movine from one flow to other

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.

Cloudhub expose services 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 '

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

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

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.

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

Correct answer is Anypoint Visualizer

MuleSoft Doc Ref : https://docs.mulesoft.com/visualizer/

Anypoint Visualizer provides a real-time, graphical representation of the APIs, and Mule applications that are running and discoverable. It also displays third-party systems that are invoked by a Mule API, proxy, or application within your application network. The data displayed in the graph is dynamically updated and does not require prior configuration. Additionally, the data displayed is secure, as only users with the proper permissions can view the application network graph.

Diagram Description automatically generated

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

Scatter-Gather Router

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

Correct answer is Creates a mock service for an API

API Notebook is an open source, shareable web application for API documentation, interactive API tutorial and example generatation, and a client for your API endpoints. Using API Notebook, you can make requests and quickly transform the responses into readable format. However it cannot be used to mock service for an API.

MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/1.x/api-notebook-concept

This is a trick question.

You can call only 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

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

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

• ...

Mule Ref Doc : Refining Batch Steps Processing | 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 and 102 (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 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}

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

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

Correct answer is Patients from year 2021.

The thing to note here is that year is not a query parameter and not the uri parameter. Hence it will filter all the patients and return the ones for whom year is 2021

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

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

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

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

The default value is Zero which corresponds to Finish processing.

The value -1, corresponds to Continue processing.

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

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

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 do 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: List all Foos matching query criteria, if provided;
• otherwise list all Foos
• 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:

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

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

Option 3 is the only corect answer as it concatenates payload with String.

Below option wont work.

#["The payload is " ++ payload]

Concatenation function expects both arguments to be string. As the question says payload is json object , this will throw error while running it. You can try this in Anypoint Studio and you will get the same result which I mentioned.

hence correct answer is

The payload is: #[payload]

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

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

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

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

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

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

1) Changing method attribute to POST in ClientRequestFlow

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

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

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

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

Database always return rows as an array.

Array is the correct answer

Correct answer is API manager