[2023] Valid MCIA-Level-1-Maintenance test answers & MuleSoft MCIA-Level-1-Maintenance exam pdf [Q21-Q45]

NO.21 A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity. The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms. If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API’s desired SLA?

Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete

Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds

Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries

No timeout is possible to meet the upstream API’s desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

Explanation
Before we answer this question , we need to understand what median (50th percentile) and 80th percentile means. If the 50th percentile (median) of a response time is 500ms that means that 50% of my transactions are either as fast or faster than 500ms.
If the 90th percentile of the same transaction is at 1000ms it means that 90% are as fast or faster and only 10% are slower. Now as per upstream SLA , 99th percentile is 800 ms which means 99% of the incoming requests should have response time less than or equal to 800 ms. But as per one of the backend API , their 95th percentile is 1000 ms which means that backend API will take 1000 ms or less than that for 95% of. requests.
As there are three API invocation from upstream API , we can not conclude a timeout that can be set to meet the desired SLA as backend SLA’s do not support it.
Let see why other answers are not correct.
1) Do not set a timeout –> This can potentially violate SLA’s of upstream API
2) Set a timeout of 100 ms; —> This will not work as backend API has 100 ms as median meaning only 50% requests will be answered in this time and we will get timeout for 50% of the requests. Important thing to note here is, All APIs need to be executed sequentially, so if you get timeout in first API, there is no use of going to second and third API. As a service provider you wouldn’t want to keep 50% of your consumers dissatisfied. So not the best option to go with.
*To quote an example: Let’s assume you have built an API to update customer contact details.
– First API is fetching customer number based on login credentials
– Second API is fetching Info in 1 table and returning unique key
– Third API, using unique key provided in second API as primary key, updating remaining details
* Now consider, if API times out in first API and can’t fetch customer number, in this case, it’s useless to call API 2 and 3 and that is why question mentions specifically that all APIs need to be executed sequentially.
3) Set a timeout of 50 ms –> Again not possible due to the same reason as above Hence correct answer is No timeout is possible to meet the upstream API’s desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

NO.22 An insurance provider is implementing Anypoint platform to manage its application infrastructure and is using the customer hosted runtime for its business due to certain financial requirements it must meet. It has built a number of synchronous API’s and is currently hosting these on a mule runtime on one server These applications make use of a number of components including heavy use of object stores and VM queues.
Business has grown rapidly in the last year and the insurance provider is starting to receive reports of reliability issues from its applications.
The DevOps team indicates that the API’s are currently handling too many requests and this is over loading the server. The team has also mentioned that there is a significant downtime when the server is down for maintenance.
As an integration architect, which option would you suggest to mitigate these issues?

Add a load balancer and add additional servers in a server group configuration

Add a load balancer and add additional servers in a cluster configuration

Increase physical specifications of server CPU memory and network

Change applications by use an event-driven model

NO.23 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

NO.24 A company is planning to extend its Mule APIs to the Europe region. Currently all new applications are deployed to Cloudhub in the US region following this naming convention
{API name}-{environment}. for example, Orders-SAPI-dev, Orders-SAPI-prod etc.
Considering there is no network restriction to block communications between API’s, what strategy should be implemented in order to apply the same new API’s running in the EU region of CloudHub as well to minimize latency between API’s and target users and systems in Europe?

Set region property to Europe (eu-de) in API manager for all the mule application No need to change the naming convention

Set region property to Europe (eu-de) in API manager for all the mule application Change the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users

Set region property to Europe (eu-de) in runtime manager for all the mule application No need to change the naming convention

Set region property to Europe (eu-de) in runtime manager for all the mule application Change the naming convention to {API name}-{environment}-{region} and communicate this change to the consuming applications and users

NO.25 What condition requires using a CloudHub Dedicated Load Balancer?

When cross-region load balancing is required between separate deployments of the same Mule application

When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes

When API invocations across multiple CloudHub workers must be load balanced

When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

NO.26 What is a key difference between synchronous and asynchronous logging from Mule applications?

Synchronous logging writes log messages in a single logging thread but does not block the Mule event being processed by the next event processor

Asynchronous logging can improve Mule event processing throughput while also reducing the processing time for each Mule event

Asynchronous logging produces more reliable audit trails with more accurate timestamps

Synchronous logging within an ongoing transaction writes log messages in the same thread that processes the current Mule event

NO.27 A trading company handles millions of requests a day. Due to nature of its business, it requires excellent performance and reliability within its application.
For this purpose, company uses a number of event-based API’s hosted on various mule clusters that communicate across a shared message queue sitting within its network.
Which method should be used to meet the company’s requirement for its system?

XA transactions and XA connected components

JMS transactions

JMS manual acknowledgements with a reliability pattern

VM queues with reliability pattern

NO.28 A mule application uses an HTTP request operation to involve an external API.
The external API follows the HTTP specification for proper status code usage.
What is possible cause when a 3xx status code is returned to the HTTP Request operation from the external API?

The request was not accepted by the external API

The request was Redirected to a different URL by the external API

The request was NOT RECEIVED by the external API

The request was ACCEPTED by the external API

NO.29 As a part of business requirement , old CRM system needs to be integrated using Mule application. CRM system is capable of exchanging data only via SOAP/HTTP protocol. As an integration architect who follows API led approach , what is the the below step you will perform so that you can share document with CRM team?

Create RAML specification using Design Center

Create SOAP API specification using Design Center

Create WSDL specification using text editor

Create WSDL specification using Design Center

NO.30 A mule application designed to fulfil two requirements
a) Processing files are synchronously from an FTPS server to a back-end database using VM intermediary queues for load balancing VM events b) Processing a medium rate of records from a source to a target system using batch job scope Considering the processing reliability requirements for FTPS files, how should VM queues be configured for processing files as well as for the batch job scope if the application is deployed to Cloudhub workers?

Use Cloud hub persistent queues for FTPS files processing
There is no need to configure VM queues for the batch jobs scope as it uses by default the worker’s disc for VM queueing

Use Cloud hub persistent VM queue for FTPS file processing
There is no need to configure VM queues for the batch jobs scope as it uses by default the worker’s JVM memory for VM queueing

Use Cloud hub persistent VM queues for FTPS file processing
Disable VM queue for the batch job scope

Use VM connector persistent queues for FTPS file processing Disable VM queue for the batch job scope

NO.31 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

NO.32 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?

An XA transaction synchronizes the database systems with the least amount of Mule configuration or coding

An XA transaction handles the largest number of requests in the shortest time

An XA transaction automatically rolls back operations against both database systems if any operation falls

An XA transaction writes to both database systems as fast as possible

NO.33 A Mule application is being designed for deployment to a single CloudHub worker. The Mule application will have a flow that connects to a SaaS system to perform some operations each time the flow is invoked.
The SaaS system connector has operations that can be configured to request a short-lived token (fifteen minutes) that can be reused for subsequent connections within the fifteen minute time window. After the token expires, a new token must be requested and stored.
What is the most performant and idiomatic (used for its intended purpose) Anypoint Platform component or service to use to support persisting and reusing tokens in the Mule application to help speed up reconnecting the Mule application to the SaaS application?

Nonpersistent object store

Persistent object store

Variable

Database

NO.34 A company is designing an integration Mule application to process orders by submitting them to a back-end system for offline processing. Each order will be received by the Mule application through an HTTP5 POST and must be acknowledged immediately.
Once acknowledged the order will be submitted to a back-end system. Orders that cannot be successfully submitted due to the rejections from the back-end system will need to be processed manually (outside the banking system).
The mule application will be deployed to a customer hosted runtime and will be able to use an existing ActiveMQ broker if needed. The ActiveMQ broker is located inside the organization’s firewall. The back-end system has a track record of unreliability due to both minor network connectivity issues and longer outages.
Which combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the back-end system while supporting but minimizing manual order processing?

One or more On Error scopes to assist calling the back-end system An Untill successful scope containing VM components for long retries A persistent dead-letter VM queue configure in Cloud hub

An Until Successful scope to call the back-end system One or more ActiveMQ long-retry queues One or more ActiveMQ dead-letter queues for manual processing

One or more on-Error scopes to assist calling the back-end system one or more ActiveMQ long-retry queues A persistent dead-letter Object store configuration in the CloudHub object store service

A batch job scope to call the back in system An Untill successful scope containing Object Store components for long retries. A dead-letter object store configured in the Mule application

NO.35 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

NO.36 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

NO.37 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

NO.38 Which Salesforce API is invoked to deploy, retrieve, create or delete customization information such as custom object definitions using a Mule Salesforce connector in a Mule application?

Metadata API

REST API

SOAP API

Bulk API

NO.39 In one of the critical payment related mule application, transaction is being used . As an enhancement to implementation , scatter gather route is introduced which is also the part of transaction group. Scatter gather route has 4 routes.
What will be the behavior of the Mule application in case of error occurs in 4th route of the scatter-gather router and transaction needs to be rolled back?

Only errored route will be rolled back

All routes will be rolled back

Scatter Gather router cannot be part of transaction

NO.40 An organization is designing Mule application which connects to a legacy backend. It has been reported that backend services are not highly available and experience downtime quite often. As an integration architect which of the below approach you would propose to achieve high reliability goals?

Alerts can be configured in Mule runtime so that backend team can be communicated when services are down

Until Successful scope can be implemented while calling backend API’s

On Error Continue scope to be used to call in case of error again

Create a batch job with all requests being sent to backend using that job as per the availability of backend API’s

NO.41 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?

Anypoint Platform Private Cloud Edition

Anypoint Runtime Fabric

CloudHub

Anypoint Service Mesh

NO.42 A leading bank implementing new mule API.
The purpose of API to fetch the customer account balances from the backend application and display them on the online platform the online banking platform. The online banking platform will send an array of accounts to Mule API get the account balances.
As a part of the processing the Mule API needs to insert the data into the database for auditing purposes and this process should not have any performance related implications on the account balance retrieval flow How should this requirement be implemented to achieve better throughput?

Implement the Async scope fetch the data from the backend application and to insert records in the Audit database

Implement a for each scope to fetch the data from the back-end application and to insert records into the Audit database

Implement a try-catch scope to fetch the data from the back-end application and use the Async scope to insert records into the Audit database

Implement parallel for each scope to fetch the data from the backend application and use Async scope to insert the records into the Audit database

NO.43 An organization is designing a mule application to support an all or nothing transaction between serval database operations and some other connectors so that they all roll back if there is a problem with any of the connectors Besides the database connector , what other connector can be used in the transaction.

VM

Anypoint MQ

SFTP

ObjectStore

NO.44 An auto mobile company want to share inventory updates with dealers Dl and D2 asynchronously and concurrently via queues Q1 and Q2. Dealer Dl must consume the message from the queue Q1 and dealer D2 to must consume a message from the queue Q2.
Dealer D1 has implemented a retry mechanism to reprocess the transaction in case of any errors while processing the inventers updates. Dealer D2 has not implemented any retry mechanism.
How should the dealers acknowledge the message to avoid message loss and minimize impact on the current implementation?

Dealer D1 must use auto acknowledgement and dealer D2 can use manual acknowledgement and acknowledge the message after successful processing

Dealer D1 can use auto acknowledgement and dealer D2 can use IMMEDIATE acknowledgement and acknowledge the message of successful processing

Dealer D1 and dealer D2 must use AUTO acknowledgement and acknowledge the message after successful processing

Dealer D1 can use AUTO acknowledgement and dealer D2 must use manual acknowledgement and acknowledge the message after successful processing

NO.45 An organization has defined a common object model in Java to mediate the communication between different Mule applications in a consistent way. A Mule application is being built to use this common object model to process responses from a SOAP API and a REST API and then write the processed results to an order management system.
The developers want Anypoint Studio to utilize these common objects to assist in creating mappings for various transformation steps in the Mule application.
What is the most idiomatic (used for its intended purpose) and performant way to utilize these common objects to map between the inbound and outbound systems in the Mule application?

Use JAXB (XML) and Jackson (JSON) data bindings

Use the WSS module

Use the Java module

Use the Transform Message component

[2023] Valid MCIA-Level-1-Maintenance test answers & MuleSoft MCIA-Level-1-Maintenance exam pdf [Q21-Q45]

[2023] Valid MCIA-Level-1-Maintenance test answers & MuleSoft MCIA-Level-1-Maintenance exam pdf [Q21-Q45]

TrainingDump

Leave a Reply
Cancel reply

Leave a Reply

[2023] Valid MCIA-Level-1-Maintenance test answers & MuleSoft MCIA-Level-1-Maintenance exam pdf [Q21-Q45]

TrainingDump

Leave a Reply Cancel reply

Leave a Reply

Leave a Reply
Cancel reply