Mulesoft MCD-Level-1 Exam Questions

A Mule application contains two HTTP Listeners, each configured for different API
endpoints: http://acme.com/apis/orders and http: //acme .com/a pis/customers.
What base path value should be set in an HTT? Listener config element so that it can be
used to configure both HTTP Listeners?

A.

/apis/?

B.

/apis/

C.

/apis/orders|customers

D.

/apis/*

D.

/apis/*

A Batch Job scope has five batch steps. An event processor throws an error in the second batch step because the input data is incomplete. What is the default behavior of the batch job after the error is thrown?

A. All processing of the batch job stops.

B. Event processing continues to the next batch step.

C. Error is ignored

D. Batch is retried

A. All processing of the batch job stops.

Explanation:
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.

Refer to the exhibit.

What is the response to a web client request tohttp://localhost:8081?

A.

After

B.

before

C.

Validation Error

D.

null

C.

Validation Error

Refer to the exhibits.

Client sends the request to ClientRequestFlow which calls ShippingFlow using HTTP Request activity.
During E2E testing it is found that that HTTP:METHOD_NOT_ALLOWED error is thrown whenever client sends request to this flow.
What attribute you would change in ClientRequestFlow to make this implementation work successfully?

A. Change the method attribute value to "*’’

B. Change the path attribute value to "/api/ship"

C. Change the allowed method attributes value to "POST"

D. Change the protocol attribute value to "HTTPS"

C. Change the allowed method attributes value to "POST"

Explanation:
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)

Refer to the exhibits.

A Mule application contains a Choice router. What is logged when the flow completes?

A.

EU

B.

US

C.

"REGION"

D.

["US", "EU"]

B.

US

What is the trait name you would use for specifying client credentials in RAML?

A. headers

B. client-id

C. client-id-required

D. cannot be specified in RAML

C. client-id-required

Explanation:
client-id-required enforces clients to add client_id and client_secret.
Please refer to below steps.
Add a section called traits: at the root level to define query parameters:
•traits:
- client-id-required:
queryParameters:
client_id:
type: string
client_secret:
type: string
2) Reference the trait in each of the methods to specify that each of the methods require these query parameters. After each method in the RAML file, add is:
[client-id-required]. For example:
/users:
get:
is: [client-id-required]
description: Gets a list of JSONPlaceholder users.

Refer to the exhibits The Mule application does NOT define any global error handlers.

A web client sends a POST request to the Multi application with this input payload The File Write operation throws a FILECONNECTIVITY error. What response message is returned to the web client?

A. "ORDER NOT_CREATED"

B. "OTHER ERROR"

C. "File written"

D. "FILECONNECTIVITY"

A. "ORDER NOT_CREATED"

A web client submits a request to http://localhost:8081?accountType=personal. The query
parameter is captured using a Set Variable transformer to a variable named accountType.
What is the correct DataWeave expression to log accountType?

A.

Account Type: #[flowVars.accountType]

B.

Account Type: #[message.inboundProperties.accountType]

C.

Account Type: # [attributes.accountType]

D.

Account Type: #[vars.accountType]

D.

Account Type: #[vars.accountType]