CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. MuleSoft
  5. MCD-Level-2

Free MCD-Level-2 Exam Braindumps (page: 6)

Page 6 of 16
PDF with 60 Questions

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?

  1. CloudHub encrypts the value
  2. The Mule server encrypts the value
  3. Anypoint Studio secures the value
  4. Runtime Manager masks the value

Answer(s): D

Explanation:

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



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?

  1. 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.
  2. Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.
  3. Create 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
  4. Create a Mule daman project.
    Create a common-global-error-handler flow inside the domain project.
    Use this domain project as a dependency.

Answer(s): C

Explanation:

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



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?

  1. Use a DataWeave 2.09 transform operation, and at the log of the DataWeave script, add:
    %dw 2.0
    Import.json-moduls
  2. Using the DataWeave if Else condition test the values of the payload against the examples included in the schema
  3. Apply the JSON Schema policy in API Manager and reference the correct schema in the policy configuration
  4. Add the JSON module dependency and add the validate-schema operation in the flow, configured to reference the schema

Answer(s): D

Explanation:

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



Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?

  1. A database as a transactional outbox and an Until Successful router to retry any requests
  2. A Parallel for Each scope with each HTTP request wrapped in a Try scope
  3. Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
  4. VM queues as a reliability pattern with error handlers to roll back any requests

Answer(s): C

Explanation:

To invoke multiple HTTP APIs in parallel and roll back failed requests in sequence, the developer should use a Scatter-Gather router as a central Saga orchestrator for all API requests with compensating actions for failing routes. A Scatter-Gather router executes multiple routes concurrently and aggregates the results. A Saga orchestrator coordinates a series of actions across different services and handles failures by executing compensating actions. Therefore, using a Scatter- Gather router as a Saga orchestrator allows invoking multiple HTTP APIs in parallel and rolling back any failed requests in sequence.


Reference:

https://docs.mulesoft.com/mule-runtime/4.3/scatter- gather-concept https://docs.mulesoft.com/mule-runtime/4.3/saga



Page 6 of 16



Post your Comments and Discuss MuleSoft MCD-Level-2 exam with other Community members:

Anonymous commented on November 10, 2024
Good ONE FOR mcd l2
INDIA
upvote

RM commented on October 30, 2024
Thank you for the dumps
Anonymous
upvote

Champ commented on September 26, 2024
Good to see that something is still free. I truly appreciate this service.
Mexico
upvote