MCIA-Level-1-Maintenance Exam Dumps - MuleSoft Certified Integration Architect - Level 1 MAINTENANCE

Go to page:

Question # 4

A project team is working on an API implementation using the RAML definition as a starting point. The team has updated the definition to include new operations and has published a new version to exchange. Meanwhile another team is working on a mule application consuming the same API implementation.

During the development what has to be performed by the mule application team to take advantage of the newly added operations?

Scaffold the client application with the new definition

Scaffold API implementation application with the new definition

Update the REST connector from exchange in the client application

Update the API connector in the API implementation and publish to exchange

Full Access

Question # 5

A company is planning to migrate its deployment environment from on-premises cluster to a Runtime Fabric (RTF) cluster. It also has a requirement to enable Mule applications deployed to a Mule runtime instance to store and share data across application replicas and restarts.

How can these requirements be met?

Anypoint object store V2 to share data between replicas in the RTF cluster

Install the object store pod on one of the cluster nodes

Configure Persistence Gateway in any of the servers using Mule Object Store

Configure Persistent Gateway at the RTF

Full Access

Question # 6

The AnyAirline organization's passenger reservations center is designing an integration solution that combines invocations of three different System APIs (bookFlight, bookHotel, and bookCar) in a business transaction. Each System API makes calls to a single database.

The entire business transaction must be rolled back when at least one of the APIs fails.

What is the most idiomatic (used for its intended purpose) way to integrate these APIs in near real-time that provides the best balance of consistency, performance, and reliability?

Implement eXtended Architecture (XA) transactions between the API implementations

Coordinate between the API implementations using a Saga pattern

Implement caching in each API implementation to improve performance

Implement local transactions within each API implementation

Configure each API implementation to also participate in the same eXtended Architecture (XA) transaction

Implement caching in each API implementation to improve performance

Implement local transactions in each API implementation

Coordinate between the API implementations using a Saga pattern

Apply various compensating actions depending on where a failure occurs

Implement an eXtended Architecture (XA) transaction manager in a Mule application using a Saga pattern

Connect each API implementation with the Mule application using XA transactions

Apply various compensating actions depending on where a failure occurs

Full Access

Question # 7

A global, high-volume shopping Mule application is being built and will be deployed to CloudHub. To improve performance, the Mule application uses a Cache scope that maintains cache state in a CloudHub object store. Web clients will access the Mule application over HTTP from all around the world, with peak volume coinciding with business hours in the web client's geographic location. To achieve optimal performance, what Anypoint Platform region should be chosen for the CloudHub object store?

Choose the same region as to where the Mule application is deployed

Choose the US-West region, the only supported region for CloudHub object stores

Choose the geographically closest available region for each web client

Choose a region that is the traffic-weighted geographic center of all web clients

Full Access

Answer:

Explanation:

Explanation

CloudHub object store should be in same region where the Mule application is deployed. This will give optimal performance.

Before learning about Cache scope and object store in Mule 4 we understand what is in general Caching is and other related things.

WHAT DOES â€œCACHINGâ€ MEAN?

Caching is the process of storing frequently used data in memory, file system or database which saves processing time and load if it would have to be accessed from original source location every time.

In computing, a cache is a high-speed data storage layer which stores a subset of data, so that future requests for that data are served up faster than is possible by accessing the dataâ€™s primary storage location. Caching allows you to efficiently reuse previously retrieved or computed data.

How does Caching work?

The data in a cache is generally stored in fast access hardware such as RAM (Random-access memory) and may also be used in correlation with a software component. A cacheâ€™s primary purpose is to increase data retrieval performance by reducing the need to access the underlying slower storage layer.

Caching in MULE 4

In Mule 4 caching can be achieved in mule using cache scope and/or object-store. Cache scope internally uses Object Store to store the data.

What is Object Store

Object Store lets applications store data and states across batch processes, Mule components, and applications, from within an application. If used on cloud hub, the object store is shared between applications deployed on Cluster.

Cache Scope is used in below-mentioned cases:

â— Need to store the whole response from the outbound processor

â— Data returned from the outbound processor does not change very frequently

â— As Cache scope internally handle the cache hit and cache miss scenarios it is more readable

Object Store is used in below-mentioned cases:

â— Need to store custom/intermediary data

â— To store watermarks

â— Sharing the data/stage across applications, schedulers, batch.

If CloudHub object store is in same region where the Mule application is deployed it will aid in fast access of data and give optimal performance.

Question # 8

A company is building an application network and has deployed four Mule APIs: one experience API, one process API, and two system APIs. The logs from all the APIs are aggregated in an external log aggregation tool. The company wants to trace messages that are exchanged between multiple API implementations. What is the most idiomatic (based on its intended use) identifier that should be used to implement Mule event tracing across the multiple API implementations?

Mule event ID

Mule correlation ID

Client's IP address

DataWeave UUID

Full Access