Free Practice Questions for Salesforce Salesforce-MuleSoft-Developer-I Exam

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 : https://docs.muleso ft.com/mule-runtime/4.3/for-each-scope-concept

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

Keyword to ad function in Dataweave transformation is fun. Hence option 2 and 4 are invalid. Also parameters needs to be passed exactly in same order as defined in function definition. Hence correct answer is'

fun addKV( object: Object, key: String, value: Any) =

object ++ {(key):(value)}

---

addKV ( {"hello': "world"}, "hola", "mundo" )

MuleSoft Documentation Reference : https://docs.mulesoft.com/mule-runtime/4.3/dataweave-functions

DataWeave FunctionDefinition Syntax

To define a function in DataWeave use the following syntax:

fun myFunction(param1, param2, ...) =

The fun keyword starts the definition of a function.

myFunction is the name you define for the function.

Function namesmust be valid identifiers.

(param1, param2, … , paramn) represents the parameters that your function accepts.

You can specify from zero to any number of parameters, separated by commas (,) and enclosed in parentheses.

The = sign marks the beginning of thecode block to execute when the function is called.

represents the actual code that you define for your function.