Mulesoft MCD-LEVEL2 Online Practice Questions and Exam Preparation

Mulesoft MCD-LEVEL2 Online Questions & Answers

• Question 21:

  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. Pass in the runtime parameter `'-Danpow.platform.gatekeeper=disabled''
  C. Deactivate the API in API Manager so the Autodiscovery element will not find the application when it runs in Studio
  D. Run the test as-s, with no changes because the Studio runtime will not attempt to connect to API Manager
  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

  ---

  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

• Question 22:

  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
  A. A parent pom.xml

  ---

  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

• Question 23:

  A Mule application defines as SSL/TLS keystore properly `tis,keystore.keyPassword'' as secure.

  How canthis property be referenced to access its value within the application?

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

  ---

  Explanation

  secure::tiskeystore,keyPassowrdShortExplanationofCorrectAnswerOnly:Toreferenceasecur epropertyvaluewithintheapplication,thedeveloperneedstousethesyntax{secure::}. 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

• Question 24:

  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 one public location with each API in its own schedule
  B. From one private location with all 10 APIs in a single schedule
  C. From one public location with all 10 APIs in a single schedule
  D. From 10 public locations with each API in its own schedule
  C. From one public location with all 10 APIs in a single schedule

  ---

  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 locationwith 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

• Question 25:

  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:200. Body `Error in processing your request
  B. HTTP Status Code:500. Body `The HTTP CONNECTIVITY Error description
  C. HTTP Status Code:500. Body `Error in processing your request
  D. HTTP Status Code:500. Body `Error in processing your request
  C. HTTP Status Code:500. Body `Error in processing your request

  ---

  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

• Question 26:

  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 failures[`2']
  C. Error,errorMessage,payload.failures[`2']
  D. Payload [`2']
  C. Error,errorMessage,payload.failures[`2']

  ---

  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

• Question 27:

  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 hit, both the OAuth and HTTP Caching policies are evaluated; then the cached response is returned to the caller
  B. In case of a cache it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller
  C. 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
  D. In case of a cache miss, both the OAuth and HTTP Cachingpolicies 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 it, only the HTTP Caching policy is evaluating; then the cached response is returned to the caller

  ---

  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

• Question 28:

  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 keystore
  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 always succeed regardless of the CA
  D. 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.

  ---

  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

• Question 29:

  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. A1, B1, F1, B2, A2
  B. B1, A1, F1, A2, B2
  C. F1, A1, B1, B2, A2
  D. F1, B1, A1, A2, B2
  A. A1, B1, F1, B2, A2

  ---

  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 executedafter 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

• 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 transient queues, the message will be processed after the system comes online
  D. For any type of queue, the message will be lost
  B. For persistent queues, the message will be processed after the system comes online

  ---

  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