A Mule application contains a Batch Job scope with several Batch Step scopes. The Batch Job scope is configured with a batch block size of 25.A payload with 4,000 records is received by the Batch Job scope.When there are no errors, how does the Batch Job scope process records within and between the Batch Step scopes?

The Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed in parallel All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope

The Batch Job scope processes each record block sequentially, one at a time Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed sequentially, one at a time All 4000 records must be completed before the blocks of records are available to the next Batch Step scope

The Batch Job scope processes multiple record blocks in parallel, and a block of 25 records can jump ahead to the next Batch Step scope over an earlier block of records Each Batch Step scope is invoked with one record in the payload of the received Mule event For each Batch Step scope, all 25 records within a block are processed sequentially, one record at a time All the records in a block must be completed before the block of 25 records is available to the next Batch Step scope

The Batch Job scope processes multiple record blocks in parallel Each Batch Step scope is invoked with a batch of 25 records in the payload of the received Mule event For each Batch Step scope, all 4000 records are processed in parallel Individual records can jump ahead to the next Batch Step scope before the rest of the records finish processing in the current Batch Step scope

To implement predictive maintenance on its machinery equipment, ACME Tractors has installed thousands of IoT sensors that will send data for each machinery asset as sequences of JMS messages, in near real-time, to a JMS queue named SENSOR_DATA on a JMS server. The Mule application contains a JMS Listener operation configured to receive incoming messages from the JMS servers SENSOR_DATA JMS queue. The Mule application persists each received JMS message, then sends a transformed version of the corresponding Mule event to the machinery equipment back-end systems.The Mule application will be deployed to a multi-node, customer-hosted Mule runtime cluster. Under normal conditions, each JMS message should be processed exactly once.How should the JMS Listener be configured to maximize performance and concurrent message processing of the JMS queue?

Set numberOfConsumers to a value greater than one Set primaryNodeOnly = false

Set numberOfConsumers = 1 Set primaryNodeOnly = false

Set numberOfConsumers = 1 Set primaryNodeOnly = true

Set numberOfConsumers to a value greater than one Set primaryNodeOnly = true

Set numberOfConsumers to a value greater than one Set primaryNodeOnly = false

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 handles the largest number of requests in the shortest time

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

An organization has implemented a continuous integration (CI) lifecycle that promotes Mule applications through code, build, and test stages. To standardize the organization's CI journey, a new dependency control approach is being designed to store artifacts that include information such as dependencies, versioning, and build promotions.To implement these process improvements, the organization will now require developers to maintain all dependencies related to Mule application code in a shared location.What is the most idiomatic (used for its intended purpose) type of system the organization should use in a shared location to standardize all dependencies related to Mule application code?

A MuleSoft-managed repository at repository.mulesoft.org

The Anypoint Object Store service at cloudhub.io

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

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

A Mule application uses APIkit for SOAP to implement a SOAP web service. The Mule application has been deployed to a CloudHub worker in a testing environment.The integration testing team wants to use a SOAP client to perform Integration testing. To carry out the integration tests, the integration team must obtain the interface definition for the SOAP web service.What is the most idiomatic (used for its intended purpose) way for the integration testing team to obtain the interface definition for the deployed SOAP web service in order to perform integration testing with the SOAP client?

Retrieve the XML file(s) from Runtime Manager

Retrieve the OpenAPI Specification file(s) from API Manager

Retrieve the WSDL file(s) from the deployed Mule application

Retrieve the RAML file(s) from the deployed Mule application

Retrieve the XML file(s) from Runtime Manager

An organization is designing a Mule application to periodically poll an SFTP location for new files containing sales order records and then process those sales orders. Each sales order must be processed exactly once.To support this requirement, the Mule application must identify and filter duplicate sales orders on the basis of a unique ID contained in each sales order record and then only send the new sales orders to the downstream system.What is the most idiomatic (used for its intended purpose) Anypoint connector, validator, or scope that can be configured in the Mule application to filter duplicate sales orders on the basis of the unique ID field contained in each sales order record?

Configure an Idempotent Message Validator component to filter each record by the order ID

Configure a Cache scope to filter and store each record from the received file by the order ID

Configure a Database connector to filter and store each record by the order ID

Configure an Idempotent Message Validator component to filter each record by the order ID

Configure a watermark In an On New or Updated File event source to filter unique records by the order ID

An organization's security requirements mandate centralized control at all times over authentication and authorization of external applications when invoking web APIs managed on Anypoint Platform.What Anypoint Platform feature is most idiomatic (used for its intended purpose), straightforward, and maintainable to use to meet this requirement?

Client management configured in access management

Identity management configured in access management

Enterprise Security module coded in Mule applications

External access configured in API Manager

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 Transform Message component

A marketing organization is designing a Mule application to process campaign data. The Mule application will periodically check for a file in a SFTP location and process the records in the file. The size of the file can vary from 10MB to 5GB. Due to the limited availabiltty of vCores, the Mule application is deployed to a single CloudHub worker configured with vCore size 0.2.The application must transform and send different formats of this file to three different downstream SFTP locations.What is the most idiomatic (used for its intended purpose) and performant way to configure the SFTP operations or event sources to process the large files to support these deployment requirements?

Use an in-memory repeatable stream

Use a file-stored non-repeatable stream

Use an in-memory non-repeatable stream

Use a file-stored repeatable stream

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

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

As a part of project requirement, client will send a stream of data to mule application. Payload size can vary between 10mb to 5GB. Mule application is required to transform the data and send across multiple sftp servers. Due to the cost cuttings in the organization, mule application can only be allocated one worker with size of 0.2 vCore.As an integration architect , which streaming strategy you would suggest to handle this scenario?

In-memory non repeatable stream

File based non-repeatable stream

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?

Both of the above option will have same latency

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

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?

Create similar model for Mule applications

Create a custom application to read Java code and make it available for Mule application

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

Scatter Gather router cannot be part of transaction

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 reprocessingWhat 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

An airline is architecting an API connectivity project to integrate its flight data into an online aggregation website. The interface must allow for secure communication high-performance and asynchronous message exchange.What are suitable interface technologies for this integration assuming that Mulesoft fully supports these technologies and that Anypoint connectors exist for these interfaces?

AsyncAPI over HTTPS AMQP with RabbitMQ JSON/REST over HTTPS

XML over ActiveMQ XML over SFTP XML/REST over HTTPS

CSV over FTP YAM L over TLS JSON over HTTPS

SOAP over HTTPS HOP over TLS gRPC over HTTPS

An application deployed to a runtime fabric environment with two cluster replicas is designed to periodically trigger of flow for processing a high-volume set of records from the source system and synchronize with the SaaS system using the Batch job scopeAfter processing 1000 records in a periodic synchronization of 1 lakh records, the replicas in which batch job instance was started went down due to unexpected failure in the runtime fabric environmentWhat is the consequence of losing the replicas that run the Batch job instance?

The second replicas will take over processing the remaining 99000 records

The remaining 99000 records will be lost and left and processed

The second replicas will take over processing the remaining 99000 records

A new replacement replica will be available and will be process all 1,00,000 records from scratch leading to duplicate record processing

A new placement replica will be available and will take or processing the remaining 99,000 records

One of the backend systems involved by the API implementation enforces rate limits on the number of request a particle client can make.Both the back-end system and API implementation are deployed to several non-production environments including the staging environment and to a particular production environment. Rate limiting of the back-end system applies to all non-production environments.The production environment however does not have any rate limiting.What is the cost-effective approach to conduct performance test of the API implementation in the non-production staging environment?

Create a Mocking service that replicates the back-end system's production performance characteristics Then configure the API implementation to use the mocking service and conduct the performance test

Including logic within the API implementation that bypasses in locations of the back-end system in the staging environment and invoke a Mocking service that replicates typical back-end system responses Then conduct performance test using this API implementation

Use MUnit to simulate standard responses from the back-end system. Then conduct performance test to identify other bottlenecks in the system

Create a Mocking service that replicates the back-end system's production performance characteristics Then configure the API implementation to use the mocking service and conduct the performance test

Conduct scaled-down performance tests in the staging environment against rate-limiting back-end system. Then upscale performance results to full production scale

A system API EmployeeSAPI is used to fetch employee's data from an underlying SQL database.The architect must design a caching strategy to query the database only when there is an update to the employees stable or else return a cached response in order to minimize the number of redundant transactions being handled by the database.What must the architect do to achieve the caching objective?

Use an On Table Row on employees table and call invalidate cache Use an object store caching strategy and expiration interval to empty

Use a Scheduler with a fixed frequency every hour triggering an invalidate cache flow Use an object store caching strategy and expiration interval to empty

Use a Scheduler with a fixed frequency every hour triggering an invalidate cache flow Use an object store caching strategy and set expiration interval to 1-hour

Use an on table rule on employees table call invalidate cache and said new employees data to cache Use an object store caching strategy and set expiration interval to 1-hour

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 flowHow should this requirement be implemented to achieve better throughput?

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

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

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 scope that participates in the local transaction.What is the behavior of the Scatter-Gather when running within this local transaction?

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

Execution of all routes within Scatter-Gather occurs sequentially Any error that occurs inside Scatter-Gather will be handled by error handler and will not result in roll back

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

Execution of all routes within Scatter-Gather occurs in parallel Any error that occurs inside Scatter-Gather will be handled by error handler and will not result in roll back

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

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

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

Refer to the exhibit. The HTTP Listener and the Logger are being handled from which thread pools respectively?

Shared Selector Pool and CPU LITE

CPU_INTENSIVE and Dedicated Selector pool

Shared Selector Pool and CPU LITE

An organization has strict unit test requirement that mandate every mule application must have an MUnit test suit with a test case defined for each flow and a minimum test coverage of 80%.A developer is building Munit test suit for a newly developed mule application that sends API request to an external rest API.What is the effective approach for successfully executing the Munit tests of this new application while still achieving the required test coverage for the Munit tests?

Mock the rest API invocation in the Munits and return a mock response for those invocations

Invoke the external endpoint of the rest API from the mule floors

Mark the rest API invocations in the Munits and then call the mocking service flow that simulates standard responses from the REST API

Mock the rest API invocation in the Munits and return a mock response for those invocations

Create a mocking service flow to simulate standard responses from the rest API and then configure the mule flows to call the marking service flow

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

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

As a part of project requirement, Java Invoke static connector in a mule 4 application needs to invoke a static method in a dependency jar file. What are two ways to add the dependency to be visible by the connectors class loader?(Choose two answers)

Add the dependency jar file to the java classpath by setting the JVM parameters

Configure the dependency as a shared library in the project POM

In the Java Invoke static connector configuration, configure a path and name of the dependency jar file

Add the dependency jar file to the java classpath by setting the JVM parameters

Use Maven command to include the dependency jar file when packaging the application

Configure the dependency as a shared library in the project POM

Update mule-artefact.json to export the Java package

When the mule application using VM is deployed to a customer-hosted cluster or multiple cloudhub workers, how are messages consumed by the Mule engine?

by starting an XA transaction for each new message

the primary only in order to avoid duplicate processing

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 serverThese 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

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?

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

An organization is building a test suite for their applications using m-unit. The integration architect has recommended using test recorder in studio to record the processing flows and then configure unit tests based on the capture eventsWhat are the two considerations that must be kept in mind while using test recorder(Choose two answers)

Tests for flows cannot be created with Mule errors raised inside the flow or already existing in the incoming event

A recorded flow execution ends successfully but the result does not reach its destination because the application is killed

Tests for flows cannot be created with Mule errors raised inside the flow or already existing in the incoming event

Recorder supports smoking a message before or inside a ForEach processor

The recorder support loops where the structure of the data been tested changes inside the iteration

A recorded flow execution ends successfully but the result does not reach its destination because the application is killed

Mocking values resulting from parallel processes are possible and will not affect the execution of the processes that follow in the test

Salesforce Certified MuleSoft Integration Architect I Practice Test 4

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?

Become a Premium Member for full access

Unlock Premium Member

Salesforce Certified MuleSoft Integration Architect I Practice Test 4

Question

Salesforce Certified MuleSoft Integration Architect I Practice Tests

Practice Tests