Pass the MuleSoft MuleSoft Certified Developer MCD-Level-1 Questions and answers with CertsForce

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 is responsible 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

Correct answer is as below. Attributes in the incoming xml payload are always accessed using @.Similarly *item is required as we have multiple items in the request

%dw 2.0

output application/csv

---

payload.sale.*item map ((value, index) -> {

index: index,

sale: value.@saleId,

itemName: value.desc,

itemPrice: (value.quantity) * (value.price),

item: value.@itemId

} )

Entire event would be sent to each route in parallel.

Scatter-Gather works as follows :

- The Scatter-Gather component receives a Mule event and sends a reference of this Mule event to each processing route.

- Each of the processing routes starts executing in parallel. After all processors inside a route finish processing, the route returns a Mule event, which can be either the same Mule event without modifications or a new Mule event created by the processors in the route as a result of the modifications applied.

- After all processing routes have finished execution, the Scatter-Gather component creates a new Mule event that combines all resulting Mule events from each route, and then passes the new Mule event to the next component in the flow.

Diagram Description automatically generated

MuleSoft Documentation Reference : https://docs.mulesoft.com/db-connector/1.9/database-connector-select

The HTTP 415 Unsupported Media Type client error response code indicates that the server refuses to accept the request because the payload format is in an unsupported format. The format problem might be due to the request's indicated Content-Type or Content-Encoding , or as a result of inspecting the data directly. As per RAML input is expected in application/xml.

Hence correct answer is Set a request header with the name Content-Type to a

Correct answer is /accounts?account_type=retail&industry=finance

Query parameters are a defined set of parameters attached to the end of a url. They are extensions of the URL that are used to help define specific content or actions based on the data being passed. To append query params to the end of a URL, a ‘?’ Is added followed immediately by a query parameter.

To add multiple parameters, an ‘&’ is added in between each.

Error in validation component will get processed by Processer level On Error Propagate block and then error will be rethrown which will get processed by flow level error handler which will set payload to "Error- main flow". Hence correct answer is Error - main flow

1) Request is received by HTTP listener

2) Try scope gets executed

3) The validator component in the Try scope creates an Error Object because the payload is not null.

4) The On Error Propagate handles the error. The payload is set to “Error – Try scope”

6) “Error – Try scope” is returned to the 'On Error Continue' block. Main flow execution stops. Payload is set to "Error - main flow"

7) “Error - main flow” is returned to the requestor in the body of the HTTP request. HTTP Status Code: 200

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

Reference Diagram though not exactly same, conditions are similar. They will help you answer any new question on error handling in real exam:

Timeline Description automatically generated

https://docs.mulesoft.com/mule-runtime/4.3/on-error-scope-concept#on-error-continue

Correct answer is A global element

Global error handlers are to be created in global element .

Quick note to remember here is Global error handlers come in to picture only when there are no error handlers specified as flow level.

Steps to create Global error handler

1) Click Global Elements to open Global Configuration Elements. Global Elements is located below the Studio canvas

2) In Global Configuration Elements, click Create to open the Choose Global Type dialog

Graphical user interface, text, application, chat or text message Description automatically generated

3) From the dialog, select Global Configuration -→ Configuration, and then click OK to open the Configuration dialog.

Graphical user interface, text, application, email Description automatically generated

4) From the select Configuration dialog, select allErrorHandler for the Default Error Handler field, and click OK.