Try Before You Buy

Download a free sample of any of our exam questions and answers

  • 24/7 customer support, Secure shopping site
  • Free One year updates to match real exam scenarios
  • If you failed your exam after buying our products we will refund the full amount back to you.

[Aug-2023] MCD-Level-2 PDF Dumps Are Helpful To produce Your Dreams Correct QA's [Q32-Q56]

Share

[Aug-2023] MCD-Level-2 PDF Dumps Are Helpful To produce Your Dreams Correct QA's

New MCD-Level-2 exam Free Sample Questions to Practice

NEW QUESTION # 32
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?

  • A. Use the Tracing module to set logging variables with a Mapped Diagnostic Context
  • B. Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector
  • C. Set a flow variable and edit the log4/2.xml file to output the variable as part of the message pattern
  • D. Use flow variables within every logger processor to log the order ID

Answer: A

Explanation:
Explanation
To enrich every log message with the order ID, the developer should use the Tracing module to set logging variables with a Mapped Diagnostic Context (MDC). The Tracing module allows adding custom key-value pairs to log messages using MDC variables. The developer can use Set Logging Variables operation to set the order ID as an MDC variable and then use it in any logger processor within the same thread or event.
References: https://docs.mulesoft.com/tracing-module/1.0/tracing-module-reference#set-logging-variables


NEW QUESTION # 33
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 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.
  • 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 daman project.
    Create a common-global-error-handler flow inside the domain project.
    Use this domain project as a dependency.

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 # 34
A heathcare customer wants to use hospital system data, which includes code that was developed using legacy tools and methods. The customer has created reusable Java libraries in order to read the data from the system.
What is the most effective way to develop an API retrieve the data from the hospital system?

  • A. Install libraries in a local repository and refer to it in the pm.xml file
  • B. Refer to JAR files in the code
  • C. Include the libraries writes deploying the code into the runtime
  • D. Create the Java code in your project and invoice the data from the code

Answer: A

Explanation:
Explanation
To develop an API that retrieves data from a hospital system using reusable Java libraries, the developer should install libraries in a local repository and refer to it in the pom.xml file. This way, the developer can use Maven to manage dependencies and invoke Java code from Mule applications using Java Module operations.
References:
https://docs.mulesoft.com/mule-runtime/4.3/java-module-reference#add-the-java-module-to-your-project
https://docs.mulesoft.com/mule-runtime/4.3/java-module-reference#invoke-java-code


NEW QUESTION # 35
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 # 36
A Mule application uses API autodiscovery to access and enforce policies for a RESTful implementation.

  • A. The name of the flow that has APlkit Console to receive all incoming RESTful operation requests.
  • B. The name of the flow that has HTTP listener to receive all incoming RESTful operation requests
  • C. Any of the APIkit generate implement flows
  • D. Northing because flowRef is an optional attribute which can be passed runtime

Answer: B

Explanation:
Explanation
To use API autodiscovery to access and enforce policies for a RESTful implementation, flowRef must be set to the name of the flow that has HTTP listener to receive all incoming RESTful operation requests. This way, API autodiscovery can identify the API implementation and associate it with the corresponding API specification and policies in API Manager. The flow that has HTTP listener is usually the main flow that contains the APIKit Router. References:
https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept#flowref


NEW QUESTION # 37
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 succeed if the CA's certificate is present in the JRE's default truststore.
  • B. The HTTP Request operation will always fail regardless of the CA
  • C. The HTTP Request operation will always succeed regardless of the CA
  • D. The HTTP Request operation will succeed if the CA'S certificate is present in the JRE's default keystore

Answer: A

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 # 38
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?

  • A. ${secure::tiskeystore,keyPassowrd}
  • B. #{secure::tiskeystore,keyPassowrd}
  • C. p{secure::tiskeystore,keyPassowrd}
  • D. ${secure::tiskeystore,keyPassowrd}

Answer: A

Explanation:
Explanation
secure::tiskeystore,keyPassowrdShortExplanationofCorrectAnswerOnly:Toreferenceasecurepropertyvaluewithin In this case, the property name is tiskeystore,keyPassword, so the correct syntax is
${secure::tiskeystore,keyPassowrd}. References:
https://docs.mulesoft.com/mule-runtime/4.3/secure-configuration-properties#referencing-secure-properties


NEW QUESTION # 39
A Mule application contain two policies Policy A and Policy A has order1, and Policy B has order 2. Policy A Policy B, and a flow are defined by he configuration below.

When a HTTP request arrives at the Mule application's endpoint, what will be the execution order?

  • A. F1, A1, B1, B2, A2
  • B. B1, A1, F1, A2, B2
  • C. F1, B1, A1, A2, B2
  • D. A1, B1, F1, B2, A2

Answer: D

Explanation:
Explanation
Based on the configuration below, when a HTTP request arrives at the Mule application's endpoint, the execution order will be A1, B1, F1, B2, A2. This is because policies are executed before and after the API implementation flow according to their order attribute. Policy A has order 1, which means it is executed first before Policy B, which has order 2. The flow is executed after both policies are executed before the flow.
Then, Policy B is executed after the flow before Policy A is executed after the flow. References:
https://docs.mulesoft.com/api-manager/2.x/policies-policy-order


NEW QUESTION # 40
Refer to the exhibits.
Bioinfo System API is implemented and published to Anypoint Exchange. A developer wants to invoke this API using its REST Connector.
What should be added to the POM?

  • A.
  • B.
  • C.
  • D.
  • E.

Answer: D

Explanation:
Explanation
To invoke Bioinfo System API using its REST Connector, option E should be added to the pom.xml file. This option adds a dependency for Bioinfo System API REST Connector with its group ID, artifact ID, version, classifier, and type. The classifier specifies that it is a REST Connector (raml-client), and the type specifies that it is a Mule plugin (mule-plugin). References:
https://docs.mulesoft.com/apikit/4.x/apikit-4-generate-from-rest-api-task#add-the-api-dependency-to-the-pom-fil


NEW QUESTION # 41
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. Set a custom Anypoint MQ user property to propagate the order ID and set the correlation ID in the receiving applications.
  • C. Use the default correlation ID, Anypoint MQ will sutomatically propagate it.
  • 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 # 42
A Mule application deployed to multiple Cloudhub 2.0 replicas needs to temporarily persist large files over
10MB between flow executions, and routinely needs to query whether the file data exists on separate executions.
How can this be achieved?

  • A. Store the key and full contents of the file, caching the filename and location between requests
  • B. Use an in-memory Object Store
  • C. Store the key and full contents of the file in an Object Store
  • D. Store the contents of the file on separate storage, and store the key and location of the file Object using Object Store v2

Answer: D

Explanation:
Explanation
To temporarily persist large files over 10MB between flow executions, and routinely query whether the file data exists on separate executions, the developer should store the contents of the file on separate storage, and store the key and location of the file object using Object Store v2. This way, the developer can avoid storing large files in memory or exceeding the size limit of Object Store v2 (10MB per object). The developer can also use Object Store v2 operations to query, retrieve, or delete the file object by its key. References:
https://docs.mulesoft.com/object-store/osv2-faq#can-i-store-files-in-object-store-v2


NEW QUESTION # 43
A Mule application includes a subflow containing a Scatter.Gather scope. Within each log of the Scatter.Gatter. an HTTP connector calls a PUT endpoint to modify records in different upstream system. The subflow is called inside an Unit successful scope to retry if a transitory exception is raised.
A technical spike is being performed to increase reliability of the Mule application.
Which steps should be performed within the Mule flow above the ensure idempontent behavior?

  • A. Change the PUT requests inside the Scatter-Gather to POST requests
  • B. None, the flow already exhibits idempotent behavior
  • C. Remove the Put requests from the Scatter-Getter and perform them sequentially
  • D. Ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails

Answer: D

Explanation:
Explanation
To ensure idempotent behavior within a Mule flow that contains a subflow with a Scatter-Gather scope, the developer should ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails. Idempotency means that multiple identical requests have the same effect as a single request. Therefore, if one of the HTTP requests inside the Scatter-Gather fails, the error-handling flow should undo any changes made by other successful requests to ensure consistency and avoid partial updates.
References: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept
https://docs.mulesoft.com/mule-runtime/4.3/error-handling


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

  • A. An encryption algorithm
  • B. The TLS version
  • C. A protocol
  • D. The Public key format

Answer: A

Explanation:
Explanation
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. References: https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#cipher-suites


NEW QUESTION # 45
Refer to the exhibit.
A Mute Object Store is configured with an entry TTL of one second and an expiration interval of 30 seconds.
What is the result of the flow if processing between os'store and os:retrieve takes 10 seconds?

  • A. OS:KEY_NOT_FOUND
  • B. originalPayload
  • C. nullPayload
  • D. testPayload

Answer: C

Explanation:
Explanation
The result of the flow is nullPayload if processing between os:store and os:retrieve takes 10 seconds. This is because the entry TTL of the object store is one second, which means that any stored value expires after one second and is removed from the object store. The expiration interval of 30 seconds only determines how often the object store checks for expired values, but it does not affect the TTL. Therefore, when os:retrieve tries to get the value after 10 seconds, it returns nullPayload because the value has already expired and been removed.
References: https://docs.mulesoft.com/object-store/osv2-faq#how-does-the-time-to-live-work


NEW QUESTION # 46
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?

  • A. CloudHub encrypts the value
  • B. Runtime Manager masks the value
  • C. Anypoint Studio secures the value
  • D. The Mule server encrypts the value

Answer: B

Explanation:
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. References:
https://docs.mulesoft.com/runtime-manager/runtime-manager-agent-for-mule4#properties-tab


NEW QUESTION # 47
The HTTP Request operation raises an HTTP CONNECTIVITY error.
Which HTTP status code and body are returned to the web client?

  • A. HTTP Status Code:500.
    Body 'Error in processing your request
  • B. HTTP Status Code:200.
    Body 'Error in processing your request
  • C. HTTP Status Code:500.
    Body 'Error in processing your request
  • D. HTTP Status Code:500.
    Body 'The HTTP CONNECTIVITY Error description

Answer: A

Explanation:
Explanation
When the HTTP Request operation raises an HTTP CONNECTIVITY error, it triggers an on-error-continue handler that sets a payload with 'Error in processing your request'. Since no status code is explicitly set in this handler, it defaults to 500 (INTERNAL SERVER ERROR). Therefore, the web client receives an HTTP response with status code 500 and body 'Error in processing your request'. References:
https://docs.mulesoft.com/mule-runtime/4.3/error-handling#on-error-continue


NEW QUESTION # 48
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?

  • A. Use ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases
  • B. Use ''Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 independent
  • C. Chain together the test suites and test cases for Flow-1 and Flow-2
  • D. Use 'After Test Case' to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases

Answer: B

Explanation:
Explanation
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. References: https://docs.mulesoft.com/munit/2.3/munit-test-flow


NEW QUESTION # 49
A mule application exposes and API for creating payments. An Operations team wants to ensure that the Payment API is up and running at all times in production.
Which approach should be used to test that the payment API is working in production?

  • A. Monitor the Payment API directly sending real customer payment data
  • B. Configure the application to send health data to an external system
  • C. Create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API
  • D. Create a health check endpoint that reuses the same port number and HTTP Listener configuration as the API itself

Answer: C

Explanation:
Explanation
To test that the payment API is working in production, the developer should create a health check endpoint that listens on a separate port and uses a separate HTTP Listener configuration from the API. This way, the developer can isolate the health check endpoint from the API traffic and avoid affecting the performance or availability of the API. The health check endpoint should return a simple response that indicates the status of the API, such as OK or ERROR. References:
https://docs.mulesoft.com/api-functional-monitoring/afm-create-monitor#create-a-monitor


NEW QUESTION # 50
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. htt-policy:operation
  • B. http-policy:processor
  • C. It is not possible to intercept outgoing HTTP requests, only inbound requests
  • D. http-policy:source

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 # 51
Which command is used to convert a JKS keystore to PKCS12?

  • A. Keytool-importkeystore -srckeystore keystore jks-srcstoretype PKCS12 -destkeystore keystore.p12
    -deststoretype JKS
  • B. Keytool-importkeystore -srckeystore keystore p12-srcstoretype JKS -destkeystore keystore.p12
    -deststoretype PKCS12
  • C. Keytool-importkeystore -srckeystore keystore p12-srcstoretype PKCS12 -destkeystore keystore.jks
    -deststoretype JKS
  • D. Keytool-importkeystore -srckeystore keystore jks-srcstoretype JKS -destkeystore keystore.p13
    -deststoretype PKCS12

Answer: B

Explanation:
Explanation
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). References:
https://docs.oracle.com/en/java/javase/11/tools/keytool.html#GUID-5990A2E4-78E3-47B7-AE75-6D182625954


NEW QUESTION # 52
A Mule implementation uses a HTTP Request within an Unit Successful scope to connect to an API.
How should a permanent error response like HTTP:UNAUTHORIZED be handle inside Until Successful to reduce latency?

  • A. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
  • B. Put the HTTP Request inside a try scope in Unit Successful.
    In the error handler, use On Error Propagate to catch permanent errors like HTTP UNAUTHORIZED.
  • C. Put the HTTP Request inside a try scope in Unit Successful.
    In the error handler, use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED.
  • D. In Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.

Answer: C

Explanation:
Explanation
To handle a permanent error response like HTTP:UNAUTHORIZED inside Until Successful, the developer should put the HTTP Request inside a try scope in Unit Successful, and use On Error Continue to catch permanent errors like HTTP UNAUTHORIZED in the error handler. This way, the developer can avoid retrying requests that will always fail due to a permanent error, and reduce latency. On Error Continue allows the flow to continue processing after handling the error. References:
https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope
https://docs.mulesoft.com/mule-runtime/4.3/on-error-continue-concept


NEW QUESTION # 53
Which statement is true about using mutual TLS to secure an application?

  • A. Mutual TLS ensures only authorized end users are allowed to access an endpoint
  • B. Mutual TLS requires a hardware security module to be used
  • C. Mutual TLS authenticates the identity of the server before the identity of the client
  • D. Mutual TLS increases the encryption strength versus server-side TLS alone

Answer: C

Explanation:
Explanation
Mutual TLS (mTLS) is an extension of TLS that requires both parties (client and server) to present their certificates to each other during the handshake process. This way, both parties can verify each other's identity and establish a secure connection. The authentication of the server happens before the authentication of the client, as the server sends its certificate first and then requests the client's certificate. References:
https://docs.mulesoft.com/mule-runtime/4.3/tls-configuration#mutual-authentication


NEW QUESTION # 54
Which type of cache invalidation does the Cache scope support without having to write any additional code?

  • A. White-behind invalidation
  • B. Write-through invalidation
  • C. Notification-based invalidation
  • D. Time to live

Answer: D

Explanation:
Explanation
The Cache scope supports time to live (TTL) as a cache invalidation strategy without having to write any additional code. TTL specifies how long the cached response is valid before it expires and needs to be refreshed. The Cache scope also supports custom invalidation strategies using MEL or DataWeave expressions. References: https://docs.mulesoft.com/mule-runtime/4.3/cache-scope#cache_invalidation


NEW QUESTION # 55
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?

  • A. Use ''Before Test Case'' To collect data from Flow-1 test cases before running Flow-2 test cases
  • B. Use ''Set Event to pass the input that is needed, and keep the test cases for Flow-1 and Flow-2 independent
  • C. Chain together the test suites and test cases for Flow-1 and Flow-2
  • D. Use 'After Test Case' to produce the data needed from Flow-1 test cases to pass to Flow-2 test cases

Answer: B

Explanation:
Explanation
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. References: https://docs.mulesoft.com/munit/2.3/munit-test-flow


NEW QUESTION # 56
......

Cover MCD-Level-2 Exam Questions Make Sure You 100% Pass: https://examboost.vce4dumps.com/MCD-Level-2-latest-dumps.html