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

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

To compare, DataWeave syntax is #[payload == "FR"].

In this case only one = is used so it will give syntax error.

Hence the correct answer is A dataweave syntax error

Application properties can be defined in .yaml or in .properties file.

MuleSoft Doc Ref : https://docs.mulesoft.com/mule-runtime/4.3/configuring-properties#supported_files

String is the correct answer as XML is of an Object type String

Correct answer is

%dw 2.0

output application/json

import modules::Utility

---

Utility::encryptString( "John Smith" )

DataWeave 2.0 functions are packaged in modules. Before you begin, note that DataWeave 2.0 is for Mule 4 apps. For Mule 3 apps, refer to DataWeave Operators in the Mule 3.9 documentation. For other Mule versions, you can use the version selector for the Mule Runtime table of contents.

Functions in the Core (dw::Core) module are imported automatically into your DataWeave scripts. To use other modules, you need to import the module or functions you want to use by adding the import directive to the head of your DataWeave script, for example:

import dw::core::Strings

import camelize, capitalize from dw::core::Strings

import * from dw::core::Strings

The way you import a module impacts the way you need to call its functions from a DataWeave script. If the directive does not list specific functions to import or use * from to import all functions from a function module, you need to specify the module when you call the function from your script. For example, this import directive does not identify any functions to import from the String module, so it calls the pluralize function like this: Strings::pluralize("box").

Transform

%dw 2.0

import dw::core::Strings

output application/json

---

{ 'plural': Strings::pluralize("box") }

Correct answer is Publish the API to Anypoint Exchange

Anypoint Exchange makes this possible by making it discoverable in below ways

1) In private exchange for internal developers

2) In a public portal for external developers/clients

Here is diagram created by me to help you understand sequence:

Diagram Description automatically generated

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. In this case as per RAML specification data is expected in application/json and in request Content-Type is set as "text/plain" which is incorrect. Hence solution is set the request Content-Type header to application/json

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/415

API portal are created by API Exchange and cannot be created by Design Center

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:

Diagram Description automatically generated