QUESTION: 69

An organization will deploy Mule applications to Cloudhub, Business requirements mandate that all application logs be stored ONLY in an external splunk consolidated logging service and NOT in Cloudhub.
In order to most easily store Mule application logs ONLY in Splunk, how must Mule application logging be configured in Runtime Manager, and where should the log4j2 splunk appender be defined?

Keep the default logging configuration in RuntimeManager
Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manager to support at Mule application deployments.
Disable Cloudhub logging in Runtime Manager
Define the splunk appender in EACH Mule application’s log4j2.xml file
Disable Cloudhub logging in Runtime Manager
Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manger to support at Mule application deployments.
Keep the default logging configuration in Runtime Manager Define the Splunk appender in EACH Mule application log4j2.xml file

Answer(s): B

Explanation:

By default, CloudHub replaces a Mule application's log4j2.xml file with a CloudHub log4j2.xml file. In CloudHub, you can disable the CloudHub provided Mule application log4j2 file. This allows integrating Mule application logs with custom or third-party log management systems

Reveal Solution Next Question

QUESTION: 70

A Mule application is synchronizing customer data between two different database systems.
What is the main benefit of using XA transaction over local transactions to synchronize these two database system?

Reduce latency
Increase throughput
Simplifies communincation
Ensure consistency

Answer(s): D

Explanation:

* XA transaction add tremendous latency so "Reduce Latency" is incorrect option XA transactions define "All or No" commit protocol.
* Each local XA resource manager supports the A.C.I.D properties (Atomicity, Consistency, Isolation, and Durability).

So correct choice is "Ensure consistency"

Reference:

https://docs.mulesoft.com/mule-runtime/4.3/xa-transactions

Reveal Solution Next Question

QUESTION: 71

A mule application is deployed to a Single Cloudhub worker and the public URL appears in Runtime Manager as the APP URL.
Requests are sent by external web clients over the public internet to the mule application App url. Each of these requests routed to the HTTPS Listener event source of the running Mule application.
Later, the DevOps team edits some properties of this running Mule application in Runtime Manager. Immediately after the new property values are applied in runtime manager, how is the current Mule application deployment affected and how will future web client requests to the Mule application be handled?

Cloudhub will redeploy the Mule application to the OLD Cloudhub worker
New web client requests will RETURN AN ERROR until the Mule application is redeployed to the OLD Cloudhub worker
CloudHub will redeploy the Mule application to a NEW Cloudhub worker
New web client requests will RETURN AN ERROR until the NEW Cloudhub worker is available
Cloudhub will redeploy the Mule application to a NEW Cloudhub worker
New web client requests are ROUTED to the OLD Cloudhub worker until the NEW Cloudhub worker is available.
Cloudhub will redeploy the mule application to the OLD Cloudhub worker
New web client requests are ROUTED to the OLD Cloudhub worker BOTH before and after the Mule application is redeployed.

Answer(s): C

Explanation:

CloudHub supports updating your applications at runtime so end users of your HTTP APIs experience zero downtime. While your application update is deploying, CloudHub keeps the old version of your application running. Your domain points to the old version of your application until the newly uploaded version is fully started. This allows you to keep servicing requests from your old application while the new version of your application is starting.

Reveal Solution Next Question

QUESTION: 72

An external REST client periodically sends an array of records in a single POST request to a Mule application API endpoint.
The Mule application must validate each record of the request against a JSON schema before sending it to a downstream system in the same order that it was received in the array
Record processing will take place inside a router or scope that calls a child flow. The child flow has its own error handling defined. Any validation or communication failures should not prevent further processing of the remaining records.
To best address these requirements what is the most idiomatic(used for it intended purpose) router or scope to used in the parent flow, and what type of error handler should be used in the child flow?

First Successful router in the parent flow
On Error Continue error handler in the child flow
For Each scope in the parent flow
On Error Continue error handler in the child flow
Parallel For Each scope in the parent flow
On Error Propagate error handler in the child flow
Until Successful router in the parent flow
On Error Propagate error handler in the child flow

Answer(s): B

Explanation:

Correct answer is For Each scope in the parent flow On Error Continue error handler in the child flow. You can extract below set of requirements from the question a) Records should be sent to downstream system in the same order that it was received in the array b) Any validation or communication failures should not prevent further processing of the remaining records First requirement can be met using For Each scope in the parent flow and second requirement can be met using On Error Continue scope in child flow so that error will be suppressed.

Reveal Solution Next Question

Free MCIA-LEVEL-1 Exam Braindumps (page: 18)

QUESTION: 69

Explanation:

QUESTION: 70

Explanation:

Reference:

QUESTION: 71

Explanation:

QUESTION: 72

Explanation: