Salesforce-MuleSoft-Developer-II Exam Practice Test Instant Access

Question 1

Two APIs are deployed to a two-node on-prem cluster. Due to a requirements change, the two APIs must communicate to exchange data asynchronously.

AIf the two APIs use the same domain, the VM Connector can be leveraged

BThe VM Connector is used to inter-application communication, so it is not possible to use the VM Connector

CInstead of using the VM Connector use <flow-ref>directly

DIt is not possible to use the VM Connector since the APIs are running in a cluster mode and each mode has it own set of VM Queues

Answer : A

To communicate asynchronously between two APIs deployed to a two-node on-prem cluster, the developer can use the VM Connector if the two APIs use the same domain. The VM Connector allows passing messages between different Mule applications within a single Mule runtime instance or across different instances using shared memory or persistent storage. If two APIs are deployed under the same domain, they can share resources such as VM queues and communicate asynchronously using VM Connector operations. Reference: https://docs.mulesoft.com/mule-runtime/4.3/vm-connector https://docs.mulesoft.com/mule-runtime/4.3/shared-resources

Question 2

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

AA database as a transactional outbox and an Until Successful router to retry any requests

BA Parallel for Each scope with each HTTP request wrapped in a Try scope

CScatter-Gather as central Saga orchestrator for all API request with compensating actions for failing routes

DVM queues as a reliability pattern with error handlers to roll back any requests

Answer : C

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. Reference: https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept https://docs.mulesoft.com/mule-runtime/4.3/saga

Question 3

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?

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.

Create a common-global-error-handler flow in all Mule Applications Refer to it flow-ref wherever needed.

CCreate 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

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. Reference: https://docs.mulesoft.com/mule-runtime/4.3/error-handling#global-error-handler

Question 4

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?