Question No. 1

Refer to the exhibit.

Based on the code snippet, schema,json file, and payload below, what is the outcome of the given code snippet when a request is sent with the payload?

AThe Mule flow will execute successfully with status code 200, and the response will be the JSON sent in request

BThe Mule flow will execute successfully with status code 204

CThe Mule flow will throw the exception 'JSON:SCHEMA_NOT_HONOURED

DThe Mule flow will execute successfully with status code 200m and a response will display the message '' Age in years which must equal to or greater than zero.''

Show Answer

Correct Answer: C

Based on the code snippet, schema.json file, and payload below, the outcome of the given code snippet when a request is sent with the payload is that the Mule flow will throw the exception 'JSON:SCHEMA_NOT_HONOURED'. This is because the payload does not conform to the schema.json file, which specifies that age must be a number greater than or equal to zero. The payload has age as a string with a negative value, which violates the schema. Therefore, the validate-schema operation throws an error with type 'JSON:SCHEMA_NOT_HONOURED'. Reference: https://docs.mulesoft.com/json-module/1.1/json-validate-schema

Question No. 2

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

AA database as a transactional outbox and an Until Successful router to retry any requests

BA Parallel for Each scope with each HTTP request wrapped in a Try scope

CScatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes

DVM queues as a reliability pattern with error handlers to roll back any requests

Show Answer

Correct Answer: C

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

Question No. 3

An order processing system is composed of multiple Mule application responsible for warehouse, sales and shipping. Each application communication using Anypoint MQ. Each message must be correlated against the original order ID for observability and tracing.

How should a developer propagate the order ID as the correlation ID across each message?

AUse the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID

BSet a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.

CUse the default correlation ID, Anypoint MQ will sutomatically propagate it.

DWrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID

Show Answer

Correct Answer: D

To propagate the order ID as the correlation ID across each message using Anypoint MQ, the developer should wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID. The With CorrelationID scope allows setting a custom correlation ID for any event that occurs within it. The Tracing module also enables distributed tracing across different Mule applications and services using Anypoint Monitoring. Reference: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#with-correlation-id-scope https://docs.mulesoft.com/tracing-module/1.0/tracing-module-concepts

Question No. 4

In a Mule project, Flow-1 contains a flow-ref to Flow-2 depends on data from Flow-1 to execute successfully.

Which action ensures the test suites and test cases written for Flow-1 and Flow-2 will execute successfully?

AChain together the test suites and test cases for Flow-1 and Flow-2

BUse ''Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 independent

CUse ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases

DUse 'After Test Case' to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases

Show Answer

Correct Answer: B

To ensure the test suites and test cases written for Flow-1 and Flow-2 will execute successfully, the developer should use a Set Event processor to pass the input that is needed by Flow-2, and keep the test cases for Flow-1 and Flow-2 independent. This way, the developer can isolate the testing of each flow and avoid coupling them together. Reference: https://docs.mulesoft.com/munit/2.3/munit-test-flow

Question No. 5

Mule application A is deployed to CloudHub and is using Object Store v2. Mute application B is also deployed to CloudHub.

Which approach can Mule application B use to remove values from Mule application A'S Object Store?

AObject Store v2 REST API

BCloudHub Connector

CObject Store Connector

DCloudHub REST API

Show Answer

Correct Answer: A

To remove values from Mule application A's Object Store v2, Mule application B can use Object Store v2 REST API. This API allows performing operations on Object Store v2 resources using HTTP methods, such as GET, POST, PUT, and DELETE. Mule application B can use the DELETE method to remove values from Mule application A's Object Store v2 by specifying the object store ID and the key of the value to delete. Reference: https://docs.mulesoft.com/object-store/osv2-apis

Free MuleSoft MCD-Level-2 Exam Actual Questions

The questions for MCD-Level-2 were last updated On Nov 18, 2024