MCIA-Level-1-Maintenance Exam Questions Tutorials

MuleSoft Certified Integration Architect - Level 1 MAINTENANCE Questions and Answers

Question 9

How does timeout attribute help inform design decisions while using JMS connector listening for incoming messages in an extended architecture (XA) transaction?

Options:

After the timeout is exceeded, stale JMS consumer threads are destroyed and new threads are created

The timeout specifies the time allowed to pass between receiving JMS messages on the same JMS connection and then after the timeout new JMS connection is established

The time allowed to pass between committing the transaction and the completion of the mule flow and then after the timeout flow processing triggers an error

The timeout defines the time that is allowed to pass without the transaction ending explicitly and after the timeout expires, the transaction rolls back

Question 10

A company is implementing a new Mule application that supports a set of critical functions driven by a rest API enabled, claims payment rules engine hosted on oracle ERP. As designed the mule application requires many data transformation operations as it performs its batch processing logic.

The company wants to leverage and reuse as many of its existing java-based capabilities (classes, objects, data model etc.) as possible

What approach should be considered when implementing required data mappings and transformations between Mule application and Oracle ERP in the new Mule application?

Options:

Create a new metadata RAML classes in Mule from the appropriate Java objects and then perform transformations via Dataweave

From the mule application, transform via theXSLT model

Transform by calling any suitable Java class from Dataweave

Invoke any of the appropriate Java methods directly, create metadata RAML classes and then perform required transformations via Dataweave

Question 11

Customer has deployed mule applications to different customer hosted mule run times. Mule applications are managed from Anypoint platform.

What needs to be configured to monitor these Mule applications from Anypoint monitoring and what sends monitoring data to Anypoint monitoring?

Options:

Enable monitoring of individual applications from runtime manager application settings

Runtime manager agent sends monitoring data from the mule applications to Anypoint monitoring

Install runtime manager agent on each mule runtime

Runtime manager agent since monitoring data from the mule applications to Anypoint monitoring

Anypoint monitoring agent on each mule runtime

Anypoint monitoring agent sends monitoring data from the mule applications to Anypoint monitoring

By default, Anypoint monitoring agent will be installed on each Mule run time

Anypoint Monitoring agent automatically sends monitoring data from the Mule applications to Anypoint monitoring

Question 12

Organization wants to achieve high availability goal for Mule applications in customer hosted runtime plane. Due to the complexity involved, data cannot be shared among of different instances of same Mule application. What option best suits to this requirement considering high availability is very much critical to the organization?

Options:

The cluster can be configured

Use third party product to implement load balancer

High availability can be achieved only in CloudHub

Use persistent object store

Answer:

Explanation:

Explanation

High availability is about up-time of your application

A) High availability can be achieved only in CloudHub isn't correct statement. It can be achieved in customer hosted runtime planes as well

B) An object store is a facility for storing objects in or across Mule applications. Mule runtime engine (Mule) uses object stores to persist data for eventual retrieval. It can be used for disaster recovery but not for High Availability. Using object store can't guarantee that all instances won't go down at once. So not an appropriate choice.

Reference: [Reference: https://docs.mulesoft.com/mule-runtime/4.3/mule-object-stores, C) High availability can be achieved by below two models for on-premise MuleSoft implementations., 1) Mule Clustering – Where multiple Mule servers are available within the same cluster environment and the routing of requests will be done by the load balancer. A cluster is a set of up to eight servers that act as a single deployment target and high-availability processing unit. Application instances in a cluster are aware of each other, share common information, and synchronize statuses. If one server fails, another server takes over processing applications. A cluster can run multiple applications. ( refer left half of the diagram), In given scenario, it's mentioned that 'data cannot be shared among of different instances'. So this is not a correct choice., Reference: https://docs.mulesoft.com/runtime-manager/cluster-about, 2) Load balanced standalone Mule instances – The high availability can be achieved even without cluster, with the usage of third party load balancer pointing requests to different Mule servers. This approach does not share or synchronize data between Mule runtimes. Also high availability achieved as load balanced algorithms can be implemented using external load balancer. ( refer right half of the diagram), Graphical user interface, diagram, application Description automatically generated, ]

Black Friday Special 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: save70

MCIA-Level-1-Maintenance Exam Questions Tutorials

MuleSoft Certified Integration Architect - Level 1 MAINTENANCE Questions and Answers

Options:

Answer:

Options:

Answer:

Options:

Answer:

Options:

Answer:

Explanation:

CompTIA

Fortinet

Microsoft

Salesforce