Free Practice Questions for Salesforce Salesforce-MuleSoft-Developer-I Exam

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

Here’s specifically what is happening here:

1) Payload is successfully set to “Before”

2) Is null validation is used which will pass the message only if payload is null. In this case as payload is not null, it creates an Error Object. Flow execution stops

#[error.description] = “Validation error”

3)Because no error handler is defined, the Mule default error handler handles the error

4) “Validation error” is the error message returned to the requestor in the body of the HTTP request with HTTP Status Code: 500

Reference diagram:

A picture containing timeline Description automatically generated

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

Correct answer is async sub flow. Rest are valid flows in Mule.

Sub flow is always synchronous.

QUESTIONNO: 232

Refer to the exhibit. This RAML fragment defines a Book data type that is used in a RAML API specification.

An API implementation is created for this RAML API specification.

What is valid JSON input for a request from a web client to an implementation of this RAML API specification?

A.

B.

C.

D.

Answer: B

Paths

The pathof 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 capturethose 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

Correct answer is Specify throttling , security and other policies

MuleSoft Doc Ref : https://docs.mulesoft.com/api-manager/2.x/api-gateway-capabilities-mule4

API Gateway isresponsible for below functions.

1) Determine which traffic is authorized

2) Meter the traffic

3) Logs transaction

4) Apply throttling and other policies (Not specifying. These are specified in API Manager)

Graphical user interface, text, application Description automatically generated

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 isURL 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 nothappen 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 : HTTPListener Reference - Mule 4 | MuleSoft Documentation