Free Access to Salesforce.MuleSoft-Integration-Architect-I.v2026-03-30.q190 with Valid Practice Test (Page 25)

Question 116

When designing an upstream API and its implementation, the development team has been advised to not set timeouts when invoking downstream API. Because the downstream API has no SLA that can be relied upon.
This is the only donwstream API dependency of that upstream API. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

A.The invocation of the downstream API will run to completion without timing out.
B.An SLA for the upstream API CANNOT be provided.
C.A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes.
D.A load-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes.

Question 117

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

A.Compile, package, unit test, validate unit test coverage, deploy
B.Compile, package, unit test, deploy, integration test (Incorrect)
C.Compile, package, unit test, deploy, create associated API instances in API Manager
D.Import from API designer, compile, package, unit test, deploy, publish to Anypoint Exchange

Correct Answer: A

Correct answer is "Compile, package, unit test, validate unit test coverage, deploy" : Anypoint Platform supports continuous integration and continuous delivery using industry standard tools Mule Maven Plugin The Mule Maven plugin can automate building, packaging and deployment of Mule applications from source projects Using the Mule Maven plugin, you can automate your Mule application deployment to CloudHub, to Anypoint Runtime Fabric, or on-premises, using any of the following deployment strategies * CloudHub deployment * Runtime Fabric deployment * Runtime Manager REST API deployment * Runtime Manager agent deployment MUnit Maven Plugin The MUnit Maven plugin can automate test execution, and ties in with the Mule Maven plugin. It provides a full suite of integration and unit test capabilities, and is fully integrated with Maven and Surefire for integration with your continuous deployment environment. Since MUnit 2.x, the coverage report goal is integrated with the maven reporting section. Coverage Reports are generated during Maven's site lifecycle, during the coverage-report goal. One of the features of MUnit Coverage is to fail the build if a certain coverage level is not reached. MUnit is not used for integration testing Also publishing to Anypoint Exchange or to create associated API instances in API Manager is not a part of CICD pipeline which can ne achieved using mulesoft provided maven plugin Architecture mentioned in the question can be diagrammatically put as below. Persistent Object Store is the correct answer .
* Mule Object Stores: An object store is a facility for storing objects in or across Mule applications. Mule uses object stores to persist data for eventual retrieval.
Mule provides two types of object stores:
1) In-memory store - stores objects in local Mule runtime memory. Objects are lost on shutdown of the Mule runtime. So we cant use in memory store in our scenario as we want to share watermark within all cloudhub workers
2) Persistent store - Mule persists data when an object store is explicitly configured to be persistent. Hence this watermark will be available even any of the worker goes down

Question 118

As a part of project , existing java implementation is being migrated to Mulesoft. Business is very tight on the budget and wish to complete the project in most economical way possible.
Canonical object model using java is already a part of existing implementation. Same object model is required by mule application for a business use case. What is the best way to achieve this?

A.Make use of Java module
B.Create similar model for Mule applications
C.Create a custom application to read Java code and make it available for Mule application
D.Use Anypoint exchange

Question 119

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?

A.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
B.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
C.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
D.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

Correct Answer: B

* To design an integration Mule application that processes orders and ensures reliability even with an unreliable back-end system, the following components and ActiveMQ queues should be used:
* Until Successful Scope: This scope ensures that the Mule application will continue trying to submit the order to the back-end system until it succeeds or reaches a specified retry limit. This helps in handling transient network issues or minor outages of the back-end system.
* ActiveMQ Long-Retry Queues: By placing the orders in long-retry queues, the application can manage retries over an extended period. This is particularly useful when the back-end system experiences longer outages. The ActiveMQ broker, located within the organization's firewall, can reliably handle these queues.
* ActiveMQ Dead-Letter Queues: Orders that cannot be successfully submitted after all retry attempts should be moved to dead-letter queues. This allows for manual processing of these orders. The dead- letter queue ensures that no orders are lost and provides a clear mechanism for handling failed submissions.
Implementation Steps:
* HTTP Listener: Set up an HTTP listener to receive incoming orders.
* Immediate Acknowledgment: Immediately acknowledge the receipt of the order to the client.
* Until Successful Scope: Use the Until Successful scope to attempt submitting the order to the back-end system. Configure retry intervals and limits.
* Long-Retry Queues: Configure ActiveMQ long-retry queues to manage retries.
* Dead-Letter Queues: Set up ActiveMQ dead-letter queues for orders that fail after maximum retry attempts, allowing for manual intervention.
This approach ensures that the system can handle temporary and prolonged back-end outages while minimizing manual processing.
References:
* MuleSoft Documentation on Until Successful Scope: https://docs.mulesoft.com/mule-runtime/4.3/until- successful-scope
* ActiveMQ Documentation: https://activemq.apache.org/

Question 120

Which productivity advantage does Anypoint Platform have to both implement and manage an AP?

A.Automatic API proxy generation
B.Automatic API specification generation
C.Automatic API semantic versioning
D.Automatic API governance

Question 116

Question 117

Question 118

Question 119

Question 120

Download PDF File