Online Access Free MCIA-Level-1-Maintenance Exam Questions

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

• A.An XA transaction handles the largest number of requests in the shortest time
• B.An XA transaction automatically rolls back operations against both database systems if any operation falls
• C.An XA transaction synchronizes the database systems with the least amount of Mule configuration or coding
• D.An XA transaction writes to both database systems as fast as possible

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?

• A.Transform by calling any suitable Java class from Dataweave
• B.Invoke any of the appropriate Java methods directly, create metadata RAML classes and then perform required transformations via Dataweave
• C.From the mule application, transform via theXSLT model
• D.Create a new metadata RAML classes in Mule from the appropriate Java objects and then perform transformations via Dataweave

A company wants its users to log in to Anypoint Platform using the company's own internal user credentials.
To achieve this, the company needs to integrate an external identity provider (IdP) with the company's Anypoint Platform master organization, but SAML 2.0 CANNOT be used. Besides SAML 2.0, what single-sign-on standard can the company use to integrate the IdP with their Anypoint Platform master organization?

• A.OAuth 2.0
• B.SAML 1.0
• C.OpenID Connect
• D.Basic Authentication

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?

• A.High availability can be achieved only in CloudHub
• B.Use persistent object store
• C.Use third party product to implement load balancer
• D.The cluster can be configured

An external web UI application currently accepts occasional HTTP requests from client web browsers to change (insert, update, or delete) inventory pricing information in an inventory system's database. Each inventory pricing change must be transformed and then synchronized with multiple customer experience systems in near real-time (in under 10 seconds). New customer experience systems are expected to be added in the future.
The database is used heavily and limits the number of SELECT queries that can be made to the database to 10 requests per hour per user.
What is the most scalable, idiomatic (used for its intended purpose), decoupled. reusable, and maintainable integration mechanism available to synchronize each inventory pricing change with the various customer experience systems in near real-time?

• A.Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the ID attribute set to an appropriate database column In the same flow, use a Batch Job scope to publish transformed Inventory-pricing records to an Anypoint MQ queue Write other Mule applications to subscribe to the Anypoint MQ queue, transform each received message, and then update the Mule application's corresponding customer experience system(s)
• B.Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the watermark attribute set to an appropriate database column In the same now, use a Scatter-Gather to call each customer experience system's REST API with transformed inventory-pricing records
• C.Add a trigger to the inventory-pricing database table so that for each change to the inventory pricing database, a stored procedure is called that makes a REST call to a Mule application Write the Mule application to publish each Mule event as a message to an Anypoint MQ exchange Write other Mule applications to subscribe to the Anypoint MQ exchange, transform each received message, and then update the Mule application's corresponding customer experience system(s)
• D.Replace the external web UI application with a Mule application to accept HTTP requests from client web browsers In the same Mule application, use a Batch Job scope to test if the database request will succeed, aggregate pricing changes within a short time window, and then update both the inventory pricing database and each customer experience system using a Parallel For Each scope