QUESTION: 49

Refer to the exhibit. The main flow contains an HTTP Request in the middle of the flow. The HTTP Listeners and HTTP request use default configurations.
What values are accessible to the Logger at the end of the flow after a web client submit request to http://local:801/order?color=red?

payload
payload quantity var
payload color query param
payload quantity var color query param

Answer(s): B

Explanation:

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.

Reveal Solution Next Question

QUESTION: 50

Refer to the exhibit.

In the execution of the Scatter_Gather, the flow1 route completes after 10 seconds and the flow2 route completes after 20 seconds.
How many seconds does it take for the Scatter_Gather to complete?

0
10
20
30

Answer(s): C

Reveal Solution Next Question

QUESTION: 51

To avoid hard-coding values, a flow uses some property placeholders and the corresponding values are stored in a configuration file.
Where does the configuration file's location need to be specified in the Mule application?

The pom.xml file
A global element
The mule-art if act .json file
a flow attribute

Answer(s): B

Explanation:

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

Reveal Solution Next Question

QUESTION: 52

Refer to the exhibit.

What is the correct syntax to add an employee ID as a URI parameter in an HTTP Listener path?

(employeelD)
${emp!oyeelD}
{employeelD}
# [employeelD]

Answer(s): C

Explanation:

Paths
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.

Reference:

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

Reveal Solution Next Question

Free Salesforce-MuleSoft-Developer-I Exam Braindumps (page: 14)

QUESTION: 49

Explanation:

QUESTION: 50

QUESTION: 51

Explanation:

QUESTION: 52

Explanation:

Reference:

Salesforce-MuleSoft-Developer-I Exam Discussions & Posts