Free SALESFORCE-MULESOFT-DEVELOPER-I Exam Dumps Preview

To compare, DataWeave syntax is #[payload == "FR"].
In this case only one = is used so it will give syntax error.
Hence the correct answer is A dataweave syntax error

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

The path of an HTTP listener can be static, which requires exact matches, or feature placeholders.
Placeholders can be wildcards (*), which match against anything they are compared to, or parameters ({param}), which not only match against anything but also capture those values on a URI parameters map.
Take the following example paths for three listeners using a configuration that establishes api/v1 as the base path: account/mulesoft/main-contact: only match the exact path request
http://awesome-company.com/api/v1/account/mulesoft/main-contact
account/{accountId}/main-contact: matches all path requests structured
similarly, such as http://awesome-company.com/api/v1/account/salesforce/main-contact, and save salesforce as the value of accountId. account/{accountId}/*: matches all path requests different from main-
contact, such as http://awesome-company.com/api/v1/account/mulesoft/users, and save mulesoft as the value of accountId.
Mule Ref Doc :
https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#paths

In this case both the flows can start without any error and requests can be received on both ports. Flow names httpListener1 can call other flow using HTTP request without any issues.
Hence correct answer is The mule application start successfully
Web client requests can be received at URI on port 2222 and on port 3333.

Lets check why other options are incorrect 1) The mule application fails to start. There is URL path conflict because both HTTP Listeners are
configured with same path ---- This is incorrect as port value is different in both listeners 2) The mule application start successfully. Web client requests can only be received at URI on port 2222
but not on port 3333 --- This is incorrect as there is no reason for not receiving requests on port 3333 3) The mule application fails to start because of the port binding conflict as HTTP request also use same
port i.e. 3333 --- Port binding conflict will not happen in this case. It would have if both listener configurations would have been on same port . But that is not the case here.
Mule Ref Doc : HTTP Listener Reference - Mule 4 | MuleSoft Documentation

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.

WSDL is used to define the contract in case of SOAP . RAML/OAS is used to REST services

DataWeave is the MuleSoft expression language for accessing and transforming data that travels through a Mule app. DataWeave is tightly integrated with the Mule runtime engine, which runs the scripts and expressions in your Mule app.
References:
https://docs.mulesoft.com/mule-runtime/4.3/dataweave

Correct answer is Publish the API to Anypoint Exchange Anypoint Exchange makes this possible by making it discoverable in below ways 1) In private exchange for internal developers
2) In a public portal for external developers/clients
Here is diagram created by me to help you understand sequence:

This helps CloudHub to dynamically allocates a port at deployment time. MuleSoft Doc Ref :
https://docs.mulesoft.com/mule-runtime/4.3/deploy-to-cloudhub#prerequisites

References:
https://docs.mulesoft.com/runtime-manager/developing-applications-for-cloudhub

Correct answer is APP: API RESOURCE NOT FOUND
-------------------------------------------------------------------------------------------------------------------------
-------------------------- 1) A web client submits the request to the HTTP Listener.
2) The HTTP Request throws an "HTTP:NOT_FOUND" error, execution halts.
3) The On Error Propagate error Handler handles the error. In this case ,HTTP:NOT_FOUND error is mapped to custom error
APP:API_RESOURCE_NOT_FOUND. This error processor sets payload to APP:API_RESOURCE_NOT_FOUND.
4) "APP:API_RESOURCE_NOT_FOUND. " is the error message returned to the requestor in the body of the HTTP request with HTTP Status Code: 500 Reference Diagram:

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

Correct answer is Change the method attributes value to "POST".
It can be fixed in either of the two ways as below.
1) Changing method attribute to POST in ClientRequestFlow 2) Setting allowedMethods as PUT in ShippingFlow (but doesn't fit as question mentions about changing
ClientRequestFlow)

Correct answer is A global element When we create a configuration file , that file needs to added as Global Configuration file in Global element. A global element is a reusable object containing parameters that any number of elements in a flow can share. You reference a global element from Anypoint Connectors or components in your Mule application

MuleSoft Doc Ref :
https://docs.mulesoft.com/api-manager/2.x/policy-mule3-tutorial-manage-an-api#to-add-the-tier
Steps to create SLA Tier are as follows:
1) In API Manager, in API Administration, click a version.
2) Check that the API supports resource-level policies: On the API version details page, in Status, click
Configure Endpoint, and check that Type is RAML.
3) Choose the SLA Tiers, and click Add SLA Tier. Set up limit on SLA tier

Correct answer is Add required headers to RAML specification and redeploy new API proxy MuleSoft Doc
Ref :
https://docs.mulesoft.com/api-manager/2.x/tutorial-manage-an-api
Steps are as below : Add the Required RAML Snippet SLA-based rate limiting requires adding a RAML or OAS snippet to your API. This procedure demonstrates adding a RAML snippet.
Specify the client ID and secret as query parameters.
Add a section called traits: at the RAML root level to define query parameters: traits:
- client-id-required:
queryParameters:
client_id:
type: string
client_secret:
type: string
Add the client-id-required trait to every method that requires these query parameters:
/users:
get:
is: [client-id-required] description: Gets a list of JSONPlaceholder users.

Step 2 : Add the SLA Tier in API Manager Step 3 : Apply the policy and redeploy
References:
https://docs.mulesoft.com/api-manager/2.x/tutorial-manage-an-api

In case of an error , batch job completes in flight steps and stops further processing. MuleSoft Doc Ref : Handling Errors During Batch Job | MuleSoft Documentation The default is all processing will stop but we can change it by Max Failed Record field. General -> Max Failed Records: Mule has three options for
handling a record-level error: Finish processing, Continue processing and Continue processing until the batch job accumulates a maximum number of failed records. This behavior can be controlled by Max Failed Records.
The default value is Zero which corresponds to Finish processing.
The value -1, corresponds to Continue processing.
The value +ve integer, corresponds to Continue processing until the batch job accumulates a maximum number of failed records

Option 1 is the only correct choice due to two reasons. 1) Concatenation is always with ++ sign and not with + sign which makes option 2 and 3 wrong 2) hearders can be accessed with attributes. headers and not with only headers which makes option 4 incorrect

Setting Breakpoints
To set breakpoints, right-click a building block, then select Toggle Breakpoint. Studio applies a red dot to the building block's icon on the canvas. When you run your application in Debug mode, Studio stops the flow execution at the breakpoint you have set, allowing you to check the Mule Event content in the Mule Debugger View.
Mule Ref Doc : Setting Breakpoints | MuleSoft Documentation

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

Key thing to note here is that any changes made to payload in for each loop are not available outside for each scope where as variable value updated in for each loop is visible out side for each loop too.
In this example , sequence can be described as follows 1) Payload is set to the value [5, 10, 15, 20]
2) Variable is set to the value of 1 3) For each loop is executed four times and in each loop payload value is updated to append "Req" and
variable is count is increased by 1 4) Once control comes out of for each , payload changes made within for each are not visible. Hence
payload at this point of time is equal to payload available before entering for each loop which was [5, 10, 15, 20]. Similarly variable value updated in for each loop is also available outside hence variable value is 5 as it was updated in loop.
5) Hence correct answer is [[5, 10, 15, 20], 5]
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.
For non-Java collections, such as XML or JSON, use a DataWeave expression to split data. Use the Collection field for this purpose.

Correct answer is as below as concatenation operation works only with string and not with the objects. In this case payload is object.

"You called the function '++' with these arguments:
1: String ("INFO")
2: Object ({student: {name: "Anay" as String {class: "java.lang.String"},age

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

Center for Enablement is correct answer .It is a cross-functional team typically staffed with members from central IT, line-of-business departments, and digital innovation teams charged with productizing, publishing, and harvesting reusable assets and best practices. In this case , app team would have checked first with Center for Enablement before developing their own API's. Hence could have avoided re-work

Mule applications can be scaled vertically by changing worker size. Mule applications can be scaled horizontally by adding more workers.

By default, Debugger listens for incoming TCP connections on localhost port 6666 You can change this in a project's run configuration.
MuleSoft Doc Ref :
https://docs.mulesoft.com/studio/7.5/visual-debugger-concept