Salesforce-MuleSoft-Developer-I Exam Dumps - Salesforce MuleSoft Questions and Answers

Correct answer is Attributes.

Query parameters , URI parameters and headers are some of examples which are part of attributes.

Diagram Description automatically generated

Bottom of Form

Top of Form

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

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.

Mule Doc Reference : https://docs.mulesoft.com/mule-runtime/4.3/for-each-scope-concept

Empty array is returned when no rows are matched.

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

Correct answer is

%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 4 apps. 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") }

Flow Reference Component

Flow Reference routes the Mule event to another flow or subflow, 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 Mule event 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
• quantity var
• color query param