Top Salesforce MuleSoft-Integration-Architect-I Courses Online - Updated [May-2026]
MuleSoft-Integration-Architect-I Practice Dumps - Verified By Test4Cram Updated 275 Questions
Salesforce MuleSoft-Integration-Architect-I Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
| Topic 6 |
|
| Topic 7 |
|
| Topic 8 |
|
NEW QUESTION # 79
Additional nodes are being added to an existing customer-hosted Mule runtime cluster to improve performance. Mule applications deployed to this cluster are invoked by API clients through a load balancer.
What is also required to carry out this change?
- A. API implementations using an object store must be adjusted to recognize the new nodes and persist to them
- B. A new load balancer must be provisioned to allow traffic to the new nodes in a round-robin fashion
- C. New firewall rules must be configured to accommodate communication between API clients and the new nodes
- D. External monitoring tools or log aggregators must be configured to recognize the new nodes
Answer: D
Explanation:
* Clustering is a group of servers or mule runtime which acts as a single unit.
* Mulesoft Enterprise Edition supports scalable clustering to provide high availability for the Mulesoft application.
* In simple terms, virtual servers composed of multiple nodes and they communicate and share information through a distributed shared memory grid.
* By default, Mulesoft ensures the High availability of applications if clustering implemented.
* Let's consider the scenario one of the nodes in cluster crashed or goes down and under maintenance. In such cases, Mulesoft will ensure that requests are processed by other nodes in the cluster. Mulesoft clustering also ensures that the request is load balanced between all the nodes in a cluster.
* Clustering is only supported by on-premise Mule runtime and it is not supported in Cloudhub.
Correct answer is External monitoring tools or log aggregators must be configured to recognize the new nodes
* Rest of the options are automatically taken care of when a new node is added in cluster.
Reference: https://docs.mulesoft.com/runtime-manager/cluster-about
NEW QUESTION # 80
A stock trading company handles millions of trades a day and requires excellent performance and reliability within its stock trading system. The company operates a number of event-driven APIs Implemented as Mule applications that are hosted on various customer-hosted Mule clusters and needs to enable message exchanges between the APIs within their internal network using shared message queues.
What is an effective way to meet the cross-cluster messaging requirements of its event-driven APIs?
- A. JMS transactions with automatic acknowledgements
- B. Persistent VM queues with automatic acknowledgements
- C. Non-transactional JMS operations with a reliability pattern and manual acknowledgements
- D. extended Architecture (XA) transactions and XA connected components with manual acknowledgements
Answer: A
Explanation:
* JMS (Java Message Service): JMS is a robust messaging standard that supports reliable and asynchronous communication. It allows message producers and consumers to exchange messages via a common message broker.
* Transactions with Automatic Acknowledgements: Utilizing JMS transactions ensures that messages are processed reliably. The automatic acknowledgement mode means that once the consumer receives the message, it acknowledges the broker automatically, ensuring that no messages are lost.
* Performance and Reliability: JMS transactions offer both high performance and reliability. By enabling transactions, each message processing step can be committed or rolled back, ensuring data integrity.
* Cross-Cluster Messaging: For a stock trading company dealing with millions of trades, using JMS transactions allows for consistent and reliable message delivery across different clusters in their network. This approach is more suitable compared to non-transactional or VM queues due to the scale and reliability requirements.
* Event-Driven APIs: The APIs can leverage the transactional nature of JMS to ensure that messages exchanged between different services are reliable and can recover gracefully from failures.
MuleSoft Documentation on JMS Connector: MuleSoft JMS Connector
JMS 2.0 Specification: Oracle JMS 2.0
NEW QUESTION # 81
In a Mule Application, a flow contains two (2) JMS consume operations that are used to connect to a JMS broker and consume messages from two(2) JMS destination. The Mule application then joins the two JMS messages together.
The JMS broker does not implement high availability (HA) and periodically experiences scheduled outages of upto 10 mins for routine maintenance.
What is the most idiomatic (used for its intented purpose) way to build the mule flow so it can best recover from the expected outages?
- A. Configure a reconnection strategy for the JMS connector
- B. Enclose the two(2) JMS operation in an Until Successful scope
- C. Consider a transaction for the JMS connector
- D. Enclose the two(2) JMS operations in a Try scope with an Error Continue error handler
Answer: A
Explanation:
When an operation in a Mule application fails to connect to an external server, the default behavior is for the operation to fail immediately and return a connectivity error. You can modify this default behavior by configuring a reconnection strategy for the operation. You can configure a reconnection strategy for an operation either by modifying the operation properties or by modifying the configuration of the global element for the operation. The following are the available reconnection strategies and their behaviors: None Is the default behavior, which immediately returns a connectivity error if the attempt to connect is unsuccessful Standard (reconnect) Sets the number of reconnection attempts and the interval at which to execute them before returning a connectivity error Forever (reconnect-forever) Attempts to reconnect continually at a given interval
NEW QUESTION # 82
An organization is designing multiple new applications to run on CloudHub in a single Anypoint VPC and that must share data using a common persistent Anypoint object store V2 (OSv2).
Which design gives these mule applications access to the same object store instance?
- A. An Anypoint MQ connector configured to directly access the persistent object store
- B. Object store V2 can be shared across cloudhub applications with the configured osv2 connector
- C. AVM connector configured to directly access the persistence queue of the persistent object store
- D. The object store V2 rest API configured to access the persistent object store
Answer: B
Explanation:
Object Store v2 (OSv2) in MuleSoft allows multiple applications within the same Anypoint Virtual Private Cloud (VPC) to share data. To achieve this, the OSv2 connector must be configured in each application to access the common persistent object store instance. This configuration enables the applications to read from and write to the same object store, facilitating data sharing. Object Store v2 is designed to be persistent and reliable, making it suitable for scenarios where data needs to be retained and shared across multiple applications.
MuleSoft Documentation on Object Store v2
NEW QUESTION # 83
A project uses Jenkins to implement CI/CD process. It was observed that each Mule package contains some of the Jenkins files and folders for configurations of CI/CD jobs.
As these files and folders are not part of the actual package, expectation is that these should not be part of deployed archive.
Which file can be used to exclude these files and folders from the deployed archive?
- A. _muleExclude
- B. mulelnclude
- C. muleignore
- D. _unTrackMule
Answer: C
Explanation:
* Requirement Analysis: Jenkins files and folders used for CI/CD configurations are not part of the actual Mule package and should be excluded from the deployed archive.
* Solution: MuleSoft provides the .muleignore file to specify files and directories that should be excluded from the packaged application.
* Implementation Steps:
* Create a .muleignore File: In the root directory of your Mule project, create a file named .
muleignore.
* Specify Exclusions: Add the paths of the Jenkins files and folders that you want to exclude from the deployment package into the .muleignore file.
# .muleignore example /path/to/jenkins/file1 /path/to/jenkins/folder/*
* Build and Deploy: When you build your Mule application, the Mule runtime will read the .
muleignore file and exclude the specified files and directories from the deployment archive.
* Advantages:
* Clean Deployment: Ensures that only necessary files are included in the deployment package, reducing the package size and preventing potential issues related to unwanted files.
* Ease of Maintenance: Easy to update and manage which files are excluded from the deployment package.
References
* MuleSoft Documentation on .muleignore
NEW QUESTION # 84
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?
- A. SOAP over HTTPS HOP over TLS gRPC over HTTPS
- B. CSV over FTP YAM L over TLS JSON over HTTPS
- C. AsyncAPI over HTTPS
AMQP with RabbitMQ JSON/REST over HTTPS - D. XML over ActiveMQ XML over SFTP XML/REST over HTTPS
Answer: C
Explanation:
For integrating flight data into an online aggregation website with secure, high-performance, and asynchronous message exchange, the most suitable interface technologies supported by MuleSoft are:
* AsyncAPI over HTTPS: AsyncAPI is a specification for asynchronous APIs, which is ideal for high- performance, event-driven communication. Using HTTPS ensures secure communication.
* AMQP with RabbitMQ: AMQP (Advanced Message Queuing Protocol) is a protocol for message- oriented middleware. RabbitMQ is a popular message broker that supports AMQP, allowing for reliable and asynchronous message exchange.
* JSON/REST over HTTPS: JSON is a lightweight data-interchange format, and REST (Representational State Transfer) is an architectural style for designing networked applications. Using HTTPS ensures secure communication.
Implementation Steps:
* Define the AsyncAPI specification for the flight data events and set up the infrastructure to handle these events over HTTPS.
* Set up RabbitMQ and configure AMQP for message queuing. Ensure that your MuleSoft application is capable of consuming and producing messages using the RabbitMQ connector.
* Implement RESTful APIs using JSON over HTTPS to expose the flight data securely.
These technologies collectively ensure secure, asynchronous, and high-performance integration.
References:
* MuleSoft Documentation: AsyncAPI
* MuleSoft Documentation: RabbitMQ Connector
* MuleSoft Documentation: JSON and REST APIs
NEW QUESTION # 85
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?
- A. Use a file-stored non-repeatable stream
- B. Use an in-memory non-repeatable stream
- C. Use an in-memory repeatable stream
- D. Use a file-stored repeatable stream
Answer: C
Explanation:
Reference: https://docs.mulesoft.com/mule-runtime/4.4/streaming-about
NEW QUESTION # 86
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 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
- B. 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
- C. 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
- D. 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
Answer: C
NEW QUESTION # 87
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?
- A. Metadata API
- B. REST API
- C. SOAP API
- D. Bulk API
Answer: B
NEW QUESTION # 88
An organization uses a four(4) node customer hosted Mule runtime cluster to host one(1) stateless api implementation. The API is accessed over HTTPS through a load balancer that uses round-robin for load distribution. Each node in the cluster has been sized to be able to accept four(4) times the current number of requests.
Two(2) nodes in the cluster experience a power outage and are no longer available. The load balancer directs the outage and blocks the two unavailable the nodes from receiving further HTTP requests.
What performance-related consequence is guaranteed to happen to average, assuming the remaining cluster nodes are fully operational?
- A. 100% increase in the number of requests received by each remaining node
- B. 50% reduction in the throughput of the API
- C. 100% increase in the average response time of the API
- D. 50% increase in the JVM heap memory consumed by each remaining node
Answer: C
Explanation:
* "100% increase in the throughput of the API" might look correct, as the number of requests processed per second might increase, but is it guaranteed to increase by 100%? Using 4 nodes will definitely increase throughput of system. But it is cant be precisely said if there would be 100% increase in throughput as it depends on many other factors. Also it is nowhere mentioned in the description that all nodes have same CPU
/memory assigned. The question is about the guaranteed behavior * Increasing number of nodes will have no impact on response time as we are scaling application horizontally and not vertically. Similarly there is no change in JVM heap memory usage. * So Correct answer is 50% reduction in the number of requests being received by each node This is because of the two reasons. 1) API is mentioned as stateless 2) Load Balancer is used
NEW QUESTION # 89
An external REST client periodically sends an array of records in a single POST request to a Mule application API endpoint.
The Mule application must validate each record of the request against a JSON schema before sending it to a downstream system in the same order that it was received in the array Record processing will take place inside a router or scope that calls a child flow. The child flow has its own error handling defined. Any validation or communication failures should not prevent further processing of the remaining records.
To best address these requirements what is the most idiomatic(used for it intended purpose) router or scope to used in the parent flow, and what type of error handler should be used in the child flow?
- A. Parallel For Each scope in the parent flow
On Error Propagate error handler in the child flow - B. First Successful router in the parent flow
On Error Continue error handler in the child flow - C. For Each scope in the parent flow
On Error Continue error handler in the child flow - D. Until Successful router in the parent flow
On Error Propagate error handler in the child flow
Answer: C
Explanation:
Correct answer is For Each scope in the parent flow On Error Continue error handler in the child flow. You can extract below set of requirements from the question a) Records should be sent to downstream system in the same order that it was received in the array b) Any validation or communication failures should not prevent further processing of the remaining records First requirement can be met using For Each scope in the parent flow and second requirement can be met using On Error Continue scope in child flow so that error will be suppressed.
NEW QUESTION # 90
A set of integration Mule applications, some of which expose APIs, are being created to enable a new business process. Various stakeholders may be impacted by this. These stakeholders are a combination of semi-technical users (who understand basic integration terminology and concepts such as JSON and XML) and technically skilled potential consumers of the Mule applications and APIs.
What Is an effective way for the project team responsible for the Mule applications and APIs being built to communicate with these stakeholders using Anypoint Platform and its supplied toolset?
- A. Capture documentation about the Mule applications and APIs inline within the Mule integration flows and use Anypoint Studio's Export Documentation feature to provide an HTML version of this documentation to the stakeholders
- B. Use Anypoint Exchange to register the various Mule applications and APIs and share the RAML definitions with the stakeholders, so they can be discovered
- C. Create Anypoint Exchange entries with pages elaborating the integration design, including API notebooks (where applicable) to help the stakeholders understand and interact with the Mule applications and APIs at various levels of technical depth
- D. Use Anypoint Design Center to implement the Mule applications and APIs and give the various stakeholders access to these Design Center projects, so they can collaborate and provide feedback
Answer: C
Explanation:
As the stakeholders are semitechnical users , preferred option is Create Anypoint Exchange entries with pages elaborating the integration design, including API notebooks (where applicable) to help the stakeholders understand and interact with the Mule applications and APIs at various levels of technical depth
NEW QUESTION # 91
Which key DevOps practice and associated Anypoint Platform component should a MuteSoft integration team adopt to improve delivery quality?
- A. A Continuous design with API Designer
- B. Passive monitoring with Anypoint Monitoring
- C. Automated testing with MUnit
- D. Manual testing with Anypoint Studio
Answer: C
Explanation:
To improve delivery quality, a MuleSoft integration team should adopt automated testing with MUnit. MUnit is MuleSoft's testing framework that allows developers to create, design, and run unit and integration tests on their Mule applications. Automated testing with MUnit ensures that each part of the Mule application is tested for correctness and performance, catching issues early in the development cycle. This practice leads to higher quality code, reduced defects, and more reliable integrations.
Other practices mentioned, such as continuous design with API Designer and passive monitoring with Anypoint Monitoring, are important but do not directly address the need for rigorous and automated testing to ensure quality.
References
* MuleSoft Documentation on MUnit
* Best Practices for Automated Testing with MUnit
NEW QUESTION # 92
A Mule application contains a Batch Job with two Batch Steps (Batch_Step_l and Batch_Step_2). A payload with 1000 records is received by the Batch Job.
How many threads are used by the Batch Job to process records, and how does each Batch Step process records within the Batch Job?
- A. Each Batch Job uses SEVERAL THREADS for the Batch Steps Each Batch Step instance receives ONE record at a time as the payload, and RECORDS are processed IN PARALLEL within and between the two Batch Steps
- B. Each Batch Job uses SEVERAL THREADS for the Batch Steps Each Batch Step instance receives ONE record at a time as the payload, and BATCH STEP INSTANCES execute IN PARALLEL to process records and Batch Steps in ANY order as fast as possible
- C. Each Batch Job uses a SINGLE THREAD to process a configured block size of record Each Batch Step instance receives A BLOCK OF records as the payload, and BLOCKS of records are processed IN ORDER
- D. Each Batch Job uses a SINGLE THREAD for all Batch steps Each Batch step instance receives ONE record at a time as the payload, and RECORDS are processed IN ORDER, first through Batch_Step_l and then through Batch_Step_2
Answer: A
Explanation:
* Each Batch Job uses SEVERAL THREADS for the Batch Steps
* Each Batch Step instance receives ONE record at a time as the payload. It's not received in a block, as it does not wait for multiple records to be completed before moving to next batch step. (So Option D is out of choice)
* RECORDS are processed IN PARALLEL within and between the two Batch Steps.
* RECORDS are not processed in order. Let's say if second record completes batch_step_1 before record 1, then it moves to batch_step_2 before record 1. (So option C and D are out of choice)
* A batch job is the scope element in an application in which Mule processes a message payload as a batch of records. The term batch job is inclusive of all three phases of processing: Load and Dispatch, Process, and On Complete.
* A batch job instance is an occurrence in a Mule application whenever a Mule flow executes a batch job. Mule creates the batch job instance in the Load and Dispatch phase. Every batch job instance is identified internally using a unique String known as batch job instance id.
NEW QUESTION # 93
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?
- A. In RTF-VM, edit the pod configuration to automatically install and configure an Anypoint Monitoring agent
- B. In RTF-VM, install and configure the external LTM's log-forwarding agent
- C. In RTF-VM. configure the out-of-the-box external log forwarder
- D. In each Mule application, configure custom Log4j settings
Answer: B
NEW QUESTION # 94
Which Anypoint Platform component should a MuleSoft developer use to create an API specification prior to building the API implementation?
- A. Runtime Manager
- B. MUnit
- C. API Manager
- D. API Designer
Answer: D
Explanation:
A MuleSoft developer should use API Designer to create an API specification prior to building the API implementation. API Designer is a component of Anypoint Platform that provides a web-based interface for designing and documenting APIs. It supports API modeling languages such as RAML and OAS, enabling developers to define the structure, resources, and operations of an API before proceeding with implementation. This approach aligns with the design-first methodology, ensuring a well-defined contract for the API.
References:
* Anypoint API Designer
* API Design Best Practices
NEW QUESTION # 95
How does timeout attribute help inform design decisions while using JMS connector listening for incoming messages in an extended architecture (XA) transaction?
- A. 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
- B. The timeout defines the time that is allowed to pass without the transaction ending explicitly and after the timeout expires, the transaction rolls back
- C. After the timeout is exceeded, stale JMS consumer threads are destroyed and new threads are created
- D. 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
Answer: B
Explanation:
* Timeout Attribute:
* The timeout attribute in the JMS connector specifies the maximum time allowed for a transaction to be completed. If the transaction does not complete within this specified time, it will be considered a timeout.
* Transaction Management:
* In the context of an Extended Architecture (XA) transaction, this timeout ensures that if the transaction is not explicitly ended within the defined time, the transaction is rolled back to maintain data consistency.
* Implications of Timeout:
* If the timeout is exceeded, the JMS message processing is considered unsuccessful, and all operations within the transaction are undone, which helps in avoiding partial updates and maintaining a reliable state.
References:
* MuleSoft Documentation on JMS Connector
* Understanding XA Transactions
NEW QUESTION # 96
A company is implementing a new Mule application that supports a set of critical functions driven by a rest API enabled, claims payment rules engine hosted on oracle ERP. As designed the mule application requires many data transformation operations as it performs its batch processing logic.
The company wants to leverage and reuse as many of its existing java-based capabilities (classes, objects, data model etc.) as possible What approach should be considered when implementing required data mappings and transformations between Mule application and Oracle ERP in the new Mule application?
- A. From the mule application, transform via theXSLT model
- B. Transform by calling any suitable Java class from Dataweave
- C. Create a new metadata RAML classes in Mule from the appropriate Java objects and then perform transformations via Dataweave
- D. Invoke any of the appropriate Java methods directly, create metadata RAML classes and then perform required transformations via Dataweave
Answer: B
Explanation:
Leveraging existing Java-based capabilities for data transformations in a Mule application can enhance efficiency and reuse. Here's how to integrate Java classes for transformations:
* Create Java Classes:
* Ensure the Java classes that contain the transformation logic are available in the Mule application project.
* Compile the Java classes if they are not already compiled and place the .class files or JAR file in the Mule project's classpath.
* Configure DataWeave to Call Java Methods:
* Use DataWeave's capability to invoke Java methods within the transformation scripts.
* Import the Java classes and methods in the DataWeave script.
%dw 2.0 import * from my.package.ClassName output application/json --- { transformedData: ClassName::
methodName(payload) }
* Perform Transformations:
* Write DataWeave scripts that call the appropriate Java methods to perform the necessary transformations.
* Ensure the input and output types match between DataWeave and the Java methods.
* Test Transformations:
* Thoroughly test the transformations to ensure the Java methods are correctly invoked and the expected transformations are applied.
This approach allows for seamless integration of existing Java logic into Mule applications, leveraging DataWeave's power for comprehensive data transformations.
References
* MuleSoft Documentation: DataWeave and Java Integration
* MuleSoft Documentation: Using Java with Mule
NEW QUESTION # 97
A large life sciences customer plans to use the Mule Tracing module with the Mapped Diagnostic Context (MDC) logging operations to enrich logging in its Mule application and to improve tracking by providing more context in the Mule application logs. The customer also wants to improve throughput and lower the message processing latency in its Mule application flows.
After installing the Mule Tracing module in the Mule application, how should logging be performed in flows in Mule applications, and what should be changed In the log4j2.xml files?
- A. In the flows, add Mule Tracing module Set logging variable operations before any Core Logger components.In log4j2.xml files, change the appender's pattern layout to use %MDC and then assign the appender to a Logger or Root element.
- B. In the flows, add Mule Tracing module Set logging variable operations before any CoreLogger components.In log4j2.xmI files, change the appender's pattern layout to use the %MDC placeholder and then assign the appender to an AsyncLogger element.
- C. In the flows, add Mule Tracing module Set logging variable operations before any CoreLogger components.In log4j2.xmI files, change the appender''s pattern layout to use %asyncLogger placeholder and then assign the appender to an AsyncLogger element.
- D. In the flows, wrap Logger components in Async scopes. In log4j2.xmI files, change the appender's pattern layout to use the %asyncLoggerplaceholder and then assign the appender to a Logger or Root element.
Answer: A
Explanation:
* Mule Tracing Module and MDC:
* The Mule Tracing module enhances logging by adding context-specific information to logs using Mapped Diagnostic Context (MDC).
* MDC allows including additional metadata in logs, making it easier to trace and debug issues in the application.
* Set Logging Variable Operations:
* In Mule flows, before any Core Logger components, add Set logging variable operations from the Mule Tracing module.
* This ensures that the contextual information is set before logs are written.
* Configuring log4j2.xml:
* Update the log4j2.xml file to change the appender's pattern layout to include %MDC placeholders.
* Assign the appender to either a Logger or the Root element to ensure that logs across the application include the MDC-enriched information.
* Improving Throughput and Lowering Latency:
* Using MDC with %MDC placeholders ensures that enriched logging does not significantly impact performance.
* This setup improves logging detail while maintaining efficient message processing.
MuleSoft Documentation on Mule Tracing: Mule Tracing Module
Log4j2 Documentation on MDC: Log4j2 MDC
NEW QUESTION # 98
A key Cl/CD capability of any enterprise solution is a testing framework to write and run repeatable tests.
Which component of Anypoint Platform provides the te6t automation capabilities for customers to use in their pipelines?
- A. MUnit
- B. Exchange Mocking Service
- C. Anypoint CLl
- D. Mule Maven Plugin
Answer: A
Explanation:
MUnit is the testing framework component of Anypoint Platform that provides test automation capabilities for customers to use in their CI/CD pipelines. MUnit allows developers to write, run, and automate unit and integration tests for Mule applications. It supports creating repeatable tests for various scenarios, ensuring that the application functions correctly and adheres to specified requirements. MUnit integrates seamlessly with Anypoint Studio, enabling efficient test creation and execution as part of the development lifecycle.
References:
* MUnit Overview
* Testing with MUnit
NEW QUESTION # 99
In preparation for a digital transformation initiative, an organization is reviewing related IT integration projects that failed for various for reason.
According to MuleSoft's surveys of global IT leaders, what is a common cause of IT project failure that this organization may likely discover in its assessment?
- A. Lack of alignment around business outcomes
- B. Following an Agile delivery methodology
- C. Spending too much time on enablement
- D. Reliance on an Integration-Platform-as-a-Service (iPaaS)
Answer: A
NEW QUESTION # 100
A Kubernetes controller automatically adds another pod replica to the resource pool in response to increased application load.
Which scalability option is the controller implementing?
- A. Horizontal
- B. Diagonal
- C. Down
- D. Vertical
Answer: A
Explanation:
The Kubernetes controller is implementing horizontal scalability by adding another pod replica in response to increased application load. Horizontal scaling involves adding more instances of a service or application to handle the increased load, as opposed to vertical scaling, which would involve adding more resources (CPU, RAM) to a single instance. Horizontal scaling is a key feature of cloud-native applications and is supported by Kubernetes to ensure high availability and performance.
References:
* Kubernetes Horizontal Pod Autoscaling
* Understanding Horizontal vs. Vertical Scaling
NEW QUESTION # 101
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?
- A. 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 - B. Orders API truststore: The Orders API public key
Process Orders keystore: The Process Orders private key and public key - C. Orders API truststore: The Orders API private key and public key
Process Orders keystore: The Process Orders private key public key - D. 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
Answer: D
NEW QUESTION # 102
......
New (2026) Salesforce MuleSoft-Integration-Architect-I Exam Dumps: https://www.test4cram.com/MuleSoft-Integration-Architect-I_real-exam-dumps.html
Updated MuleSoft-Integration-Architect-I Exam Dumps - PDF Questions and Testing Engine: https://drive.google.com/open?id=1IRF2QncHamLyplY_69Lr3IlUNe7HJ7h1