Mulesoft MuleSoft Certified Architect MCIA-LEVEL-1-MAINTENANCE Questions & Answers

• Question 111:

  An integration Mule application is deployed to a customer-hosted multi-node Mule 4 runtime duster. The Mule application uses a Listener operation of a JMS connector to receive incoming messages from a JMS queue. How are the messages consumed by the Mule application?

  A. Depending on the JMS provider's configuration, either all messages are consumed by ONLY the primary cluster node or else ALL messages are consumed by ALL cluster nodes

  B. Regardless of the Listener operation configuration, all messages are consumed by ALL cluster nodes

  C. Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node

  D. Regardless of the Listener operation configuration, all messages are consumed by ONLY the primary cluster node

  Correct Answer: C

  Correct answer is Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node For applications running in clusters,

  you have to keep in mind the concept of primary node and how the connector will behave. When running in a cluster, the JMS listener default behavior will be to receive messages only in the primary node, no matter what kind of destination

  you are consuming from. In case of consuming messages from a Queue, you'll want to change this configuration to receive messages in all the nodes of the cluster, not just the primary.

  This can be done with the primaryNodeOnly parameter:

• Question 112:

  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?

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

  C. HTTP status 401 unauthorized for policy violation

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

  Correct Answer: A

• Question 113:

  What aspects of a CI/CD pipeline for Mute applications can be automated using MuleSoft- provided Maven plugins?

  A. Compile, package, unit test, deploy, create associated API instances in API Manager B Import from API designer, compile, package, unit test, deploy, publish to Am/point Exchange

  B. Compile, package, unit test, validate unit test coverage, deploy

  C. Compile, package, unit test, deploy, integration test

  Correct Answer: C

• Question 114:

  Refer to the exhibit.

  A Mule application is being designed to expose a SOAP web service to its clients.

  What language is typically used inside the web service's interface definition to define the data structures that the web service Is expected to exchange with its clients?

  

  A. WSDL

  B. XSD

  C. JSON Schema

  D. RAMI

  Correct Answer: B

• Question 115:

  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?

  A. Logging needs to be changed from asynchronous to synchronous

  B. External log appender needs to be used in this case

  C. Persistent memory storage should be used in such scenarios

  D. Mixed configuration of asynchronous or synchronous loggers should be used to log exceptions via synchronous way

  Correct Answer: D

  Correct approach is to use Mixed configuration of asynchronous or synchronous loggers shoud be used to log exceptions via synchronous way Asynchronous logging poses a performance-reliability trade-off. You may lose some messages if Mule crashes before the logging buffers flush to the disk. In this case, consider that you can have a mixed configuration of asynchronous or synchronous loggers in your app. Best practice is to use asynchronous logging over synchronous with a minimum logging level of WARN for a production application. In some cases, enable INFO logging level when you need to confirm events such as successful policy installation or to perform troubleshooting. Configure your logging strategy by editing your application's src/main/resources/log4j2.xml file

• Question 116:

  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?

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

  B. 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)

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

  D. 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)

  Correct Answer: B

• Question 117:

  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?

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

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

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

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

  Correct Answer: A

  Reference: https://docs.mulesoft.com/mule-runtime/4.4/transaction-management

• Question 118:

  Refer to the exhibit.

  

  One of the backend systems invoked by an API implementation enforces rate limits on the number of requests a particular client can make. Both the backend system and the API implementation are deployed to several non-production environments in addition to production.

  Rate limiting of the backend system applies to all non-production environments. The production environment, however, does NOT have any rate limiting.

  What is the most effective approach to conduct performance tests of the API implementation in a staging (non-production) environment?

  A. Create a mocking service that replicates the backend system's production performance characteristics. Then configure the API implementation to use the mocking service and conduct the performance tests

  B. Use MUnit to simulate standard responses from the backend system then conduct performance tests to identify other bottlenecks in the system

  C. Include logic within the API implementation that bypasses invocations of the backend system in a performance test situation. Instead invoking local stubs that replicate typical backend system responses then conduct performance tests using this API Implementation

  D. Conduct scaled-down performance tests in the staging environment against the rate limited backend system then upscale performance results to full production scale

  Correct Answer: A

  Correct answer is Create a mocking service that replicates the backend system's production performance characteristics. Then configure the API implementation to use the mocking service and conduct the performance tests

  *

  MUnit is for only Unit and integration testing for APIs and Mule apps. Not for performance Testing, even if it has the ability to Mock the backend.

  *

  Bypassing the backend invocation defeats the whole purpose of performance testing. Hence it is not a valid answer.

  *

  Scaled down performance tests cant be relied upon as performance of API's is not linear against load.

• Question 119:

  According to MuteSoft, which principle is common to both Service Oriented Architecture (SOA) and API-led connectivity approaches?

  A. Service centralization

  B. Service statefulness

  C. Service reusability

  D. Service interdependence

  Correct Answer: C

• Question 120:

  An insurance company is using a CIoudHub runtime plane. As a part of requirement, email alert should be sent to internal operations team every time of policy applied to an API instance is deleted As an integration architect suggest on how this requirement be met?

  A. Use audit logs in Anypoint platform to detect a policy deletion and configure the Audit logs alert feature to send an email to the operations team

  B. Use Anypoint monitoring to configure an alert that sends an email to the operations team every time a policy is deleted in API manager

  C. Create a custom connector to be triggered every time of policy is deleted in API manager

  D. Implement a new application that uses the Audit log REST API to detect the policy deletion and send an email to operations team the SMTP connector

  Correct Answer: D