The Best Salesforce MuleSoft-Integration-Architect-I Study Guides and Dumps of 2024

Top Salesforce MuleSoft-Integration-Architect-I Exam Audio Study Guide! Practice Questions Edition

NEW QUESTION # 21
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 scope After 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 environment What is the consequence of losing the replicas that run the Batch job instance?

• A. A new placement replica will be available and will take or processing the remaining 99,000 records
• B. The remaining 99000 records will be lost and left and processed
• C. The second replicas will take over processing the remaining
  99000 records
• D. A new replacement replica will be available and will be process all 1,00,000 records from scratch leading to duplicate record processing

Answer: C

NEW QUESTION # 22
Which Mulesoft feature helps users to delegate their access without sharing sensitive credentials or giving full control of accounts to 3rd parties?

• A. Certificates
• B. Connected apps
• C. client id enforcement policy
• D. Secure Scheme

Answer: B

Explanation:
Connected Apps
The Connected Apps feature provides a framework that enables an external application to integrate with Anypoint Platform using APIs through OAuth 2.0 and OpenID Connect. Connected apps help users delegate their access without sharing sensitive credentials or giving full control of their accounts to third parties. Actions taken by connected apps are audited, and users can also revoke access at any time. Note that some products do not currently include client IDs in this release of the Connected Apps feature. The Connected Apps feature enables you to use secure authentication protocols and control an app's access to user data. Additionally, end users can authorize the app to access their Anypoint Platform data.
Mule Ref Doc : https://docs.mulesoft.com/access-management/connected-apps-overview

NEW QUESTION # 23
A Mule application is running on a customer-hosted Mule runtime in an organization's network. The Mule application acts as a producer of asynchronous Mule events. Each Mule event must be broadcast to all interested external consumers outside the Mule application. The Mule events should be published in a way that is guaranteed in normal situations and also minimizes duplicate delivery in less frequent failure scenarios.
The organizational firewall is configured to only allow outbound traffic on ports 80 and 443. Some external event consumers are within the organizational network, while others are located outside the firewall.
What Anypoint Platform service is most idiomatic (used for its intended purpose) for publishing these Mule events to all external consumers while addressing the desired reliability goals?

• A. Anypoint MQ
• B. CloudHub VM queues
• C. CloudHub Shared Load Balancer
• D. Anypoint Exchange

Answer: A

Explanation:
Set the Anypoint MQ connector operation to publish or consume messages, or to accept (ACK) or not accept (NACK) a message.

NEW QUESTION # 24
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. HTTPS
• B. SMTP
• C. SFTP
• D. LDAP

Answer: A

NEW QUESTION # 25
An organization uses a set of customer-hosted Mule runtimes that are managed using the Mulesoft-hosted control plane. What is a condition that can be alerted on from Anypoint Runtime Manager without any custom components or custom coding?

• A. When a Mule runtime on a given customer-hosted server is experiencing high memory consumption during certain periods
• B. When a Mule runtime's customer-hosted server is about to run out of disk space
• C. When an SSL certificate used by one of the deployed Mule applications is about to expire
• D. When the Mute runtime license installed on a Mule runtime is about to expire

Answer: A

Explanation:
Correct answer is When a Mule runtime on a given customer-hosted server is experiencing high memory consumption during certain periods Using Anypoint Monitoring, you can configure two different types of alerts: Basic alerts for servers and Mule apps Limit per organization: Up to 50 basic alerts for users who do not have a Titanium subscription to Anypoint Platform You can set up basic alerts to trigger email notifications when a metric you are measuring passes a specified threshold. You can create basic alerts for the following metrics for servers or Mule apps: For on-premises servers and CloudHub apps: * CPU utilization * Memory utilization * Thread count Advanced alerts for graphs in custom dashboards in Anypoint Monitoring. You must have a Titanium subscription to use this feature. Limit per organization: Up to 20 advanced alerts

NEW QUESTION # 26
An organization is evaluating using the CloudHub shared Load Balancer (SLB) vs creating a CloudHub dedicated load balancer (DLB). They are evaluating how this choice affects the various types of certificates used by CloudHub deplpoyed Mule applications, including MuleSoft-provided, customer-provided, or Mule application-provided certificates.
What type of restrictions exist on the types of certificates that can be exposed by the CloudHub Shared Load Balancer (SLB) to external web clients over the public internet?

• A. Only customer-provided wildcard certificates are exposed.
• B. Only customer-provided self-signed certificates are exposed.
• C. Only underlying Mule application certificates are exposed (pass-through)
• D. Only MuleSoft-provided certificates are exposed.

Answer: D

Explanation:
https://docs.mulesoft.com/runtime-manager/dedicated-load-balancer-tutorial

NEW QUESTION # 27
What is an example of data confidentiality?

• A. Providing a server's private key to a client for secure decryption of data during a two-way SSL handshake
• B. Encrypting a file containing personally identifiable information (PV)
• C. Signing a file digitally and sending it using a file transfer mechanism
• D. De-masking a person's Social Security number while inserting it into a database

Answer: B

NEW QUESTION # 28
Refer to the exhibit.

Anypoint Platform supports role-based access control (RBAC) to features of the platform. An organization has configured an external Identity Provider for identity management with Anypoint Platform.
What aspects of RBAC must ALWAYS be controlled from the Anypoint Platform control plane and CANNOT be controlled via the external Identity Provider?

• A. Assigning Anypoint Platform role(s) to a user
• B. Removing a user's access to Anypoint Platform when they no longer work for the organization
• C. Assigning Anypoint Platform permissions to a role
• D. Controlling the business group within Anypoint Platform to which the user belongs

Answer: C

Explanation:
* By default, Anypoint Platform performs its own user management
- For user management, one external IdP can be integrated with the Anypoint Platform organization (note: not at business group level)
- Permissions and access control are still enforced inside Anypoint Platform and CANNOT be controlled via the external Identity Provider * As the Anypoint Platform organization administrator, you can configure identity management in Anypoint Platform to set up users for single sign-on (SSO). * You can map users in a federated organization's group to a role which also gives the flexibility of controlling the business group within Anypoint Platform to which the user belongs to. Also user can nbe removed from external identity management system when they no longer work for the organization. So they wont be able to authenticate using SSO to login to Anypoint Platform. * Using external identity we can no change permissions of a particular role in Mulesoft Anypoint platform.
* So Correct answer is Assigning Anypoint Platform permissions to a role

NEW QUESTION # 29
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 Core Logger components.
  In log4j2.xmI files, change the appender''s pattern layout to use %asyncLogger placeholder and then assign the appender to an AsyncLogger element.
• C. In the flows, add Mule Tracing module Set logging variable operations before any Core Logger 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.
• D. In the flows, wrap Logger components in Async scopes. In log4j2.xmI files, change the appender's pattern layout to use the %asyncLogger placeholder and then assign the appender to a Logger or Root element.

Answer: A

NEW QUESTION # 30
What is a key difference between synchronous and asynchronous logging from Mule applications?

• A. Synchronous logging writes log messages in a single logging thread but does not block the Mule event being processed by the next event processor
• B. Asynchronous logging can improve Mule event processing throughput while also reducing the processing time for each Mule event
• C. Asynchronous logging produces more reliable audit trails with more accurate timestamps
• D. Synchronous logging within an ongoing transaction writes log messages in the same thread that processes the current Mule event

Answer: B

Explanation:
Types of logging:
A) Synchronous: The execution of thread that is processing messages is interrupted to wait for the log message to be fully handled before it can continue.
* The execution of the thread that is processing your message is interrupted to wait for the log message to be fully output before it can continue
* Performance degrades because of synchronous logging
* Used when the log is used as an audit trail or when logging ERROR/CRITICAL messages
* If the logger fails to write to disk, the exception would raise on the same thread that's currently processing the Mule event. If logging is critical for you, then you can rollback the transaction.


B) Asynchronous:
* The logging operation occurs in a separate thread, so the actual processing of your message won't be delayed to wait for the logging to complete
* Substantial improvement in throughput and latency of message processing
* Mule runtime engine (Mule) 4 uses Log4j 2 asynchronous logging by default
* The disadvantage of asynchronous logging is error handling.
* If the logger fails to write to disk, the thread doing the processing won't be aware of any issues writing to the disk, so you won't be able to rollback anything. Because the actual writing of the log gets differed, there's a chance that log messages might never make it to disk and get lost, if Mule were to crash before the buffers are flushed.
------------------------------------------------------------------------------------------------------------------ So Correct answer is: Asynchronous logging can improve Mule event processing throughput while also reducing the processing time for each Mule event

NEW QUESTION # 31
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?

• A. 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
• B. Set region property to Europe (eu-de) in runtime manager for all the mule application No need to change the naming convention
• C. Set region property to Europe (eu-de) in API manager for all the mule application No need to change the naming convention
• D. 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

Answer: D

NEW QUESTION # 32
A payment processing company has implemented a Payment Processing API Mule application to process credit card and debit card transactions, Because the Payment Processing API handles highly sensitive information, the payment processing company requires that data must be encrypted both In-transit and at-rest.
To meet these security requirements, consumers of the Payment Processing API must create request message payloads in a JSON format specified by the API, and the message payload values must be encrypted.
How can the Payment Processing API validate requests received from API consumers?

• A. A Transport Layer Security (TLS) - Inbound policy can be applied in API Manager to decrypt the message payload and the Mule application implementation can then use the JSON Validation module to validate the JSON data
• B. The Mule application implementation can use the APIkit module to decrypt and then validate the JSON data
• C. The Mule application implementation can use DataWeave to decrypt the message payload and then use the JSON Scheme Validation module to validate the JSON data
• D. The Mule application implementation can use the Validation module to decrypt and then validate the JSON data

Answer: A

NEW QUESTION # 33
Organization wants to achieve high availability goal for Mule applications in customer hosted runtime plane. Due to the complexity involved, data cannot be shared among of different instances of same Mule application. What option best suits to this requirement considering high availability is very much critical to the organization?

• A. Use third party product to implement load balancer
• B. Use persistent object store
• C. High availability can be achieved only in CloudHub
• D. The cluster can be configured

Answer: A

Explanation:
High availability is about up-time of your application
A) High availability can be achieved only in CloudHub isn't correct statement. It can be achieved in customer hosted runtime planes as well B) An object store is a facility for storing objects in or across Mule applications. Mule runtime engine (Mule) uses object stores to persist data for eventual retrieval. It can be used for disaster recovery but not for High Availability. Using object store can't guarantee that all instances won't go down at once. So not an appropriate choice.
Reference:
C) High availability can be achieved by below two models for on-premise MuleSoft implementations.
1) Mule Clustering - Where multiple Mule servers are available within the same cluster environment and the routing of requests will be done by the load balancer. A cluster is a set of up to eight servers that act as a single deployment target and high-availability processing unit. Application instances in a cluster are aware of each other, share common information, and synchronize statuses. If one server fails, another server takes over processing applications. A cluster can run multiple applications. ( refer left half of the diagram) In given scenario, it's mentioned that 'data cannot be shared among of different instances'. So this is not a correct choice.
2) Load balanced standalone Mule instances - The high availability can be achieved even without cluster, with the usage of third party load balancer pointing requests to different Mule servers. This approach does not share or synchronize data between Mule runtimes. Also high availability achieved as load balanced algorithms can be implemented using external load balancer. ( refer right half of the diagram)

NEW QUESTION # 34
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?

• A. Use MUnit to simulate standard responses from the back-end system.
  Then conduct performance test to identify other bottlenecks in the system
• B. Conduct scaled-down performance tests in the staging environment against rate-limiting back-end system. Then upscale performance results to full production scale
• C. 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
• D. 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

Answer: C

NEW QUESTION # 35
Why would an Enterprise Architect use a single enterprise-wide canonical data model (CDM) when designing an integration solution using Anypoint Platform?

• A. To reduce dependencies when integrating multiple systems that use different data formats
• B. To automate Al-enabled API implementation generation based on normalized backend databases from separate vendors
• C. To leverage a data abstraction layer that shields existing Mule applications from nonbackward compatible changes to the model's data structure
• D. To remove the need to perform data transformation when processing message payloads in Mule applications

Answer: A

NEW QUESTION # 36
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 the JMS message (NOT in an XA transaction)
  2) Perform BOTH DB inserts in ONE DB transaction
  3) Acknowledge the JMS message
• B. 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
• C. 1) Read and acknowledge the JMS message (NOT in an XA transaction)
  2) In a NEW XA transaction, perform BOTH DB inserts
• D. 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

Answer: A

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 # 37
Refer to the exhibit.

A Mule application is being designed to be deployed to several CIoudHub workers. The Mule application's integration logic is to replicate changed Accounts from Satesforce to a backend system every 5 minutes.
A watermark will be used to only retrieve those Satesforce Accounts that have been modified since the last time the integration logic ran.
What is the most appropriate way to implement persistence for the watermark in order to support the required data replication integration logic?

• A. Persistent Object Store
• B. Persistent Cache Scope
• C. Persistent VM Queue
• D. Persistent Anypoint MQ Queue

Answer: A

Explanation:
* An object store is a facility for storing objects in or across Mule applications. Mule uses object stores to persist data for eventual retrieval.
* Mule provides two types of object stores:
1) In-memory store - stores objects in local Mule runtime memory. Objects are lost on shutdown of the Mule runtime.
2) Persistent store - Mule persists data when an object store is explicitly configured to be persistent.
In a standalone Mule runtime, Mule creates a default persistent store in the file system. If you do not specify an object store, the default persistent object store is used.
MuleSoft Reference: https://docs.mulesoft.com/mule-runtime/3.9/mule-object-stores

NEW QUESTION # 38
A customer wants to use the mapped diagnostic context (MDC) and logging variables to enrich its logging and improve tracking by providing more context in the logs.
The customer also wants to improve the throughput and lower the latency of message processing.
As an Mulesoft integration architect can you advise, what should the customer implement to meet these requirements?

• A. Useasync logger at the level equal to DEBUG orTRACEand use pattern
  layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables
• B. Use synchronous logging at the INFO DEBUG or Trace level and use pattern layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables
• C. Use synchronous logging and use pattern layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables
• D. Useasync logger at the level greater than INFO and use pattern layout with [%MDC] in the log4j2,xml configuration file and then configure the logging variables

Answer: D

NEW QUESTION # 39
......

Valid MuleSoft-Integration-Architect-I Exam Updates - 2024 Study Guide: https://www.testsimulate.com/MuleSoft-Integration-Architect-I-study-materials.html