Salesforce SALESFORCE-MULESOFT-DEVELOPER-II Online Practice Questions and Exam Preparation

Salesforce SALESFORCE-MULESOFT-DEVELOPER-II Online Questions & Answers

• Question 21:

  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/Reference:

  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. https://docs.mulesoft.com/muleruntime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime.3/error-handling

• Question 22:

  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/Reference:

  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.

  Reference:

  https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

• Question 23:

  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.xml file to output the variable as part of the message pattern
  C. Create a custom XML SDK component to wrap the logger processor and automatically add the order ID within the connector
  D. Use the Tracing module to set logging variables with a Mapped Diagnostic Context
  D. Use the Tracing module to set logging variables with a Mapped Diagnostic Context

  ---

  Explanation/Reference:

  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. https:// docs.mulesoft.com/tracing-module.0/tracingmodule-reference#set-logging-variables

• Question 24:

  Refer to the exhibit.

  

  When creating a new project, which API implementation allows for selecting the correct API version and scaffolding the flows from the API specification?

  A. Import a published API
  B. Generate a local RAML from anypoint Studio
  C. Download RAML from Design Center
  D. Import RAML from local file
  C. Download RAML from Design Center

  ---

  Explanation/Reference:

  To create a new project that selects the correct API version and scaffolds the flows from the API specification, the developer should import a published API. This option allows importing an API specification that has been published to Anypoint Exchange or Design Center, and selecting a specific version of that API specification. The developer can also choose to scaffold flows based on that API specification. https://docs.mulesoft.com/ apikit.x/apikit-4-new-project-task

• Question 25:

  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 validatecustomer'' 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/Reference:

  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.

  Reference:

  https://docs.mulesoft.com/mule-runtime.3/until-successful-scope

• Question 26:

  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/Reference:

  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. https://docs.mulesoft.com/api- manager.x/policies-policy-order

• Question 27:

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

  ---

  Explanation/Reference:

  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.

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

• Question 28:

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

  ---

  Explanation/Reference:

  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.

  Reference:

  https://docs.mulesoft.com/runtime-manager/runtime-manager-agent-for-mule4#properties-tab

• Question 29:

  A Flight Management System publishes gate change notification events whenever a flight's arrival gate changes. Other systems, including Baggage Handler System. Inflight Catering System and Passenger Notifications System, must each

  asynchronously receive the same gate change notification to process the event according.

  Which configuration is required in Anypoint MQ to achieve this publish/subscribe model?

  A. Publish each client subscribe directly to the exchange.Have each client subscribe directly to the queue.
  B. Publish the gate change notification to an Anypoint MC queue Have each client subscribe directly to the queue
  C. Publish the gate change notification to an Anypoint MQ queue. Create different anypoint MQ exchange meant for each of the other subscribing systems Bind the queue with each of the exchanges
  D. Publish the gate change notification to an Anypoint MQ exchanhe. Create different Anypoint MQ queues meant for each of the other subscribing systems. Bind the exchange with each of the queues.
  D. Publish the gate change notification to an Anypoint MQ exchanhe. Create different Anypoint MQ queues meant for each of the other subscribing systems. Bind the exchange with each of the queues.

  ---

  Explanation/Reference:

  To achieve a publish/subscribe model using Anypoint MQ, where each system receives the same gate change notification event, the developer should publish the gate change notification to an Anypoint MQ exchange, create different Anypoint MQ queues meant for each of the other subscribing systems, and bind the exchange with each of the queues. An exchange is a message routing agent that can send messages to different queues based on predefined criteria. By binding an exchange with multiple queues, each queue receives a copy of every message sent to that exchange. Therefore, each system can subscribe to its own queue and receive every gate change notification event. https://docs.mulesoft.com/anypoint-mq.x/anypoint-mq-exchanges

• Question 30:

  A developer is working on a project that requires encrypting all data before sending it to a backend application. To accomplish this, the developer will use PGP encryption in the Mule 4 Cryptography module. What is required to encrypt the data before sending it to the backend application?

  A. The application needs to configure HTTPS TLS context information to encrypt the data
  B. The application needs to both the private and public keys to encrypt the data
  C. The application needs the public key from the backend service to encrypt the data
  D. The application needs the private key from the backend service to encrypt the data
  C. The application needs the public key from the backend service to encrypt the data

  ---

  Explanation/Reference:

  To encrypt the data before sending it to the backend application using PGP encryption, the application needs the public key from the backend service. PGP encryption uses a public-key cryptography system, which means that each party has a pair of keys: a public key and a private key. The public key is used to encrypt data, and the private key is used to decrypt data. Therefore, to encrypt data for a specific recipient (the backend service), the application needs to use the recipient's public key. The recipient can then use its own private key to decrypt the data. Reference: https://docs.mulesoft.com/mule-runtime.3/cryptography-pgp