Mulesoft MCD-Level-1 Exam Questions

What should this endpoint return considering the API is build using standard practices?
http://dev.acme.com/api/patients?year=2021

A. Patient with id 2021

B. Patients from year 2021

C. No patients

D. All patients

B. Patients from year 2021

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

A company has defined two RAML fragments, Book Data Type and Book Example to be used in APIs. What would be valid RAML to use these fragments?

A. 1. #%RAML 1.0
2. title: Books
3. types:
4. Book: ABC/Examples/bookDataType.raml
5. /books:
6. post:
7. body:
8. application/json:
9. type: Book
10. examples:
11. input: ABC/Examples/bookExample.raml
12. responses:
13. 201:
14. body:
15. application/json:
16. example:
17. message: Book added

B. 1.#%RAML 1.0
2.title: Books
3.Book: !include bookDataType.raml
4./books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: !include bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added

C. 1.#%RAML 1.0
2.title: Books
3.Book: bookDataType.raml
4./books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added

D. 1.#%RAML 1.0
2.title: Books 3.Book: bookDataType.raml
4./books:
5. post:
6. body:
7. application/json:
8. type: Book
9. examples:
10. input: bookExample.raml
11. responses:
12. 201:
13. body:
14. application/json:
15. example:
16. message: Book added

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

Refer to the exhibits.

A. 1. 1. {
2. 2. orderkey: "payload.order",
3. 3. addresskey: "vars.address"
4. 4. }

B. 1. 1. {
2. 2. orderkey: "attributes.shippingaddress.order",
3. 3. addresskey: "payload"
4. }

C. 1. 1. {
2. 2. orderkey: "payload.order",
3. 3. addresskey: "address"
4. }

D. 1. 1. {
2. 2. orderkey: "attributes.order",
3. 3. addresskey: "vars.address"
4. }

A. 1. 1. {
2. 2. orderkey: "payload.order",
3. 3. addresskey: "vars.address"
4. 4. }

Explanation:
Correct answer is as below. In this case address will be stored in a variable. Hence payload will not be overwritten and will contain order details
{
orderkey: "payload.order",
addresskey: "vars.address"
}

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]

Mule application contains ActiveMQ JMS dependency. Mule application was compiled and run successfully in Anypoint Studio. The mule application must now be exported from Anypoint Studio and shared with other developer. What export options should be selected to create the smallest JAR file that can be imported into other developer's Anypoint Studio and run successfully?

A. Select only Attach Project Sources only

B. Select both Attach Project Sources and Include project modules and dependencies option

C. Select the Include project modules and dependencies option only

D. De-select both Attach Project Sources and Include project modules and dependencies option

A. Select only Attach Project Sources only

Explanation:
Correct answer is Select only Attach Project Sources only.
You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace.
Deselect the Include project modules and dependencies option.
This option skips bundling the actual modules and external dependencies required to run the Mule application in a Mule runtime engine, creating a lightweight JAR file package that does not include any dependencies specified in the Mule application’s pom.xml file.
The generated JAR file is not a functional deployable archive and cannot be deployed to a Mule runtime engine, but instead offers a way to archive only the source files that make up the Mule application. This is the same as using the -lightWeightPackage flag when packaging using the Mule Maven Plugin and is useful if you want to distribute your project to other Studio installations because it only keeps a reference to all its dependencies.
When you import a lightweight package into Studio, all your dependencies are automatically downloaded.

Refer to the exhibits.

The Mule application implements a REST API that accepts GET requests from web clients on the URLs: http://acme com/order/status and http:Vacme.com/customer/status. What path value can be set in the HTTP GE~ event source to accept web client requests from both of these URLs?

A. *[order,customer]/status

B. */status

C. ?[order,customer]/status

D. *status

B. */status

What happens to the attributes of a Mule event in a flow after an outbound HTTP Request is made?

A. Attributes are replaced with new attributes from the HTTP Request response (which might be null)

B. New attributes may be added from the HTTP response headers, but no headers are ever removed

C. Attributes do not change

D. Previous attributes are passed unchanged

A. Attributes are replaced with new attributes from the HTTP Request response (which might be null)

Explanation:
Attributes are replaced with new attributes from the HTTP Request response.
Attributes include everything apart from Payload/body. For ex: Headers, query parameters, URI parameters.
So, when outbound HTTP request is made, new attributes need to pass the outbound HTTP request and old attributes are replaced.
I have created below diagram to make it easy for you to understand:

According to MuleSoft. what is the first step to create a Modern API?

A.

Gather a list of requirements to secure the API

B.

Create an API specification and get feedback from stakeholders

C.

Performance tune and optimize the backend systems and network

D.

Create a prototype of the API implementation

B.

Create an API specification and get feedback from stakeholders