Salesforce Salesforce-MuleSoft-Developer-I - Salesforce Certified MuleSoft Developer (Mule-Dev-201)

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 reusableand 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-ledapproach 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 itsintended 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 ${training.host}

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

How to Configure Properties to Mule 4.X Platform?

1) Go to /src/main/resources project directory.

2) Create aconfiguration file with the name configuration.yaml inside the newly created config folder.

                                           Graphical user interface, application, Word Description automatically generated

3) Go To Project > Global Element > Create > General >select the configuration.yaml file create in step- 2)

                                             Graphical user interface, application Description automatically generated 

4) To verify develop a simple flow with HTTP listener which has above entries. Put the logger that prints the values on console.

                                               Graphical user interface, application Description automatically generated

5) Additional info: Similarly, when you want to access this port in DataWeave you need to use p function

                                              Graphical user interface, text, application, email Description automatically generated

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

In this case as outbound call is made using HTTP: POST /child , all attributes will be replaced by this invocation. Hence query parameter will not be accessible at logger. Hence correct answer is option 2

In this case as outbound call is made using HTTP: POST /child , all attributes will be replacedby this invocation. Hence query parameter will not be accessible at logger.

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

QUESTIONNO: 219

A Mule project contains a DataWeave module file WebStore dvA that defines a function named loginUser The module file is located in the projects src/main/resources/libs/dw folder

What is correct DataWeave code to import all of the WebStore.dwl file's functions and then call the loginUser function for the login "cindy.park@example.com"?

A)

B)

C)

D)

A. Option A

B. Option B

C. Option C

D. Option D

Answer: D

Correct answer is an operation. For each method of the RAML specification , REST connect module provide an operation.

Please refer to the belowscreenshot.

*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 configuredaggregator’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 stepreceives 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.

https://docs.mulesoft.com/mule-runtime/4.3/batch-processing-concept