Free and Premium Salesforce Salesforce-MuleSoft-Developer-I Dumps Questions Answers

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

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

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

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:

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 :

Correct answer is async sub flow. Rest are valid flows in Mule.

Sub flow is always synchronous.

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 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 process layer as all the orchestration and transformation logic should be in process layer as per Mulesoft's recommended approach for API led connectivity.

API-led connectivity is a methodical way to connect data to applications through reusable and purposeful APIs. These APIs are developed to play a specific role – unlocking data from systems, composing data into processes, or delivering an experience.

What are the APIs that enable API-led connectivity?

API-led connectivity provides an approach for connecting and exposing assets. With this approach, rather than connecting things point-to-point, every asset becomes a managed API – a modern API, which makes it discoverable through self-service without losing control.

The APIs used in an API-led approach to connectivity fall into three categories:

System APIs – these usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. Once built, many users, can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects.

Process APIs – These APIs interact with and shape data within a single system or across systems (breaking down data silos) and are created here without a dependence on the source systems from which that data originates, as well as the target channels through which that data is delivered.

Experience APIs – 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, rather than setting up separate point-to-point integrations for each channel. An Experience API is usually created with API-first design principles where the API is designed for the specific user experience in mind.

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

APIKIt Creates a separate flow for each HTTP method

In General > Request > Query Parameters, click the plus 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

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

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

* 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

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 :

Option 1 is the correct syntax

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 :

PUT replaces the original version of the resource, whereas the PATCH method supplies a set of instructions to modify the resource

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

MuleSoft Documentation Reference :

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)

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

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

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

Graphical user interface Description automatically generated

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

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 Save the payload from the Database SELECT operation to a variable

Response from HTTP request will 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.

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 scope which 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 Reference calls 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 On Error 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 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 :

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

Correct answer is as below as it follows the correct syntax.

• http:
• basepath: "api"
• host : "localhost"
• port : "8081"

Mule Doc Reference :

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 : 

The List operation returns an array of messages in which: Each message holds the file’s content in its payload. The file’s attributes section carries the file’s metadata (such as name, creation time, and size). The payload is empty if the element is a folder.

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

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 each element in the array as a key/value pair

Correct answer is Anypoint Visualizer

MuleSoft Doc Ref :

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

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 the default route executes. Hence only Route1 will be executed as it is the first expression. hence output of logger is Route1.

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

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

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

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

* 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 configured aggregator’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 step receives 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 A global element

When we create a configuration file , that file needs to added as Global Configuration file in Global element. A global element is a reusable object containing parameters that any number of elements in a flow can share. You reference a global element from Anypoint Connectors or components in your Mule application

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 !

* RAML file contains lot of information that could be considered as "not API-describing". Sort of "economy-class" members.

Equally important, but not necessarily part of the main RAML file.

* Through !includes, RAML allows us to build file-distributed API definitions, which is not only useful to encourage code reuse but also improves readability.

* We can create RAML fragments with such code and then include them in main RAML project using !include like:

types:

Book: !include bookDataType.raml and

examples:

input: !include bookExample.raml

* Additionally for

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

Correct Answer: D

Setting Breakpoints

To set breakpoints, right-click a building block, then select Toggle Breakpoint.

Studio applies a red dot to the building block’s icon on the canvas.

When you run your application in Debug mode, Studio stops the flow execution at the breakpoint you have set, allowing you to check the Mule Event content in the Mule Debugger View.

Mule Ref Doc : Setting Breakpoints | MuleSoft Documentation

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

The First Successful router iterates through a list of configured processing routes until one of the routes executes successfully. This is sequential execution. In all other options mentioned in the question ,we can achieve parallel execution.

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 

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

account/{accountId}/*: matches all path requests different from main-contact, such as  , and save mulesoft as the value of accountId.

Mule Ref Doc : 

URI parameter (Path Param) is basically used to identify a specific resource or resources . For eg : the URL to get employee details on the basis of employeeID will be GET /employees/{employeeID} where employees is resource and {employeeID} is URI parameter. Hence option 1is the correct answer