[Jan 04, 2024] 100% Latest Most updated MCIA-Level-1-Maintenance Questions and Answers [Q32-Q49] : Free Exam Dumps Collection : http://free.examcollectionpass.com

This page was exported from Free Exam Dumps Collection [ http://free.examcollectionpass.com ]
Export date: Sat Nov 30 19:08:26 2024 / +0000 GMT

[Jan 04, 2024] 100% Latest Most updated MCIA-Level-1-Maintenance Questions and Answers [Q32-Q49]

[Jan 04, 2024] 100% Latest Most updated MCIA-Level-1-Maintenance Questions and Answers

Try with 100% Real Exam Questions and Answers

Q32. An organization has an HTTPS-enabled Mule application named Orders API that receives requests from another Mule application named Process Orders.
The communication between these two Mule applications must be secured by TLS mutual authentication (two-way TLS).
At a minimum, what must be stored in each truststore and keystore of these two Mule applications to properly support two-way TLS between the two Mule applications while properly protecting each Mule application’s keys?

Orders API truststore: The Orders API public key
Process Orders keystore: The Process Orders private key and public key

Orders API truststore: The Orders API private key and public key
Process Orders keystore: The Process Orders private key public key

Orders API truststore: The Process Orders public key
Orders API keystore: The Orders API private key and public key
Process Orders truststore: The Orders API public key
Process Orders keystore: The Process Orders private key and public key

Orders API truststore: The Process Orders public key
Orders API keystore: The Orders API private key
Process Orders truststore: The Orders API public key
Process Orders keystore: The Process Orders private key

Q33. 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?

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

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)

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

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)

Q34. An organization if struggling frequent plugin version upgrades and external plugin project dependencies. The team wants to minimize the impact on applications by creating best practices that will define a set of default dependencies across all new and in progress projects.
How can these best practices be achieved with the applications having the least amount of responsibility?

Create a Mule plugin project with all the dependencies and add it as a dependency in each application’s POM.xml file

Create a mule domain project with all the dependencies define in its POM.xml file and add each application to the domain Project

Add all dependencies in each application’s POM.xml file

Create a parent POM of all the required dependencies and reference each in each application’s POM.xml file

Q35. 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

Q36. An organization is successfully using API led connectivity, however, as the application network grows, all the manually performed tasks to publish share and discover, register, apply policies to, and deploy an API are becoming repetitive pictures driving the organization to automate this process using efficient CI/’CD pipeline.
Considering Anypoint platforms capabilities how should the organization approach automating is API lifecycle?

Use runtime manager rest apis for API management and mavenforAPI deployment

Use Maven with a custom configuration required for the API lifecycle

Use Anypoint CLI or Anypoint Platform REST apis with scripting language such as groovy

Use Exchange rest api’s for API management and MavenforAPI deployment

Q37. Insurance organization is planning to deploy Mule application in MuleSoft Hosted runtime plane. As a part of requirement , application should be scalable . highly available. It also has regulatory requirement which demands logs to be retained for at least 2 years. As an Integration Architect what step you will recommend in order to achieve this?

It is not possible to store logs for 2 years in CloudHub deployment. External log management system is required.

When deploying an application to CloudHub , logs retention period should be selected as 2 years

When deploying an application to CloudHub, worker size should be sufficient to store 2 years data

Logging strategy should be configured accordingly in log4j file deployed with the application.

Q38. An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields. The data is available partially in a database and partially in a 3rd-party CRM system. What APIs should be created to best fit these design requirements?

A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changes.

One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile app.

Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System.

Explanation
Lets analyze the situation in regards to the different options available Option : A common Experience API but separate Process APIs Analysis : This solution will not work because having common experience layer will not help the purpose as mobile and web applications will have different set of requirements which cannot be fulfilled by single experience layer API Option : Common Process API Analysis : This solution will not work because creating a common process API will impose limitations in terms of flexibility to customize API;s as per the requirements of different applications. It is not a recommended approach.
Option : Separate set of API’s for both the applications Analysis : This goes against the principle of Anypoint API-led connectivity approach which promotes creating reusable assets. This solution may work but this is not efficient solution and creates duplicity of code.
Hence the correct answer is: Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system A screenshot of a computer Description automatically generated with low confidence

Lets analyze the situation in regards to the different options available Option : A common Experience API but separate Process APIs Analysis : This solution will not work because having common experience layer will not help the purpose as mobile and web applications will have different set of requirements which cannot be fulfilled by single experience layer API Option : Common Process API Analysis : This solution will not work because creating a common process API will impose limitations in terms of flexibility to customize API;s as per the requirements of different applications. It is not a recommended approach.
Option : Separate set of API’s for both the applications Analysis : This goes against the principle of Anypoint API-led connectivity approach which promotes creating reusable assets. This solution may work but this is not efficient solution and creates duplicity of code.
Hence the correct answer is: Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system Diagram Description automatically generated

Q39. An organization has implemented the cluster with two customer hosted Mule runtimes is hosting an application.
This application has a flow with a JMS listener configured to consume messages from a queue destination. As an integration architect can you advise which JMS listener configuration must be used to receive messages in all the nodes of the cluster?

Use the parameter primaryNodeOnly= “false” on the JMS listener

Use the parameter primaryNodeOnly= “false” on the JMS listener with a shared subscription

Use the parameter primaryNodeOnly= “true” on the JMS listener with a non*shared subscription

Use the parameter primaryNodeOnly= “true” on the JMS listener

Q40. 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?

Object Store REST API

Object Store connector

Both of the above option will have same latency

Object Store of one mule application cannot be accessed by other mule application.

Q41. A rale limiting policy has been applied to a soap VI.2 API published in Clondhub. The API implementation catches errors in a global error handler on error propagate in the main flow for HTTP: RETRY_EXHAUSTED with HTTP status set to 429 and any with the HTTP status set to 500.
What is the expected H1TP status when the client exceeds the quota of the API calls?

HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API B. HTTP status 500 as defined in the ANY error handler in the API since an API:RETRY_EXHAUSTED will be generated

HTTP status 401 unauthorized for policy violation

HTTP status 400 from the rate-limiting policy violation since the call does not reach the back-end

Q42. A Mule application is built to support a local transaction for a series of operations on a single database. The Mule application has a Scatter-Gather that participates in the local transaction.
What is the behavior of the Scatter-Gather when running within this local transaction?

Execution of each route within the Scatter-Gather occurs sequentially Any error that occurs inside the Scatter-Gather will result in a rollback of all the database operations

Execution of all routes within the Scatter-Gather occurs in parallel Any error that occurs inside the Scatter-Gather will result in a rollback of all the database operations

Execution of each route within the Scatter-Gather occurs sequentially Any error that occurs inside the Scatter-Gather will NOT result in a rollback of any of the database operations

Execution of each route within the Scatter-Gather occurs in parallel Any error that occurs inside the Scatter-Gather will NOT result in a rollback of any of the database operations

Q43. How does timeout attribute help inform design decisions while using JMS connector listening for incoming messages in an extended architecture (XA) transaction?

After the timeout is exceeded, stale JMS consumer threads are destroyed and new threads are created

The timeout specifies the time allowed to pass between receiving JMS messages on the same JMS connection and then after the timeout new JMS connection is established

The time allowed to pass between committing the transaction and the completion of the mule flow and then after the timeout flow processing triggers an error

The timeout defines the time that is allowed to pass without the transaction ending explicitly and after the timeout expires, the transaction rolls back

Q44. Customer has deployed mule applications to different customer hosted mule run times. Mule applications are managed from Anypoint platform.
What needs to be configured to monitor these Mule applications from Anypoint monitoring and what sends monitoring data to Anypoint monitoring?

Enable monitoring of individual applications from runtime manager application settings Runtime manager agent sends monitoring data from the mule applications to Anypoint monitoring

Install runtime manager agent on each mule runtime
Runtime manager agent since monitoring data from the mule applications to Anypoint monitoring

Anypoint monitoring agent on each mule runtime
Anypoint monitoring agent sends monitoring data from the mule applications to Anypoint monitoring

By default, Anypoint monitoring agent will be installed on each Mule run time Anypoint Monitoring agent automatically sends monitoring data from the Mule applications to Anypoint monitoring

Q45. A banking company is developing a new set of APIs for its online business. One of the critical API’s is a master lookup API which is a system API. This master lookup API uses persistent object store. This API will be used by all other APIs to provide master lookup data.

Master lookup API is deployed on two cloudhub workers of 0.1 vCore each because there is a lot of master data to be cached. Master lookup data is stored as a key value pair. The cache gets refreshed if they key is not found in the cache.
Doing performance testing it was observed that the Master lookup API has a higher response time due to database queries execution to fetch the master lookup data.
Due to this performance issue, go-live of the online business is on hold which could cause potential financial loss to Bank.
As an integration architect, which of the below option you would suggest to resolve performance issue?

Implement HTTP caching policy for all GET endpoints for the master lookup API and implement locking to synchronize access to object store

Upgrade vCore size from 0.1 vCore to 0,2 vCore

Implement HTTP caching policy for all GET endpoints for master lookup API

Add an additional Cloudhub worker to provide additional capacity

Q46. A project team uses RAML specifications to document API functional requirements and deliver API definitions. As per the current legal requirement, all designed API definitions to be augmented with an additional non-functional requirement to protect the services from a high rate of requests according to define service level agreements.
Assuming that the project is following Mulesoft API governance and policies, how should the project team convey the necessary non-functional requirement to stakeholders?

Create proxies in API manager for the non functional requirement and publish to exchange

Add all non functional requirements as comments to RAML specification and publish to exchange

Create various SLA’s in API manager for the non functional requirement and publish to exchange

Update API definitions with the fragment for the appropriate policy and publish to exchange

Q47. What is maximum vCores can be allocated to application deployed to CloudHub?

1 vCores

2 vCores

4 vCores

16 vCores

Q48. 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

Q49. An organization 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 HTTPS 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 rejections from the back-end system will need to be processed manually (outside the back-end system).
The Mule application will be deployed to a customer-hosted runtime and is 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.
What idiomatic (used for their intended purposes) 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?

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
An Until Successful scope containing VM components for long retries
A persistent dead-letter VM queue configured in CloudHub

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 configured in the CloudHub Object Store service

A Batch Job scope to call the back-end system
An Until Successful scope containing Object Store components for long retries A dead-letter object store configured in the Mule application

New MuleSoft MCIA-Level-1-Maintenance Dumps & Questions: https://www.examcollectionpass.com/MuleSoft/MCIA-Level-1-Maintenance-practice-exam-dumps.html

Post date: 2024-01-04 15:32:35
Post date GMT: 2024-01-04 15:32:35
Post modified date: 2024-01-04 15:32:35
Post modified date GMT: 2024-01-04 15:32:35