MuleSoft Updated MCD-Level-1 Exam Questions and Answers by arnold

Correct Answer: Response body: "Error" Default response status code: 200.

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

1) Payload is successfully set to “Success – Started Flow”

2) When HTTP Request throws an error, execution halts

#[error.description] = “ABC"

#[error.errorType] = "XYZ"

3) The On Error Continue scope handles the error. When On Error Continue scope is invoked, all the processors in error block are executed and success response is sent back to the client with payload which is set in error flow. In this case payload is set to "Error" value in error block.

4) “Error” is returned to the requestor in the body of the HTTP request with HTTP Status Code: 200 as On error continue always sends success error code.

Reference Diagram:

Timeline Description automatically generated with medium confidence

* RAML file contains lot of information that could be considered as "not API-describing". Sort of "economy-class" members.

Equally important, but not necessarily part of the main RAML file.

* Through !includes, RAML allows us to build file-distributed API definitions, which is not only useful to encourage code reuse but also improves readability.

* We can create RAML fragments with such code and then include them in main RAML project using !include like:

types:

Book: !include bookDataType.raml and

examples:

input: !include bookExample.raml

* Additionally for

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

Correct Answer: D

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 is URL 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 not happen 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 : HTTP Listener Reference - Mule 4 | MuleSoft Documentation

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)