MuleSoft MCD - Level 1 Practice Test - Questions Answers, Page 15

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 : https://docs.mulesoft.com/mule-runtime/4.1/dataweave-functions

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.

Core (dw::Core) This module contains core DataWeave functions for data transformations. It is automatically imported into any DataWeave script.

Correct answer is 0.1 vCores

MuleSoft Doc Ref : https://docs.mulesoft.com/runtime-manager/cloudhub-architecture#cloudhub-workers

CloudHub Workers

Workers are dedicated instances of Mule runtime engine that run your integration applications on CloudHub. The memory capacity and processing power of a worker depends on how you configure it at the application level.

Worker sizes have different compute, memory, and storage capacities. You can scale workers vertically by selecting one of the available worker sizes:

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

Anypoint Exchange provided a way to publish , share and search API's.

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

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.

Correct answer isAn Object containing all three Mule event Objects

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.

Sample output is as below

MuleSoft Documentation reference : https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept