Mulesoft MCD-LEVEL2 Online Practice Questions and Exam Preparation

Mulesoft MCD-LEVEL2 Online Questions & Answers

• Question 31:

  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
  A. If only the email address Is invalid a VALIDATION.INVALID_EMAIL error is raised

  ---

  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

• Question 32:

  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. Initialize, validate, compute, test, package, verify, install, deploy
  B. Validate, initialize, compile, package, test, install, verify, verify, deploy
  C. Validate, initialize, compile, test package, verify, install, deploy
  D. Validation, initialize, compile, test, package, install verify, deploy
  C. Validate, initialize, compile, test package, verify, install, deploy

  ---

  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

• Question 33:

  Which pattern can a web API use to notify its client of state changes as soon as they occur?

  A. HTTP Webhock
  B. Shared database trigger
  C. Schedule Event Publisher
  D. ETL data load
  A. HTTP Webhock

  ---

  Explanation

  A web API can use HTTP Webhook to notify its client of state changes as soon as they occur. A webhook is an HTTP callback that allows an API to send real-time notifications to another system or application when an event happens. The client registers a URL with the API where it wants to receive notifications, and then the API sends an HTTP request to that URL with information about the event.

  References:https://docs.mulesoft.com/connectors/webhook/webhook-connector

• Question 34:

  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. Option A
  B. Option B
  C. Option C
  D. Option D
  E. Option E
  E. Option E

  ---

  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-thepom-file

• Question 35:

  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. Ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails
  C. Remove the Put requests from the Scatter-Getter and perform them sequentially
  D. None, the flow already exhibits idempotent behavior
  B. Ensure an error-handling flow performs corrective actions to roll back all changes if any leg of the Scatter-Gather fails

  ---

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

• Question 36:

  Which statement is true when working with correlation IDS?

  A. The HTTP Listener regenerates correlation IDs regardless of the HTTP request
  B. The Anypoint MQ Connector automatically propagates correlation IDS
  C. The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request
  D. The VM Connector does not automatically propagate correction IDs
  C. The HTTP Listener generates correlation IDS unless a correlation ID is received in the HTTP request

  ---

  Explanation

  When working with correlation IDs, the HTTP Listener generates correlation IDs unless a correlation ID is received in the HTTP request. In that case, it propagates the received correlation ID throughout the flow execution. Correlation IDs are used to track events across different flows or applications.

  References:https://docs.mulesoft.com/mule-runtime/4.3/about-mule-message#message-attributes

• Question 37:

  What is the MuleSoft recommended method to encrypt sensitive property data?

  A. The encryption key and sensitive data should be different for each environment
  B. The encryption key should be identical for all environments
  C. The encryption key should be identical for all environments and the sensitive data should be different for each environment
  D. The encryption key should be different for each environment and the sensitive data should be the same for all environments
  A. The encryption key and sensitive data should be different for each environment

  ---

  Explanation

  The MuleSoft recommended method to encrypt sensitive property data is to use the Secure Properties Tool that comes with Anypoint Studio. This tool allows encrypting properties files with a secret key and then decrypting them at runtime using the same key. The encryption key and sensitive data should be different for each environment to ensure security and avoid accidental exposure of sensitive data.

  References:https://docs.mulesoft.com/mule-runtime/4.3/secure-configuration-properties

• Question 38:

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

  A. A protocol
  B. The TLS version
  C. Anencryption algorithm
  D. The Public key format
  C. Anencryption algorithm

  ---

  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

• Question 39:

  A company with MuleSoft Titanium develops a Salesforce System API using MuleSoft out- of-the-box Salesforce Connector and deploys the API to CloudHub.

  Which steps provide the average number of requests and average response time of the Salesforce Connector?

  A. Access Anypoint Monitoring's built-in dashboard. Select a resource. Locate the information under the Connectors tab.
  B. Access Anypoint Monitoring's built-in dashboard Seclect a resource. Create a custom dashboard to retrieve the information.
  C. Access Anypoint Monitoring built-in dashboard. Select a resource. Locate the information under Log Manager
  D. Change the API Implementation to capture the information in the log. Retrieve the information from the log file.
  A. Access Anypoint Monitoring's built-in dashboard. Select a resource. Locate the information under the Connectors tab.

  ---

  Explanation

  To get the average number of requests and average response time of the Salesforce Connector, the developer should access Anypoint Monitoring's built-in dashboard, select a resource (such as an application or an API), and locate the information under the Connectors tab. The Connectors tab shows metrics for each connector used by the resource, such as average requests per minute, average response time, and failures.

  References:https://docs.mulesoft.com/monitoring/ built-in-dashboard-reference

• Question 40:

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

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

  ---

  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