CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. MuleSoft
  5. MCIA-LEVEL-1

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

Page 33 of 62
PDF with 244 Questions

A manufacturing company is planning to deploy Mule applications to its own Azure Kubernetes Service infrastructure.
The organization wants to make the Mule applications more available and robust by deploying each Mule application to an isolated Mule runtime in a Docker container while managing all the Mule applications from the MuleSoft-hosted control plane.
What is the most idiomatic (used for its intended purpose) choice of runtime plane to meet these organizational requirements?

  1. Anypoint Platform Private Cloud Edition
  2. Anypoint Runtime Fabric
  3. CloudHub
  4. Anypoint Service Mesh

Answer(s): B


Reference:

https://blogs.mulesoft.com/dev-guides/how-to-tutorials/anypoint-runtime-fabric/



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?

  1. 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
  2. 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
  3. 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
  4. 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

Answer(s): C


Reference:

https://aws.amazon.com/blogs/compute/building-a-serverless-distributed-application- using-a-saga-orchestration-pattern/



As a part of project requirement, client will send a stream of data to mule application. Payload size can vary between 10mb to 5GB. Mule application is required to transform the data and send across multiple sftp servers. Due to the cost cuttings in the organization, mule application can only be allocated one worker with size of 0.2 vCore. As an integration architect , which streaming strategy you would suggest to handle this scenario?

  1. In-memory non repeatable stream
  2. File based non-repeatable stream
  3. In-memory repeatable stream
  4. File based repeatable storage

Answer(s): D

Explanation:

As the question says that data needs to be sent across multiple sftp serves , we cannot use non- repeatable streams. The non-repeatable strategy disables repeatable streams, which enables you to read an input stream only once.
You cant use in memory storage because with 0.2 vcore you will get only 1 GB of heap memory. Hence application will error out for file more than 1 GB.
Hence the correct option is file base repeatable stream.



Mule application muleA deployed in cloudhub uses Object Store v2 to share data across instances. As a part of new requirement , application muleB which is deployed in same region wants to access this Object Store.
Which of the following option you would suggest which will have minimum latency in this scenario?

  1. Object Store REST API
  2. Object Store connector
  3. Both of the above option will have same latency
  4. Object Store of one mule application cannot be accessed by other mule application.

Answer(s): A

Explanation:

V2 Rest API is recommended for on premise applications to access Object Store. It also comes with overhead of encryption and security of using rest api. With Object Store v2, the API call is localized to the same data center as the Runtime Manager app.
But in this case requirement is to access the OS of other mule application and not the same mule application.
You can configure a Mule app to use the Object Store REST API to store and retrieve values from an object store in another Mule app.
However, Object Store v2 is not designed for app-to-app communication.



Page 33 of 62



Post your Comments and Discuss MuleSoft MCIA-LEVEL-1 exam with other Community members:

sanath sekar commented on September 05, 2024
nice good good expirence with these dumps provided
Anonymous
upvote