Salesforce Certified MuleSoft Platform Integration Architect (Mule-Arch-202) Exam Questions Instant Access

Question 1

An integration Mule application is deployed to a customer-hosted multi-node Mule 4 runtime duster. The Mule application uses a Listener operation of a JMS connector to receive incoming messages from a JMS queue.

How are the messages consumed by the Mule application?

ADepending on the JMS provider's configuration, either all messages are consumed by ONLY the primary cluster node or else ALL messages are consumed by ALL cluster nodes

BRegardless of the Listener operation configuration, all messages are consumed by ALL cluster nodes

CDepending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node

DRegardless of the Listener operation configuration, all messages are consumed by ONLY the primary cluster node

Answer : C

Correct answer is Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node

For applications running in clusters, you have to keep in mind the concept of primary node and how the connector will behave. When running in a cluster, the JMS listener default behavior will be to receive messages only in the primary node, no matter what kind of destination you are consuming from. In case of consuming messages from a Queue, you'll want to change this configuration to receive messages in all the nodes of the cluster, not just the primary.

This can be done with the primaryNodeOnly parameter:

<jms:listener config-ref='config' destination='${inputQueue}' primaryNodeOnly='false'/>

Question 2

Refer to the exhibit.

A Mule application is deployed to a cluster of two customer-hosted Mute runtimes. The Mute application has a flow that polls a database and another flow with an HTTP Listener.

HTTP clients send HTTP requests directly to individual cluster nodes.

What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has railed, but before that node is restarted?

ADatabase polling continues Only HTTP requests sent to the remaining node continue to be accepted

BDatabase polling stops All HTTP requests continue to be accepted

CDatabase polling continues All HTTP requests continue to be accepted, but requests to the failed node Incur increased latency

DDatabase polling stops All HTTP requests are rejected

Answer : A

Correct answer is Database polling continues Only HTTP requests sent to the remaining node continue to be accepted. : Architecture descripted in the question could be described as follows.When node 1 is down , DB polling will still continue via node 2 . Also requests which are coming directly to node 2 will also be accepted and processed in BAU fashion. Only thing that wont work is when requests are sent to Node 1 HTTP connector. The flaw with this architecture is HTTP clients are sending HTTP requests directly to individual cluster nodes. By default, clustering Mule runtime engines ensures high system availability. If a Mule runtime engine node becomes unavailable due to failure or planned downtime, another node in the cluster can assume the workload and continue to process existing events and messages

Question 3

An organization has deployed runtime fabric on an eight note cluster with performance profile. An API uses and non persistent object store for maintaining some of its state dat

a. What will be the impact to the stale data if server crashes?

AState data is preserved

BState data is rolled back to a previously saved version

CState data is lost

DState data is preserved as long as more than one more is unaffected by the crash

Answer : C

Question 4

Refer to the exhibit.

The HTTP Listener and the Logger are being handled from which thread pools respectively?

ACPU_INTENSIVE and Dedicated Selector pool

BUBER and NONBLOCKING

CShared Selector Pool and CPU LITE

DBLOCKING _IO and UBER

Answer : C

Question 5

A Mule application contains a Batch Job scope with several Batch Step scopes. The Batch Job scope is configured with a batch block size of 25.

A payload with 4,000 records is received by the Batch Job scope.

When there are no errors, how does the Batch Job scope process records within and between the Batch Step scopes?

AThe Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records
Each Batch Step scope is invoked with one record in the payload of the received Mule event
For each Batch Step scope, all 25 records within a block are processed in parallel
All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope

BThe Batch Job scope processes each record block sequentially, one at a time
Each Batch Step scope is invoked with one record in the payload of the received Mule event
For each Batch Step scope, all 25 records within a block are processed sequentially, one at a time
All 4000 records must be completed before the blocks of records are available to the next Batch Step scope

CThe Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records
Each Batch Step scope is invoked with one record in the payload of the received Mule event
For each Batch Step scope, all 25 records within a block are processed sequentially, one record at a time
All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope

DThe Batch Job scope processes multiple record blocks in parallel
Each Batch Step scope is invoked with a batch of 25 records in the payload of the received Mule event
For each Batch Step scope, all 4000 records are processed in parallel
Individual records can jump ahead to the next Batch Step scope before the rest of the records finish processing in the current Batch Step scope

Answer : A

Question 6

Following MuleSoft best practices, what MuleSoft runtime deployment option best meets the company's goals to begin its digital transformation journey?

ARuntime Fabric on VMs/bare metal

BCloudHub runtimes

CCustomer-hosted runtimes provisioned by a MuleSoft services partner

DCustomer-hosted self-provisioned runtimes

Answer : A

Question 7

An organization uses a set of customer-hosted Mule runtimes that are managed using the Mulesoft-hosted control plane. What is a condition that can be alerted on from Anypoint Runtime Manager without any custom components or custom coding?

AWhen a Mule runtime on a given customer-hosted server is experiencing high memory consumption during certain periods

BWhen an SSL certificate used by one of the deployed Mule applications is about to expire

CWhen the Mute runtime license installed on a Mule runtime is about to expire

DWhen a Mule runtime's customer-hosted server is about to run out of disk space

Answer : A

Correct answer is When a Mule runtime on a given customer-hosted server is experiencing high memory consumption during certain periods Using Anypoint Monitoring, you can configure two different types of alerts: Basic alerts for servers and Mule apps Limit per organization: Up to 50 basic alerts for users who do not have a Titanium subscription to Anypoint Platform You can set up basic alerts to trigger email notifications when a metric you are measuring passes a specified threshold. You can create basic alerts for the following metrics for servers or Mule apps: For on-premises servers and CloudHub apps: * CPU utilization * Memory utilization * Thread count Advanced alerts for graphs in custom dashboards in Anypoint Monitoring. You must have a Titanium subscription to use this feature. Limit per organization: Up to 20 advanced alerts