MuleSoft Certified Developer - Level 1 (Mule 4) MCD-LEVEL-1 Dumps in PDF

Explanation:

MuleSoft Documentation Reference : https://docs.mulesoft.com/db-connector/1.9/database- connector-select

Explanation:

Mule event is correct answer. Mule event has two parts which are as follows

1) Message (which contains payload and attributes like headers and query/uri parameters
2) Variables

Explanation:

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

Explanation:

Explanation:

In this case three configurations will be required each for port 8000, 6000 and 7000. There would be three global elements defined for HTTP connections. Each HTTP connection will have host and port. One example shown below with host as localhost and port 6000



To use an HTTP listener, you need to declare a configuration with a corresponding connection. This declaration establishes the HTTP server that will listen to requests. Additionally, you can configure a base path that applies to all listeners using the configuration. <http:listener-config name="HTTP_Listener_config" basePath="api/v1"> <http:listener-connection host="0.0.0.0" port="8081" />

</http:listener-config>

https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#http-listener-configuration

Explanation:

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

Explanation:

lookup(String, Any, Number)
This function enables you to execute a flow within a Mule app and retrieve the resulting payload. It works in Mule apps that are running on Mule Runtime version 4.1.4 and later. Similar to the Flow Reference component (recommended), the lookup function enables you to execute another flow within your app and to retrieve the resulting payload. It takes the flow's name and an input payload as parameters. For example, lookup("anotherFlow", payload) executes a flow named anotherFlow.
Correct answer is lookup( "createCustomerObject", {first: "Aice, last: "Green"}) MuleSoft Documentation Reference : https://docs.mulesoft.com/mule-runtime/4.3/dw-mule-

functions-lookup