Question 1

A Mule API receives a JSON payload and updates the target system with the payload. The developer usesJSON schemas to ensure the data is valid.How can the data be validation before posting to the target system?

Options :

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

B : Using the DataWeave if Else condition test the values of the payload against the examples included inthe schema

C : Apply the JSON Schema policy in API Manager and reference the correct schema in the policyconfiguration

D : Add the JSON module dependency and add the validate-schema operation in the flow, configured toreference the schema

Answer: D

Question 2

A Mule application defines as SSL/TLS keystore properly ‘tis,keystore.keyPassword’’ as secure. How can this property be referenced to access its value within the application?

Options :

A : #{secure::tiskeystore,keyPassowrd}

B : ${secure::tiskeystore,keyPassowrd}

C : ${secure::tiskeystore,keyPassowrd}

D : p{secure::tiskeystore,keyPassowrd}

Answer: B

Question 3

An API has been built to enable scheduling email provider. The front-end system does very little data entryvalidation, and problems have started to appear in the email that go to patients. A validate-customer’’ flow isadded validate the data.What is he expected behavior of the ‘validate-customer’’ flow? MCD-Level-2-page47-image13

Options :

A : If only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised

B : If the email address is invalid, processing continues to see if the appointment data and customer name are also invalid

C : If the appointment date and customer name are invalid, a SCHEDULE:INVALID_APPOINTMENT_DATE error is raised

D : If all of the values are invalid the last validation error is raised:SCHEDULE:INVALID_CUSTOMER_NAME

Answer: A

Question 4

A Mule application for processing orders must log the order ID for every log message output.What is a best practice to enrich every log message with the order ID?

Options :

A : Use flow variables within every logger processor to log the order ID

B : Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern

C : Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector

D : Use the Tracing module to set logging variables with a Mapped Diagnostic Context

Answer: D

Question 5

The HTTP Request operation raises an HTTP CONNECTIVITY error.Which HTTP status code and body are returned to the web client? MCD-Level-2-page47-image9

Options :

A : HTTP Status Code:200.Body ‘Error in processing your request

B : HTTP Status Code:500.Body ‘The HTTP CONNECTIVITY Error description

C : HTTP Status Code:500.Body ‘Error in processing your request

D : HTTP Status Code:500.Body ‘Error in processing your request

Answer: C