Pass the Salesforce Salesforce MuleSoft Salesforce-MuleSoft-Developer-I Questions and answers with CertsForce

Debugger can be used to debug applications to see event data movine from one flow to other

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

Note that private flow has error scope defined as On Error Continue . So when error occurs in private flow , it is handled by this On Error Continue scopewhich sends success response back to main flow and does not throw back an error. So main continues normally and payload is set to Success - main flow.

Hence correct answer is Success - main flow

1) HTTP listener received request

2) The Flow Referencecalls the child flow

3) The Is Number validator creates an Error Object because the payload isn’t an integer. Child Flow execution stops

#[error.description] = “payload is not a valid INTEGER value”

#[error.errorType] = VALIDATION:INVALID_NUMBER

4) The OnError Continue handles the errorThe payload is set to “Error – Sub Flow”

5) “Error – Sub Flow” is returned to the main flow as if the child flow was a success. The Set Payload is executed. The payload is reset to “Success – Finished Main Flow”

6) “Success– Main Flow” is returned to the requestor in the body of the HTTP request. HTTP Status Code: 200

As you can see, in the above example, because the error was caught by an On Error Continue scope in the child flow (RED in, GREEN out) when the Mule Message returns to the parent flow, the parent flow knows none-the-different that there was a failure because the on error continue returns a 200 success message. Note that because, to the mainFlow, the childFlow appeared to succeed, the processing of mainFlow resumed after the flow reference.

A picture containing timeline Description automatically generated

Cloudhub exposeservices on port 8081 and override value in http.port with this one .

Sample log in Runtime Manager is below

21:15:53.148 08/08/2021 Worker-0 ArtifactDeployer.start.01 INFO

Listening for connections on 'http://0.0.0.0:8081 '

Anypoint Exchange provided a way to publish , share and search API's.

MuleSoft Doc Ref : https://docs.mulesoft.com/exchange/

Transform Message Add write_date is coverting payload in JSON format and same JSON payload is avaialble to file write processor. However, if the payload is a different format (for example, not CSV) , you can place the transformation inside the Write operation to generate content that will be written without producing a side effect on the message in transit. This is not done in this case. By default, the connector writes whatever is in the message payload. Hence JSON payload will be written to file.

Allowed methods is an optional configuration. If nothing is specified then all HTTP methods are supported.

Rest all are mandatory.

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

Correct answer is Patients from year 2021.

The thing to note here is that year is not a query parameter and not the uri parameter. Hence it will filter all the patients and return the ones for whom year is 2021