[Sep-2025] Dumps Brief Outline Of The MuleSoft-Integration-Architect-I Exam - Free4Torrent
MuleSoft-Integration-Architect-I Training & Certification Get Latest Salesforce MuleSoft
NEW QUESTION # 81
A global organization operates datacenters in many countries. There are private network links between these datacenters because all business data (but NOT metadata) must be exchanged over these private network connections.
The organization does not currently use AWS in any way.
The strategic decision has Just been made to rigorously minimize IT operations effort and investment going forward.
What combination of deployment options of the Anypoint Platform control plane and runtime plane(s) best serves this organization at the start of this strategic journey?
- A. MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in multiple AWS regions
- B. MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in each datacenter
- C. MuleSoft-hosted Anypoint Platform control plane CloudHub Shared Worker Cloud in multiple AWS regions
- D. Anypoint Platform - Private Cloud Edition Customer-hosted runtime plane in each datacenter
Answer: B
Explanation:
Correct answer is MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in each datacenter There are two things to note about the question which can help us figure out correct answer.. * Business data must be exchanged over these private network connections which means we can not use MuleSoft provided Cloudhub option. So we are left with either customer hosted runtime in external cloud provider or customer hosted runtime in their own premises. As customer does not use AWS at the moment. Hence that don't have the immediate option of using Customer-hosted runtime plane in multiple AWS regions. hence the most suitable option for runtime plane is Customer-hosted runtime plane in each datacenter * Metadata has no limitation to reside in organization premises. Hence for control plane MuleSoft hosted Anypoint platform can be used as a strategic solution.
Hybrid is the best choice to start. Mule hosted Control plane and Customer hosted Runtime to start with.
Once they mature in cloud migration, everything can be in Mule hosted.
NEW QUESTION # 82
An organization has decided on a cloud migration strategy to minimize the organization's own IT resources. Currently the organization has all of its new applications running on its own premises and uses an on-premises load balancer that exposes all APIs under the base URL (https://api.rutujar.com).
As part of migration strategy, the organization is planning to migrate all of its new applications and load balancer CloudHub.
What is the most straightforward and cost-effective approach to Mule application deployment and load balancing that preserves the public URL's?
- A. Deploy the Mule application to Cloudhub
Create a CNAME record for base URL( httpsr://api.rutujar.com) in the Cloudhub shared load balancer that points to the A record of theon-premises load balancer Apply mapping rules in SLB to map URLto their corresponding Mule applications - B. Deploy the Mule application to Cloudhub
Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the Cloudhub dedicated load balancer Apply mapping rules in DLB to map URLto their corresponding Mule applications - C. Deploy the Mule application to Cloudhub
Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub shared load balancer Apply mapping rules in SLB to map URLto their corresponding Mule applications - D. For each migrated Mule application, deploy an API proxy application to Cloudhub with all traffic to the mule applications routed through a Cloud Hub Dedicated load balancer (DLB) Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub dedicated load balancer Apply mapping rules in DLB to map each API proxy application who is responding new application
Answer: B
NEW QUESTION # 83
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?
- A. On Error Continue scope to be used to call in case of error again
- B. Until Successful scope can be implemented while calling backend API's
- C. Alerts can be configured in Mule runtime so that backend team can be communicated when services are down
- D. Create a batch job with all requests being sent to backend using that job as per the availability of backend API's
Answer: B
Explanation:
Correct answer is Untill Successful scope can be implemented while calling backend API's The Until Successful scope repeatedly triggers the scope's components (including flow references) until they all succeed or until a maximum number of retries is exceeded The scope provides option to control the max number of retries and the interval between retries The scope can execute any sequence of processors that may fail for whatever reason and may succeed upon retry
NEW QUESTION # 84
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.
References:
* MuleSoft Documentation on JMS Connector: MuleSoft JMS Connector
* JMS 2.0 Specification: Oracle JMS 2.0
NEW QUESTION # 85
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. A MuleSoft-managed repository at repository.mulesoft.org
- B. API Community Manager
- C. The Anypoint Object Store service at cloudhub.io
- D. A binary artifact repository
Answer: B
NEW QUESTION # 86
A Mule application is being designed to do the following:
Step 1: Read a SalesOrder message from a JMS queue, where each SalesOrder consists of a header and a list of SalesOrderLineltems.
Step 2: Insert the SalesOrder header and each SalesOrderLineltem into different tables in an RDBMS.
Step 3: Insert the SalesOrder header and the sum of the prices of all its SalesOrderLineltems into a table In a different RDBMS.
No SalesOrder message can be lost and the consistency of all SalesOrder-related information in both RDBMSs must be ensured at all times.
What design choice (including choice of transactions) and order of steps addresses these requirements?
- A. 1) Read and acknowledge the JMS message (NOT in an XA transaction)
2) In a NEW XA transaction, perform BOTH DB inserts - B. 1) Read the JMS message in an XA transaction
2) In the SAME XA transaction, perform BOTH DB inserts but do NOT acknowledge the JMS message - C. 1) Read the JMS message (NOT in an XA transaction)
2) Perform EACH DB insert in a SEPARATE DB transaction
3) Acknowledge the JMS message - D. 1) Read the JMS message (NOT in an XA transaction)
2) Perform BOTH DB inserts in ONE DB transaction
3) Acknowledge the JMS message
Answer: D
Explanation:
* Option A says "Perform EACH DB insert in a SEPARATE DB transaction". In this case if first DB insert is successful and second one fails then first insert won't be rolled back causing inconsistency. This option is ruled out.
* Option D says Perform BOTH DB inserts in ONE DB transaction.
Rule of thumb is when one or more DB connections are required we must use XA transaction as local transactions support only one resource. So this option is also ruled out.
* Option B acknowledges the before DB processing, so message is removed from the queue. In case of system failure at later point, message can't be retrieved.
* Option C is Valid: Though it says "do not ack JMS message", message will be auto acknowledged at the end of transaction. Here is how we can ensure all components are part of XA transaction: https://docs.mulesoft.com/jms-connector/1.7/jms-transactions Additional Information about transactions:
* XA Transactions - You can use an XA transaction to group together a series of operations from multiple transactional resources, such as JMS, VM or JDBC resources, into a single, very reliable, global transaction.
* The XA (eXtended Architecture) standard is an X/Open group standard which specifies the interface between a global transaction manager and local transactional resource managers.
The XA protocol defines a 2-phase commit protocol which can be used to more reliably coordinate and sequence a series of "all or nothing" operations across multiple servers, even servers of different types
* Use JMS ack if
- Acknowledgment should occur eventually, perhaps asynchronously
- The performance of the message receipt is paramount
- The message processing is idempotent
- For the choreography portion of the SAGA pattern
* Use JMS transactions
- For all other times in the integration you want to perform an atomic unit of work
- When the unit of work comprises more than the receipt of a single message
- To simply and unify the programming model (begin/commit/rollback)
NEW QUESTION # 87
What is the MuleSoft-recommended best practice to share the connector and configuration information among the APIs?
- A. Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API
- B. Build another System API that connects to the database, and refactor all the other APIs to make requests through the new System API to access the database
- C. Create an API proxy for each System API and share the Database connector configuration with all the API proxies via an automated policy
- D. Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically
Answer: A
NEW QUESTION # 88
A Mule application uses the Database connector.
What condition can the Mule application automatically adjust to or recover from without needing to restart or redeploy the Mule application?
- A. The database server was unavailable for four hours due to a major outage but is now fully operational again
- B. One of the stored procedures being called by the Mule application has been renamed
- C. The credentials for accessing the database have been updated and the previous credentials are no longer valid
- D. The database server has been updated and hence the database driver library/JAR needs a minor version upgrade
Answer: A
Explanation:
* Any change in the application will require a restart except when the issue outside the app. For below situations , you would need to redeploy the code after doing necessary changes
-- One of the stored procedures being called by the Mule application has been renamed. In this case, in the Mule application you will have to do changes to accommodate the new stored procedure name.
-- Required redesign of Mule applications to follow microservice architecture principles. As code is changed, deployment is must
-- If the credentials changed and you need to update the connector or the properties.
-- The credentials for accessing the database have been updated and the previous credentials are no longer valid. In this situation you need to restart or redeploy depending on how credentials are configured in Mule application.
* So Correct answer is The database server was unavailable for four hours due to a major outage but is now fully operational again as this is the only external issue to application.
NEW QUESTION # 89
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. A load-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes.
- B. An SLA for the upstream API CANNOT be provided.
- C. The invocation of the downstream API will run to completion without timing out.
- D. A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes.
Answer: B
Explanation:
An SLA for the upstream API CANNOT be provided.
NEW QUESTION # 90
A manufacturing company plans 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 choice of runtime plane meets these organizational requirements?
- A. Anypoint Service Mesh
- B. CloudHub 2.0
- C. Customer-hosted self-provisioned runtime plane
- D. Anypoint Runtime Fabric
Answer: B
NEW QUESTION # 91
An API client is implemented as a Mule application that includes an HTTP Request operation using a default configuration. The HTTP Request operation invokes an external API that follows standard HTTP status code conventions, which causes the HTTP Request operation to return a 4xx status code.
What is a possible cause of this status code response?
- A. The HTTP response cannot be interpreted by the HTTP Request operation of the Mule application after it was received from the external API
- B. The external API reported an error with the HTTP request that was received from the outbound HTTP Request operation of the Mule application
- C. An error occurred inside the external API implementation when processing the HTTP request that was received from the outbound HTTP Request operation of the Mule application
- D. The external API reported that the API implementation has moved to a different external endpoint
Answer: B
Explanation:
Correct choice is: "The external API reported an error with the HTTP request that was received from the outbound HTTP Request operation of the Mule application" Understanding HTTP 4XX Client Error Response Codes : A 4XX Error is an error that arises in cases where there is a problem with the user's request, and not with the server.
Such cases usually arise when a user's access to a webpage is restricted, the user misspells the URL, or when a webpage is nonexistent or removed from the public's view.
In short, it is an error that occurs because of a mismatch between what a user is trying to access, and its availability to the user - either because the user does not have the right to access it, or because what the user is trying to access simply does not exist. Some of the examples of 4XX errors are
400 Bad Request The server could not understand the request due to invalid syntax. 401 Unauthorized Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated".
That is, the client must authenticate itself to get the requested response. 403 Forbidden The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401, the client's identity is known to the server. 404 Not Found The server can not find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 to hide the existence of a resource from an unauthorized client. This response code is probably the most famous one due to its frequent occurrence on the web. 405 Method Not Allowed The request method is known by the server but has been disabled and cannot be used. For example, an API may forbid DELETE-ing a resource. The two mandatory methods, GET and HEAD, must never be disabled and should not return this error code. 406 Not Acceptable This response is sent when the web server, after performing server-driven content negotiation, doesn't find any content that conforms to the criteria given by the user agent. The external API reported that the API implementation has moved to a different external endpoint cannot be the correct answer as in this situation 301 Moved Permanently The URL of the requested resource has been changed permanently. The new URL is given in the response.
---------------------------------------------------------------------------------------------------------------------------------------- In Lay man's term the scenario would be: API CLIENT -> MuleSoft API - HTTP request "Hey, API..
process this" -> External API API CLIENT <- MuleSoft API - http response "I'm sorry Client.. something is wrong with that request" <- (4XX) External API
NEW QUESTION # 92
A mule application must periodically process a large dataset which varies from 6 GB lo 8 GB from a back-end database and write transform data lo an FTPS server using a properly configured bad job scope.
The performance requirements of an application are approved to run in the cloud hub 0.2 vCore with 8 GB storage capacity and currency requirements are met.
How can the high rate of records be effectively managed in this application?
- A. Use streaming with a file store repeatable strategy for reading records from the database and batch aggregator with an optimal size
- B. Use streaming with a file store repeatable strategy reading records from the database and batch aggregator without any required configuration
- C. Use streaming with a file storage repeatable strategy for reading records from the database and batch aggregator with streaming to write to FTPS
- D. Use streaming with an in-memory reputable store strategy for reading records from the database and batch aggregator with streaming to write to FTPS
Answer: C
NEW QUESTION # 93
A new Mule application under development must implement extensive data transformation logic. Some of the data transformation functionality is already available as external transformation services that are mature and widely used across the organization; the rest is highly specific to the new Mule application.
The organization follows a rigorous testing approach, where every service and application must be extensively acceptance tested before it is allowed to go into production.
What is the best way to implement the data transformation logic for this new Mule application while minimizing the overall testing effort?
- A. Implement transformation logic in the new Mute application using DataWeave, invoking existing transformation services when possible
- B. Extend the existing transformation services with new transformation logic and Invoke them from the new Mule application
- C. Implement and expose all transformation logic as mlaoservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application
- D. Implement transformation logic in the new Mute application using DataWeave, replicating the transformation logic of existing transformation services
Answer: A
Explanation:
Correct answer is Implement transformation logic in the new Mule application using DataWeave, invoking existing transformation services when possible. * The key here minimal testing effort, "Extend existing transformation logic" is not a feasible option because additional functionality is highly specific to the new Mule application so it should not be a part of commonly used functionality. So this option is ruled out. *
"Implement transformation logic in the new Mule application using DataWeave, replicating the transformation logic of existing transformation services" Replicating the transformation logic of existing transformation services will cause duplicity of code. So this option is ruled out. * "Implement and expose all transformation logic as microservices using DataWeave, so it can be reused by any application component that needs it, including the new Mule application" as question specifies that the transformation is app specific and wont be used outside
NEW QUESTION # 94
What is true about the network connections when a Mule application uses a JMS connector to interact with a JMS provider (message broker)?
- A. The AMQP protocol can be used by the JMS connector to portably establish connections to various types of JMS providers
- B. The JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider
- C. To receive messages into the Mule application, the JMS provider initiates a network connection to the JMS connector and pushes messages along this connection
- D. To complete sending a JMS message, the JMS connector must establish a network connection with the JMS message recipient
Answer: B
Explanation:
* To send message or receive JMS (Java Message Service) message no separate network connection need to be established. So option A, C and D are ruled out.
Correct answer: The JMS connector supports both sending and receiving of JMS
* JMS Connector enables sending and receiving messages to queues and topics for any message service that implements the JMS specification.
* JMS is a widely used API for message-oriented middleware.
* It enables the communication between different components of a distributed application to be loosely coupled, reliable, and asynchronous.
MuleSoft Doc Reference: https://docs.mulesoft.com/jms-connector/1.7/
NEW QUESTION # 95
A DevOps team has adequate observability of individual system behavior and performance, but it struggles to track the entire lifecycle of each request across different microservices.
Which additional observability approach should this team consider adopting?
- A. Tracing
- B. Data mining
- C. Analytics
- D. Metrics
Answer: D
NEW QUESTION # 96
Refer to the exhibit.
A Mule application is deployed to a cluster of two customer-hosted Mute runtimes. The Mute application has a flow that polls a database and another flow with an HTTP Listener.
HTTP clients send HTTP requests directly to individual cluster nodes.
What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has railed, but before that node is restarted?
- A. Database polling continues All HTTP requests continue to be accepted, but requests to the failed node Incur increased latency
- B. Database polling stops All HTTP requests continue to be accepted
- C. Database polling continues Only HTTP requests sent to the remaining node continue to be accepted
- D. Database polling stops All HTTP requests are rejected
Answer: C
Explanation:
Correct answer is Database polling continues Only HTTP requests sent to the remaining node continue to be accepted. : Architecture descripted in the question could be described as follows.When node 1 is down , DB polling will still continue via node 2 . Also requests which are coming directly to node 2 will also be accepted and processed in BAU fashion. Only thing that wont work is when requests are sent to Node 1 HTTP connector. The flaw with this architecture is HTTP clients are sending HTTP requests directly to individual cluster nodes. By default, clustering Mule runtime engines ensures high system availability. If a Mule runtime engine node becomes unavailable due to failure or planned downtime, another node in the cluster can assume the workload and continue to process existing events and messages
NEW QUESTION # 97
Which productivity advantage does Anypoint Platform have to both implement and manage an AP?
- A. Automatic API semantic versioning
- B. Automatic API specification generation
- C. Automatic API proxy generation
- D. Automatic API governance
Answer: D
NEW QUESTION # 98
An application load balancer routes requests to a RESTful web API secured by Anypoint Flex Gateway.
Which protocol is involved in the communication between the load balancer and the Gateway?
- A. SMTP
- B. HTTPS
- C. SFTP
- D. LDAP
Answer: B
Explanation:
An application load balancer routes requests to a RESTful web API secured by Anypoint Flex Gateway using the HTTPS protocol. HTTPS (HyperText Transfer Protocol Secure) ensures that the communication between the load balancer and the gateway is encrypted and secure, protecting the data from eavesdropping and tampering. HTTPS is the standard protocol for secure communication over the internet, especially for APIs handling sensitive data.
References:
* Securing APIs with HTTPS
* Understanding HTTPS
NEW QUESTION # 99
A corporation has deployed Mule applications to different customer-hosted Mule runtimes. Mule applications deployed to these Mule runtimes are managed by Anypoint Platform.
What needs to be installed or configured (if anything) to monitor these Mule applications from Anypoint Monitoring, and how is monitoring data from each Mule application sent to Anypoint Monitoring?
- A. Install a Runtime Manager agent on each Mule runtime.
Each Runtime Manager agent sends monitoring data from the Mule applications running in its Mule runtime to Runtime Manager, then Runtime Manager sends monitoring data to Anypoint Monitoring. - B. Leave the out-of-the-box Anypoint Monitoring agent unchanged in its default Mule runtime installation.
Each Anypoint Monitoring agent sends monitoring data from the Mule applications running in its Mule runtime to Runtime Manager, then Runtime Manager sends monitoring data to Anypoint Monitoring. - C. Install an Anypoint Monitoring agent on each Mule runtime.
Each Anypoint Monitoring agent sends monitoring data from the Mule applications running in its Mule runtime to Anypoint Monitoring. - D. Enable monitoring of individual Mule applications from the Runtime Manager application settings.
Runtime Manager sends monitoring data to Anypoint Monitoring for each deployed Mule application.
Answer: D
NEW QUESTION # 100
According to MuleSoft, a synchronous invocation of a RESTful API using HTTP to get an individual customer record from a single system is an example of which system integration interaction pattern?
- A. Batch
- B. Multicast
- C. One-way
- D. Request-Reply
Answer: D
Explanation:
A synchronous invocation of a RESTful API using HTTP to get an individual customer record from a single system exemplifies the request-reply interaction pattern. In this pattern, a client sends a request to a service and waits for a response. The interaction is synchronous because the client expects an immediate reply and is blocked until it receives the response.
This pattern is common in scenarios where the client needs to retrieve specific data or perform an action that requires immediate feedback from the server, such as retrieving a customer record from a database.
References
* MuleSoft Integration Patterns Documentation
* Request-Reply Pattern Overview
NEW QUESTION # 101
A travel company wants to publish a well-defined booking service API to be shared with its business partners.
These business partners have agreed to ONLY consume SOAP services and they want to get the service contracts in an easily consumable way before they start any development. The travel company will publish the initial design documents to Anypoint Exchange, then share those documents with the business partners. When using an API-led approach, what is the first design document the travel company should deliver to its business partners?
- A. Create a RAML API specification using any text editor
- B. Create a WSDL specification using any XML editor
- C. Create an OAS API specification in Design Center
- D. Create a SOAP API specification in Design Center
Answer: B
Explanation:
SOAP API specifications are provided as WSDL. Design center doesn't provide the functionality to create WSDL file. Hence WSDL needs to be created using XML editor
NEW QUESTION # 102
When a Mule application using VM queues is deployed to a customer-hosted cluster or multiple CloudHub v1.0 workers/replicas, how are messages consumed across the nodes?
- A. Sequentially, only from the primary node
- B. In a non-deterministic way
- C. Sequentially, from a dedicated Anypoint MQ queue
- D. Round-robin, within an XA transaction
Answer: C
NEW QUESTION # 103
Refer to the exhibit.
A customer is running Mule applications on Runtime Fabric for Self-Managed Kubernetes (RTF-BYOKS) in a multi-cloud environment.
Based on this configuration, how do Agents and Runtime Manager
communicate, and what Is exchanged between them?
- A. UBER, Dedicated NIO Selector Pool
- B. CPU_LITE, CPU_INTENSIVE
- C. Shared NIO Selector Pool, CPU_LITE
- D. BLOCKING_IO, UBER
Answer: D
NEW QUESTION # 104
Customer has deployed mule applications to different customer hosted mule run times. Mule applications are managed from Anypoint platform.
What needs to be configured to monitor these Mule applications from Anypoint monitoring and what sends monitoring data to Anypoint monitoring?
- A. Enable monitoring of individual applications from runtime manager application settings Runtime manager agent sends monitoring data from the mule applications to Anypoint monitoring
- B. Install runtime manager agent on each mule runtime
Runtime manager agent since monitoring data from the mule applications to Anypoint monitoring - C. Anypoint monitoring agent on each mule runtime
Anypoint monitoring agent sends monitoring data from the mule applications to Anypoint monitoring - D. By default, Anypoint monitoring agent will be installed on each Mule run time Anypoint Monitoring agent automatically sends monitoring data from the Mule applications to Anypoint monitoring
Answer: C
NEW QUESTION # 105
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?
- A. Call each API request in a separate route of a Parallel For Each scope
- B. Call each API request in a separate route of a Scatter-Gather
- C. Call each API request in a separate Async scope
- D. Call each API request in a separate lookup call from Dataweave reduce operator
Answer: 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.
NEW QUESTION # 106
......
Certification Training for MuleSoft-Integration-Architect-I Exam Dumps Test Engine: https://www.free4torrent.com/MuleSoft-Integration-Architect-I-braindumps-torrent.html
Salesforce MuleSoft MuleSoft-Integration-Architect-I Real Exam Questions and Answers FREE Updated: https://drive.google.com/open?id=18iJdje8h_yxNRTjpvE6Irfw1YJiPfKgI