[Nov 20, 2024] MCD-Level-2 Test Prep Training Practice Exam Questions Practice Tests [Q23-Q46]

Share

[Nov 20, 2024] MCD-Level-2 Test Prep Training Practice Exam Questions Practice Tests

Exam Questions Answers Braindumps MCD-Level-2 Exam Dumps PDF Questions

NEW QUESTION # 23
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. 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.
  • B. Configure retrying until a MULERETRY_EXHAUSTED error is raised or the API responds back with a successful response.
  • C. In Until Successful configuration, set the retry count to 1 for error type HTTP: UNAUTHORIZED.
  • D. 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.

Answer: D

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

  • A. Object Store Connector
  • B. CloudHub REST API
  • C. Object Store v2 REST API
  • D. CloudHub Connector

Answer: C

Explanation:
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.
References:https://docs.mulesoft.com/object-store/osv2-apis


NEW QUESTION # 25
Refer to the exhibit.

A Mule application pom.xml configures the Maven Resources plugin to exclude parsing binary files in the project's src/main/resources/certs directory.
Which configuration of this plugin achieves a successful build?

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

Answer: B

Explanation:
Explanation
To configure the Maven Resources plugin to exclude parsing binary files in the project's src/main/resources/certs directory, option C should be used. This option specifies that any files with .cer or .jks extensions under the certs directory should be excluded from filtering. Filtering is a process of replacing placeholders with actual values in resource files during the build process. Binary files should not be filtered because they may become corrupted or unusable. References:
https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
https://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html


NEW QUESTION # 26
Refer to the exhibit.

A developer generates the base scaffolding for an API in Anypoint Studio.
Which HTTP status code is returned while testing using the API Kit console if no values are entered in client-secret?

  • A. HTTP status code:403
  • B. HTTP status code:400
  • C. HTTP status code:500
  • D. HTTP status code:200

Answer: A

Explanation:
Based on the code snippet and schema.json file below, when testing using the API Kit console if no values are entered in client-secret, HTTP status code 403 (FORBIDDEN) is returned. This is because client-secret is defined as a required header parameter in schema.json file, which means that it must be present in every request. If no values are entered in client-secret, then it is equivalent to omitting this header parameter, which violates the schema and causes APIKit Router to return HTTP status code 403.
References:https://docs.mulesoft.com/apikit/4.x/apikit-4-headers


NEW QUESTION # 27
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. testPayload
  • C. originalPayload
  • D. nullPayload

Answer: D

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 # 28
Which statement is true about using mutual TLS to secure an application?

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

Answer: A

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 # 29
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. Runtime Manager masks the value
  • B. The Mule server encrypts the value
  • C. CloudHub encrypts the value
  • D. Anypoint Studio secures the value

Answer: A

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 # 30
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 nay type of queue, the message will be processed after the system comes online
  • B. For persistent queues, 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: B

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 # 31
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. Runtime Manager masks the value
  • B. The Mule server encrypts the value
  • C. CloudHub encrypts the value
  • D. Anypoint Studio secures the value

Answer: A

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 # 32
Refer to the exhibit.

A Mule application pom.xml configures the Maven Resources plugin to exclude parsing binary files in the project's src/main/resources/certs directory.
Which configuration of this plugin achieves a successful build?

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

Answer: B

Explanation:
To configure the Maven Resources plugin to exclude parsing binary files in the project's src/main/resources/certs directory, option C should be used. This option specifies that any files with .cer or .jks extensions under the certs directory should be excluded from filtering. Filtering is a process of replacing placeholders with actual values in resource files during the build process. Binary files should not be filtered because they may become corrupted or unusable. References:
https://maven.apache.org/plugins/maven-resources-plugin/examples/filter.htmlhttps://maven.apache.org/plugins/


NEW QUESTION # 33
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 # 34
A scatter-gather router is configured with four routes:Route A, B, C and D.
Route C false.

  • A. Error,errorMesage.payload.results ['2']
  • B. Payload ['2']
  • C. Payload failures['2']
  • D. Error,errorMessage,payload.failures['2']

Answer: A

Explanation:
The result of accessing route C failure is Error,errorMessage,payload.failures['2']. This is because a scatter-gather router returns an aggregated message that contains an array of results from each route and an array of failures from each route. The failures array contains error objects with information about each failed route execution. To access route C failure, which is the third route (index 2), the developer needs to use Error.errorMessage.payload.failures['2'] expression.
References:https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-reference#scatter-gather-output


NEW QUESTION # 35
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. A parent pom.xml
  • B. Settings, xml
  • C. Pom, xml
  • D. A Bill of Materials (BOM) parent pm

Answer: A

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-pomhttps://maven.apache.org/guides/introduc


NEW QUESTION # 36
An API has been built to enable scheduling email provider. The front-end system does very little data entry validation, and problems have started to appear in the email that go to patients. A validate-customer'' flow is added validate the data.
What is he expected behavior of the 'validate-customer'' flow?

  • 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

Explanation:
The validate-customer flow uses an until-successful scope to validate each field of the customer data. The until-successful scope executes its processors until they succeed or exhausts the maximum number of retries.
If any processor fails, it raises an error and stops executing the remaining processors. Therefore, if only the email address is invalid, a VALIDATION.INVALID_EMAIL error is raised and the validation of appointment date and customer name is skipped.
References:https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope


NEW QUESTION # 37
When implementing a synchronous API where the event source is an HTTP Listener, a developer needs to return the same correlation ID back to the caller in the HTTP response header.
How can this be achieved?

  • A. Enable the CorrelationID checkbox in the HTTP Listener configuration
  • B. Configure a custom correlation policy
  • C. NO action is needed as the correlation ID is returned to the caller in the response header by default
  • D. Enable the auto-generate CorrelationID option when scaffolding the flow

Answer: C

Explanation:
Explanation
When implementing a synchronous API where the event source is an HTTP Listener, Mule automatically propagates some message attributes between flows via outbound and inbound properties. One of these attributes is correlation ID, which is returned to the caller in the response header by default as MULE_CORRELATION_ID. References:
https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#message-attributes


NEW QUESTION # 38
A company has been using CI/CD. Its developers use Maven to handle build and deployment activities.
What is the correct sequence of activities that takes place during the Maven build and deployment?

  • A. Validate, initialize, compile, test package, verify, install, deploy
  • B. Validation, initialize, compile, test, package, install verify, deploy
  • C. Validate, initialize, compile, package, test, install, verify, verify, deploy
  • D. Initialize, validate, compute, test, package, verify, install, deploy

Answer: A

Explanation:
The correct sequence of activities that takes place during the Maven build and deployment is validate, initialize, compile, test package, verify, install, deploy. These are Maven lifecycle phases that define a sequence of goals to execute during a build process. Each phase represents a stage in the build lifecycle and can have zero or more goals bound to it.
References:https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html


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

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

Answer: B

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.
References:https://docs.mulesoft.com/json-module/1.1/json-validate-schema


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

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

Answer: D

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-concepthttps://docs.mulesoft.com/mule-runtime/4.3/sa


NEW QUESTION # 41
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 throws an error and does not start
  • B. The test case fails with an assertion error
  • C. The test case fails with an unexpected error type
  • D. The test case passes

Answer: B

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 # 42
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 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. Use the Tracing module to set logging variables with a Mapped Diagnostic Context
  • D. Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector

Answer: C

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 # 43
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 Public key format
  • C. The TLS version
  • D. A protocol

Answer: A

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 # 44
Which properties are mandatory on the HTTP Connector configuration in order to use the OAuth 2.0 Authorization Code grant type for authentication?

  • A. Token URL, authorization URL, client ID, client secret local callback URL
  • B. External callback URL, access token URL, client ID response access token
  • C. External callback URL, access token URL, client ID, response refresh token
  • D. External callback URL, access token URL, local authorization URL, authorization URL, client ID, client secret

Answer: A

Explanation:
Explanation
To use the OAuth 2.0 Authorization Code grant type for authentication, the HTTP Connector configuration requires the following properties: token URL, authorization URL, client ID, client secret, and local callback URL. The token URL is the endpoint of the authorization server that provides access tokens. The authorization URL is the endpoint of the authorization server that initiates the user consent flow. The client ID and client secret are the credentials of the Mule application registered with the authorization server. The local callback URL is the endpoint of the Mule application that receives the authorization code from the authorization server.
References: https://docs.mulesoft.com/http-connector/1.6/http-authentication#oauth-2-0


NEW QUESTION # 45
A system API that communicates to an underlying MySQL database is deploying to CloudHub. The DevOps team requires a readiness endpoint to monitor all system APIs.
Which strategy should be used to implement this endpoint?

  • A. Create a dedicated endpoint that responds with the API status and reachability of the underlying systems
  • B. Create a dedicated endpoint that responds with the API status and health of the server
  • C. Create a dedicated endpoint that responds with the API status only
  • D. Use an existing resource endpoint of the API

Answer: A

Explanation:
Explanation
To implement a readiness endpoint to monitor all system APIs, the developer should create a dedicated endpoint that responds with the API status and reachability of the underlying systems. This way, the DevOps team can check if the system API is ready to receive requests and if it can communicate with its backend systems without errors. References:
https://docs.mulesoft.com/mule-runtime/4.3/deployment-strategies#readiness-probes


NEW QUESTION # 46
......

Download Free MuleSoft MCD-Level-2 Real Exam Questions: https://torrentpdf.exam4tests.com/MCD-Level-2-pdf-braindumps.html