100% Free MCD-Level-2 Files For passing the exam Quickly UPDATED Feb 01, 2024
MCD-Level-2 Dumps Questions Study Exam Guide
NEW QUESTION # 24
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?
- A. Create a Mule daman project.
Create a common-global-error-handler flow inside the domain project.
Use this domain project as a dependency. - B. Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.
- C. 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 - D. 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.
Answer: C
Explanation:
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. References:
https://docs.mulesoft.com/mule-runtime/4.3/error-handling#global-error-handler
NEW QUESTION # 25
Which statement is true when using XML SDK for creating custom message processors?
- A. All operations are public
- B. An XML SDK provides both inbound and outbound operations
- C. Properties 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
- D. Operations can be reused in recursive calls
Answer: A
Explanation:
Explanation
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. References: https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#operations
NEW QUESTION # 26
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?
- A. The Mule flow will throw the exception 'JSON:SCHEMA_NOT_HONOURED
- B. The Mule flow will execute successfully with status code 204
- C. The 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.'' - D. The Mule flow will execute successfully with status code 200, and the response will be the JSON sent in request
Answer: A
Explanation:
Explanation
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'. References:
https://docs.mulesoft.com/json-module/1.1/json-validate-schema
NEW QUESTION # 27
A Mule application deployed to a standardalone Mule runtime uses VM queues to publish messages to be consumed asynchronously by another flow.
In the case of a system failure, what will happen to in-flight messages in the VM queues that have been consumed?
- A. For persistent queues, the message will be processed after the system comes online
- B. For nay type of queue, the message will be processed after the system comes online
- C. For any type of queue, the message will be lost
- D. For transient queues, the message will be processed after the system comes online
Answer: A
Explanation:
Explanation
In case of a system failure, in-flight messages in persistent VM queues that have been consumed will be processed after the system comes online. This is because persistent VM queues store messages on disk and guarantee delivery even if there is a system crash or restart. Therefore, any in-flight messages that have been consumed but not processed will be recovered from disk and processed when the system is back online.
References: https://docs.mulesoft.com/mule-runtime/4.3/vm-connector#persistent-queues
NEW QUESTION # 28
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?
- A. Wrap all Anypoint MQ Publish operations within a With CorrelationID scope from the Tracing module, setting the correlation ID to the order ID
- B. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
- C. Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
- D. Use the underlying HTTP request of Anypoint MQ to set the 'X-CORRELATION_ID' header to the order ID
Answer: A
Explanation:
Explanation
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. References:
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
NEW QUESTION # 29
When registering a client application with an existing API instance or API Group instance, what is required to manually approve or reject request access?
- A. To configure the SLA tier for the application
- B. To configure the SLA tier for the application and have the role of Organization Administrator, API Manager Environment Administrator, or the Manage Contacts permission
- C. To configure the SLA tier for the application and have the Exchange Administrator permission
- D. To only have Exchange Administrator permission
Answer: B
Explanation:
Explanation
To manually approve or reject request access when registering a client application with an existing API instance or API Group instance, it is required to configure the SLA tier for the application and have one of the following roles or permissions: Organization Administrator, API Manager Environment Administrator, or Manage Contracts permission. These roles or permissions allow managing client applications and contracts in API Manager. References:
https://docs.mulesoft.com/api-manager/2.x/client-applications#managing-client-applications-and-contracts
NEW QUESTION # 30
Which pattern should be used to invoke multiple HTTP APIs in parallel and roll back failed requests in sequence?
- A. Scatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes
- B. A database as a transactional outbox and an Until Successful router to retry any requests
- C. VM queues as a reliability pattern with error handlers to roll back any requests
- D. A Parallel for Each scope with each HTTP request wrapped in a Try scope
Answer: A
Explanation:
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. References:
https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept
https://docs.mulesoft.com/mule-runtime/4.3/saga
NEW QUESTION # 31
A developer has created the first version of an API designed for business partners to work commodity prices.
What should developer do to allow more than one major version of the same API to be exposed by the implementation?
- A. In Design Center, open the RAML and modify baseUn to include a variable that indicates the version number
- B. In Design Center, open the RAML and modify each operation to include the major version number
- C. In Anypoint Studio, generate scaffolding from the RAML, and then modify the flow names generated by APIKit to include a variable with the major version number
- D. In Anypoint Studio, generate scaffolding from the RAML, and the modify the <http:listerner> in the generated flows to include a parameter to replace the version number
Answer: A
Explanation:
Explanation
To allow more than one major version of the same API to be exposed by the implementation, the developer should modify the baseUri property in the RAML file to include a variable that indicates the version number.
The baseUri property defines the base URL of the API and can include variables that are replaced with actual values when mocking or deploying the API. By using a variable for the version number, the developer can expose different versions of the API using different base URLs and avoid conflicts or confusion. References:
https://docs.mulesoft.com/api-designer/design-modify-raml-specs#baseuri
https://docs.mulesoft.com/api-manager/2.x/api-versioning
NEW QUESTION # 32
Refer to the exhibit.
The flow name is ''implementation'' with code for the MUnit test case.
When the MUnit test case is executed, what is the expected result?
- A. The test case fails with an assertion error
- B. The test throws an error and does not start
- C. The test case fails with an unexpected error type
- D. The test case passes
Answer: A
Explanation:
Explanation
Based on the code snippet and MUnit test case below, when the MUnit test case is executed, the expected result is that the test case fails with an assertion error. This is because the assert-equals processor compares two values for equality, and fails if they are not equal. In this case, the expected value is 'Hello World', but the actual value returned by the implementation flow is 'Hello Mule'. Therefore, the assertion fails and an error is thrown. References: https://docs.mulesoft.com/munit/2.3/assert-equals-processor
NEW QUESTION # 33
An API has been developed and deployed to CloudHub Among the policies applied to this API is an allowlist of IP addresses. A developer wants to run a test in Anypoint Studio and does not want any policies applied because their workstation is not included in the allowlist.
What must the developer do in order to run this test locally without the policies applied?
- A. Create a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager
- B. Run the test as-s, with no changes because the Studio runtime will not attempt to connect to API Manager
- C. Deactivate the API in API Manager so the Autodiscovery element will not find the application when it runs in Studio
- D. Pass in the runtime parameter ''-Danpow.platform.gatekeeper=disabled''
Answer: A
Explanation:
Explanation
To run a test locally without the policies applied, the developer should create a properties file specifically for local development and set the API instance ID to a value that is not used in API Manager. This way, the developer can use different configuration properties for different environments and avoid triggering API autodiscovery when running tests locally. API autodiscovery is a mechanism that associates an API implementation with its corresponding API specification and policies in API Manager based on its API instance ID. By setting this ID to a value that does not exist in API Manager, the developer can prevent API autodiscovery from finding and applying any policies to the local test. References:
https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept#configuring-api-autodiscovery
https://docs.mulesoft.com/mule-runtime/4.3/configuring-properties
NEW QUESTION # 34
A developer deploys an API to CloudHub and applies an OAuth policy on API Manager. During testing, the API response is slow, so the developer reconfigures the API so that the out-of-the-box HTTP Caching policy is applied first, and the OAuth API policy is applied second.
What will happen when an HTTP request is received?
- A. In case of a cache miss, both the OAuth and HTTP Caching policies are evaluated; then the API retrieves the data from the API implementation, and the policy does not store the data in Object Store
- B. In case of a cache miss, only the HTTP Caching policy is evaluated; then the API retrieves the data from the API implementation, and the policy stores the data to be cached in Object Store
- C. In case of a cache hit, both the OAuth and HTTP Caching policies are evaluated; then the cached response is returned to the caller
- D. In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller
Answer: D
Explanation:
Explanation
When an HTTP request is received and the HTTP Caching policy is applied first, it checks if there is a cached response for that request in Object Store. If there is a cache hit, meaning that a valid cached response exists, then only the HTTP Caching policy is evaluated and the cached response is returned to the caller without invoking the OAuth policy or the API implementation. If there is a cache miss, meaning that no valid cached response exists, then both the HTTP Caching policy and the OAuth policy are evaluated before invoking the API implementation. References:
https://docs.mulesoft.com/api-manager/2.x/http-caching-policy#policy-ordering
NEW QUESTION # 35
Which plugin or dependency is required to unit test modules created with XML SDK?
- A. XMLUnit
- B. MUnit Extensions Maven plugin
- C. MUnit Maven plugin
- D. Junit
Answer: B
Explanation:
Explanation
To unit test modules created with XML SDK, the developer needs to use the MUnit Extensions Maven plugin.
This plugin allows testing XML SDK modules using MUnit by adding a dependency to the module under test and using a custom processor tag to invoke it. References:
https://docs.mulesoft.com/mule-sdk/1.1/xml-sdk#testing
NEW QUESTION # 36
Multiple individual Mute application need to use the Mule Maven plugin to deploy to CloudHub.
The plugin configuration should .. reused where necessary and anything project, specific should be property-based.
Where should the Mule Maven details be configured?
- A. Settings, xml
- B. Pom, xml
- C. A parent pom.xml
- D. A Bill of Materials (BOM) parent pm
Answer: C
Explanation:
Explanation
To reuse Mule Maven plugin configuration across multiple individual Mule applications, the developer should use a parent pom.xml file. A parent pom.xml file defines common configuration for one or more child projects that inherit from it. The developer can specify common properties and dependencies for all child projects in the parent pom.xml file, such as Mule Maven plugin configuration, and then reference them in each child project's pom.xml file using placeholders. References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#parent-pom
https://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance
NEW QUESTION # 37
A custom policy needs to be developed to intercept all cutbound HTTP requests made by Mule applications.
Which XML element must be used to intercept outbound HTTP requests?
- A. http-policy:source
- B. http-policy:processor
- C. It is not possible to intercept outgoing HTTP requests, only inbound requests
- D. htt-policy:operation
Answer: B
Explanation:
Explanation
The http-policy:processor element is used to intercept outbound HTTP requests made by Mule applications. It allows customizing the request before it is sent to the target API and modifying the response after it is received from the target API. References:
https://docs.mulesoft.com/api-manager/2.x/policy-mule4-custom-policy#policy-xml-file
NEW QUESTION # 38
The flow is invoicing a target API. The API's protocol is HTTPS. The TLS configuration in the HTTP Request Configuration global element is set to None. A web client submits a request to
http:localhost:8081/vehicles.
If the certificate of the target API is signed by a certificate authority (CA), what is true about the HTTP Request operation when the flow executes?
- A. The HTTP Request operation will always fail regardless of the CA
- B. The HTTP Request operation will succeed if the CA's certificate is present in the JRE's default truststore.
- C. The HTTP Request operation will succeed if the CA'S certificate is present in the JRE's default keystore
- D. The HTTP Request operation will always succeed regardless of the CA
Answer: B
Explanation:
Explanation
The HTTP Request operation will use the default truststore of the JRE to validate the certificate of the target API. If the CA's certificate is present in the truststore, the operation will succeed. Otherwise, it will fail with a handshake exception. References: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#tls-default
NEW QUESTION # 39
The Center for Enablement team published a common application as a reusable module to the central Nexus repository.
How can the common application be included in all API implementations?
- A. Add a Maven dependency in the POM file with jar as <classifier>
- B. Add a Maven dependency in the PCM file with multiple-plugin as <classifier>
- C. Download the common application from Naxus and copy it to the src/main/resources folder in the API
- D. Copy the common application's source XML file and out it in a new flow file in the src/main/mule folder
Answer: A
Explanation:
Explanation
To include a common application as a reusable module in all API implementations, the developer should add a Maven dependency in the POM file with jar as <classifier>. This way, the developer can reuse Mule code from another application by packaging it as a JAR file and adding it as a dependency in the POM file of the API implementation. The classifier element specifies that it is a JAR file. References:
https://docs.mulesoft.com/mule-runtime/4.3/mmp-concept#add-a-maven-dependency-to-the-pom-file
NEW QUESTION # 40
A company deploys 10 public APIs to CloudHub. Each API has its individual health endpoint defined. The platform operation team wants to configure API Functional Monitoring to monitor the health of the APIs periodically while minimizing operational overhead and cost.
How should API Functional Monitoring be configured?
- A. From 10 public locations with each API in its own schedule
- B. From one public location with all 10 APIs in a single schedule
- C. From one public location with each API in its own schedule
- D. From one private location with all 10 APIs in a single schedule
Answer: B
Explanation:
Explanation
To configure API Functional Monitoring to monitor the health of 10 public APIs periodically while minimizing operational overhead and cost, the developer should use one public location with all 10 APIs in a single schedule. A public location is a worker that runs in a CloudHub shared environment, which is cheaper and easier to maintain than a private location. A single schedule allows running all 10 APIs tests at the same time and frequency, which reduces complexity and resource consumption. References:
https://docs.mulesoft.com/functional-monitoring/fm-create-monitor#create-a-monitor
NEW QUESTION # 41
......
MCD-Level-2 Premium Exam Engine - Download Free PDF Questions: https://www.actualtestsit.com/MuleSoft/MCD-Level-2-exam-prep-dumps.html