Free Practice Questions for MuleSoft MCD-Level-1 Exam

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

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.

Correct answer is Save the payload from the Database SELECT operation to a variable

Response from HTTP request will override the payload and hence response of database SELECT can be lost. Best way to preserve is to assign payload of first operation to variable using TransformMessage.

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

API Exchange creates REST conenctor automtaically once API is published. Hence correct answer is Publish the API specification to Any point Exchange

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") }

Gold is not valid category for connector types.

MuleSoft Doc Ref : https://docs.mulesoft.co m/mule-runtime/3.7/anypoint-connectors#connector-support-categories

Text Description automatically generated with medium confidence