Free MuleSoft-Integration-Architect-I Exam Braindumps
Salesforce Certified MuleSoft Integration Architect I Questions 66–70 (page: 15)

Updated On: 10-Feb-2026

An organization is sizing an Anypoint VPC to extend their internal network to Cloudhub. For this sizing calculation, the organization assumes 150 Mule applications will be deployed among three(3) production environments and will use Cloudhub's default zero-downtime feature. Each Mule application is expected to be configured with two(2) Cloudhub workers.This is expected to result in several Mule application deployments per hour.

  1. 10.0.0.0/21(2048 IPs)
  2. 10.0.0.0/22(1024IPs)
  3. 10.0.0.0/23(512 IPs)
  4. 10.0.0.0/24(256 IPs)

Answer(s): A

Explanation:

* When you create an Anypoint VPC, the range of IP addresses for the network must be specified in the form of a Classless Inter-Domain Routing (CIDR) block, using CIDR notation.
* This address space is reserved for Mule workers, so it cannot overlap with any address space used in your data center if you want to peer it with your VPC.
* To calculate the proper sizing for your Anypoint VPC, you first need to understand that the number of dedicated IP addresses is not the same as the number of workers you have deployed.
* For each worker deployed to CloudHub, the following IP assignation takes place: For better fault tolerance, the VPC subnet may be divided into up to four Availability Zones.
* A few IP addresses are reserved for infrastructure. At least two IP addresses per worker to perform at zero-downtime.
* Hence in this scenario 2048 IP's are required to support the requirement.



Refer to the exhibit.



This Mule application is deployed to multiple Cloudhub workers with persistent queue enabled. The retrievefile flow event source reads a CSV file from a remote SFTP server and then publishes each record in the CSV file to a VM queue. The processCustomerRecords flow's VM Listner receives messages from the same VM queue and then processes each message separately. How are messages routed to the cloudhub workers as messages are received by the VM Listener?

  1. Each message is routed to ONE of the Cloudhub workers in a DETERMINSTIC round robin fashion thereby EXACTLY BALANCING messages among the cloudhub workers
  2. Each messages routes to ONE of the available Clouhub workers in a NON- DETERMINSTIC non round-robin fashion thereby APPROXIMATELY BALANCING messages among the cloudhub workers
  3. Each message is routed to the SAME Cloudhub worker that retrieved the file, thereby BINDING ALL messages to ONLY that ONE Cloudhub worker
  4. Each message is duplicated to ALL of the Cloudhub workers, thereby SHARING EACH message with ALL the Cloudhub workers.

Answer(s): B



A mule application is being designed to perform product orchestration. The Mule application needs to join together the responses from an inventory API and a Product Sales History API with the least latency.
To minimize the overall latency.
What is the most idiomatic (used for its intended purpose) design to call each API request in the Mule application?

  1. Call each API request in a separate lookup call from Dataweave reduce operator
  2. Call each API request in a separate route of a Scatter-Gather
  3. Call each API request in a separate route of a Parallel For Each scope
  4. Call each API request in a separate Async scope

Answer(s): B

Explanation:

Scatter-Gather sends a request message to multiple targets concurrently. It collects the responses from all routes, and aggregates them into a single message.


Reference:

https://docs.mulesoft.com/mule-runtime/4.3/scatter-gather-concept



An organization will deploy Mule applications to Cloudhub, Business requirements mandate that all application logs be stored ONLY in an external splunk consolidated logging service and NOT in Cloudhub.
In order to most easily store Mule application logs ONLY in Splunk, how must Mule application logging be configured in Runtime Manager, and where should the log4j2 splunk appender be defined?

  1. Keep the default logging configuration in RuntimeManager
    Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manager to support at Mule application deployments.
  2. Disable Cloudhub logging in Runtime Manager
    Define the splunk appender in EACH Mule application's log4j2.xml file
  3. Disable Cloudhub logging in Runtime Manager
    Define the splunk appender in ONE global log4j.xml file that is uploaded once to Runtime Manger to support at Mule application deployments.
  4. Keep the default logging configuration in Runtime Manager
    Define the Splunk appender in EACH Mule application log4j2.xml file

Answer(s): B

Explanation:

By default, CloudHub replaces a Mule application's log4j2.xml file with a CloudHub log4j2.xml file. In CloudHub, you can disable the CloudHub provided Mule application log4j2 file. This allows integrating Mule application logs with custom or third-party log management systems



A Mule application is synchronizing customer data between two different database systems.
What is the main benefit of using XA transaction over local transactions to synchronize these two database system?

  1. Reduce latency
  2. Increase throughput
  3. Simplifies communincation
  4. Ensure consistency

Answer(s): D

Explanation:

* XA transaction add tremendous latency so "Reduce Latency" is incorrect option XA transactions define "All or No" commit protocol.
* Each local XA resource manager supports the A.C.I.D properties (Atomicity, Consistency, Isolation, and Durability).
--------------------------------------------------------------------------------------------------------------------- So correct choice is "Ensure consistency"


Reference:

https://docs.mulesoft.com/mule-runtime/4.3/xa-transactions



Viewing page 15 of 56
Viewing questions 71 - 75 out of 273 questions


Post your Comments and Discuss Salesforce MuleSoft-Integration-Architect-I exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!