Free MuleSoft Certified Integration Architect – Level 1 MAINTENANCE Exam MCIA-Level-1-Maintenance Exam Practice Test

Mule application is deployed to Customer Hosted Runtime. Asynchronous logging was implemented to improved throughput of the system. But it was observed over the period of time that few of the important exception log messages which were used to rollback transactions are not working as expected causing huge loss to the Organization. Organization wants to avoid these losses. Application also has constraints due to which they cant compromise on throughput much. What is the possible option in this case?

• Logging needs to be changed from asynchronous to synchronous
• External log appender needs to be used in this case
• Persistent memory storage should be used in such scenarios
• Mixed configuration of asynchronous or synchronous loggers should be used to log exceptions via synchronous way

A customer wants to use the mapped diagnostic context (MDC) and logging variables to enrich its logging and improve tracking by providing more context in the logs. The customer also wants to improve the throughput and lower the latency of message processing. As an Mulesoft integration architect can you advise, what should the customer implement to meet these requirements?

• Use synchronous logging and use pattern layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables
• Useasync logger at the level greater than INFO and use pattern layout with [%MDC] in the log4j2,xml configuration file and then configure the logging variables
• Useasync logger at the level equal to DEBUG orTRACEand use pattern layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables
• Use synchronous logging at the INFO DEBUG or Trace level and use pattern layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables

What best describes the Fully Qualified Domain Names (FQDNs), also known as DNS entries, created when a Mule application is deployed to the CloudHub Shared Worker Cloud?

• A fixed number of FQDNs are created, IRRESPECTIVE of the environment and VPC design
• The FQDNs are determined by the application name chosen, IRRESPECTIVE of the region
• The FQDNs are determined by the application name, but can be modified by an administrator after deployment
• The FQDNs are determined by both the application name and the region

An organization has deployed runtime fabric on an eight note cluster with performance profile. An API uses and non persistent object store for maintaining some of its state data. What will be the impact to the stale data if server crashes?

• State data is preserved
• State data is rolled back to a previously saved version
• State data is lost
• State data is preserved as long as more than one more is unaffected by the crash

An insurance company is implementing a MuleSoft API to get inventory details from the two vendors. Due to network issues, the invocations to vendor applications are getting timed-out intermittently. But the transactions are successful upon reprocessing What is the most performant way of implementing this requirement?

• Implement a scatter-gather scope to invoke the two vendor applications on two different route Use the Until-Successful scope to implement the retry mechanism for timeout errors on each route
• Implement a Choice scope to invoke the two vendor applications on two different route Use the try-catch scope to implement the retry mechanism for timeout errors on each route
• Implement a For-Each scope to invoke the two vendor applications Use until successful scope to implement the retry mechanism for the timeout errors
• Implement Round-Robin scope to invoke the two vendor applications on two different routes Use the Try-Catch scope to implement retry mechanism for timeout errors on each route

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

A company is designing a mule application to consume batch data from a partner's ftps server The data files have been compressed and then digitally signed using PGP. What inputs are required for the application to securely consumed these files?

• ATLS context Key Store requiring the private key and certificate for the company PGP public key of partner PGP private key for the company
• ATLS context first store containing a public certificate for partner ftps server and the PGP public key of the partner TLS contact Key Store containing the FTP credentials
• TLS context trust or containing a public certificate for the ftps server The FTP username and password The PGP public key of the partner
• The PGP public key of the partner The PGP private key for the company The FTP username and password

The ABC company has an Anypoint Runtime Fabric on VMs/Bare Metal (RTF-VM) appliance installed on its own customer-hosted AWS infrastructure. Mule applications are deployed to this RTF-VM appliance. As part of the company standards, the Mule application logs must be forwarded to an external log management tool (LMT). Given the company's current setup and requirements, what is the most idiomatic (used for its intended purpose) way to send Mule application logs to the external LMT?

• In RTF-VM, install and configure the external LTM's log-forwarding agent
• In RTF-VM, edit the pod configuration to automatically install and configure an Anypoint Monitoring agent
• In each Mule application, configure custom Log4j settings
• In RTF-VM. configure the out-of-the-box external log forwarder

A corporation has deployed multiple mule applications implementing various public and private API's to different cloudhub workers. These API's arc Critical applications that must be highly available and in line with the reliability SLA as defined by stakeholders. How can API availability (liveliness or readiness) be monitored so that Ops team receives outage notifications?

• Enable monitoring of individual applications from Anypoint monitoring
• Configure alerts with failure conditions in runtime manager
• Configure alerts failure conditions in API manager
• Use any point functional monitoring test API's functional behavior

Which of the below requirements prevent the usage of Anypoint MQ in a company's network? (Choose two answers)

• single message payload can be up to 15 MB
• payloads must be encrypted
• the message broker must be hosted on premises
• support for point-to-point messaging
• ability for a third party outside the company's network to consume events from the queue