MuleSoft MCD-Level-2 Exam Practice Test Instant Access

Question 1

An organization uses CloudHub to deploy all of its applications.

How can a common-global-handler flow be configured so that it can be reused across all of the organization's deployed applications?

Create a Mule plugin project

Create a common-global-error-handler flow inside the plugin project.

Use this plugin as a dependency in all Mute applications.

Import that configuration file in Mute applications.

Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.

CCreate a Mule Plugin project
Create a common-global-error-handler flow inside the plugin project.
Use this plugin as a dependency in all Mule applications
D.
Create a Mule daman project.
Create a common-global-error-handler flow inside the domain project.
Use this domain project as a dependency.

Answer : C

To configure a common-global-handler flow that can be reused across all of the organization's deployed applications, the developer should create a Mule Plugin project, create a common-global-error-handler flow inside the plugin project, and use this plugin as a dependency in all Mule applications. This way, the developer can import the common-global-error-handler flow in any application that needs it and avoid duplicating the error handling logic. Reference: https://docs.mulesoft.com/mule-runtime/4.3/error-handling#global-error-handler

Question 2

Refer to the exhibit.

What is the result if ''Insecure'' selected as part of the HTTP Listener configuration?

AThe HTTP Listener will trust any certificate presented by the HTTP client

BThe HTTP Lister will accept any unauthenticated request

CThe HTTP listener will only accept HTTP requests

DMutual TLS authentication will be enabled between this HTTP Listener and an HTTP client

Answer : C

Based on the exhibit below, if 'Insecure' is selected as part of the HTTP Listener configuration, the HTTP listener will only accept HTTP requests. This means that no TLS context will be configured for this listener and no encryption or authentication will be applied to incoming requests. The protocol attribute of this listener will be set to HTTP instead of HTTPS. Reference: https://docs.mulesoft.com/http-connector/1.6/http-listener-ref#insecure

Question 3

When a client and server are exchanging messages during the mTLS handshake, what is being agreed on during the cipher suite exchange?

AA protocol

BThe TLS version

CAn encryption algorithm

DThe Public key format

Answer : C

A cipher suite is a set of cryptographic algorithms that are used to secure the communication between a client and a server. A cipher suite consists of four components: a key exchange algorithm, an authentication algorithm, an encryption algorithm, and a message authentication code (MAC) algorithm. During the cipher suite exchange, the client and the server agree on which encryption algorithm to use for encrypting and decrypting the data. Reference: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#cipher-suites

Question 4

Which command is used to convert a JKS keystore to PKCS12?

AKeytool-importkeystore --srckeystore keystore p12-srcstoretype PKCS12 --destkeystore keystore.jks --deststoretype JKS

BKeytool-importkeystore --srckeystore keystore p12-srcstoretype JKS --destkeystore keystore.p12 --deststoretype PKCS12

CKeytool-importkeystore --srckeystore keystore jks-srcstoretype JKS --destkeystore keystore.p13 --deststoretype PKCS12

DKeytool-importkeystore --srckeystore keystore jks-srcstoretype PKCS12 --destkeystore keystore.p12 --deststoretype JKS

Answer : B

To convert a JKS keystore to PKCS12, the developer needs to use the keytool-importkeystore command with the following options: -srckeystore keystore.jks -srcstoretype JKS -destkeystore keystore.p12 -deststoretype PKCS12. This command imports all entries from a source JKS keystore (keystore.jks) into a destination PKCS12 keystore (keystore.p12). Reference: https://docs.oracle.com/en/java/javase/11/tools/keytool.html#GUID-5990A2E4-78E3-47B7-AE75-6D1826259549

Question 5

A Mule API receives a JSON payload and updates the target system with the payload. The developer uses JSON schemas to ensure the data is valid.

How can the data be validation before posting to the target system?

AUse a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add:
%dw 2.0
Import.json-moduls

BUsing the DataWeave if Else condition test the values of the payload against the examples included in the schema

CApply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration

DAdd the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema

Answer : D

To validate the data before posting to the target system, the developer should add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema. The JSON module provides a validate-schema operation that validates a JSON payload against a JSON schema and throws an error if the payload is invalid. Reference: https://docs.mulesoft.com/json-module/1.1/json-validate-schema

Question 6

Refer to the exhibit.

What is the result of the Mule Maven Plugin configuration of the value of property its,keystorePassoword in CloudHub 2.0?

ACloudHub encrypts the value

BThe Mule server encrypts the value

CAnypoint Studio secures the value

DRuntime Manager masks the value

Answer : D

The result of the Mule Maven Plugin configuration of the value of property its,keystorePassword in CloudHub 2.0 is that Runtime Manager masks the value. This means that Runtime Manager hides or obscures the value from anyone who views it in Runtime Manager or Anypoint Platform. Reference: https://docs.mulesoft.com/runtime-manager/runtime-manager-agent-for-mule4#properties-tab

Question 7

Which statement is true when using XML SDK for creating custom message processors?

AProperties are fields defined by an end user of the XML SDK component and serve as a global configuration for the entire Mule project in which they are used

BAn XML SDK provides both inbound and outbound operations

COperations can be reused in recursive calls

DAll operations are public

Answer : D

When using XML SDK for creating custom message processors, all operations are public by default and can be used by any Mule application that imports them. There is no way to make an operation private or protected in XML SDK. Reference: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#operations

MuleSoft MCD-Level-2 MuleSoft Certified Developer - Level 2 (Mule 4) Exam Practice Test