Salesforce MULESOFT-INTEGRATION-ARCHITECT-I Online Practice Questions and Exam Preparation

Salesforce MULESOFT-INTEGRATION-ARCHITECT-I Online Questions & Answers

• Question 191:

  An organization plans to migrate its deployment environment from an onpremises cluster to a Runtime Fabric (RTF) cluster. The on-premises Mule applications are currently configured with persistent object stores.

  There is a requirement to enable Mule applications deployed to the RTF cluster to store and share data across application replicas and through restarts of the entire RTF cluster,

  How can these reliability requirements be met?

  A. Replace persistent object stores with persistent VM queues in each Mule application deployment
  B. Install the Object Store pod on one of the cluster nodes
  C. Configure Anypoint Object Store v2 to share data between replicas in the RTF cluster
  D. Configure the Persistence Gateway in the RTF installation
  C. Configure Anypoint Object Store v2 to share data between replicas in the RTF cluster

  ---

  Explanation/Reference:

  To meet the reliability requirements for Mule applications deployed to a Runtime Fabric (RTF) cluster, where data needs to be shared across application replicas and persist through restarts, the best approach is to use Anypoint Object Store

  v2. This service is designed to provide persistent storage that can be shared among different application instances and across restarts. Steps include:

  Configure Object Store v2: Set up Anypoint Object Store v2 in the Mule application to handle data storage needs.

  Persistent Data Handling: Ensure that the configuration allows data to be shared and persist, meeting the requirements for reliability and consistency. This solution leverages MuleSoft's cloud-based storage service optimized for these use

  cases, ensuring data integrity and availability.

  References:

  MuleSoft Documentation on Object Store v2

  Configuring Persistent Data Storage in MuleSoft

• Question 192:

  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 the Validation module to decrypt and then validate the JSON data
  D. 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
  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

  ---

  Explanation/Reference:

  To ensure that data is encrypted both in-transit and at-rest, and to validate incoming requests to the Payment Processing API, the following approach is recommended:

  TLS Inbound Policy: Apply a Transport Layer Security (TLS) -Inbound policy in API Manager. This policy ensures that the data is encrypted during transmission and can be decrypted by the API Manager before it reaches the Mule application.

  Decryption: With the TLS policy applied, the message payload is decrypted when it is received by the API Manager.

  JSON Validation: After decryption, the Mule application can use the JSON Validation module to validate the structure and content of the JSON data. This ensures that the payload conforms to the specified format and contains valid data. This

  approach ensures that data is securely transmitted and properly validated upon receipt.

  References:

  Transport Layer Security (TLS) Policies

  JSON Validation Module

• Question 193:

  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 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
  B. 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
  C. 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
  D. 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
  A. 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

  ---

  Explanation/Reference:

  Reference: https://docs.mulesoft.com/mule-runtime/4.4/transaction-management

• Question 194:

  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 storage repeatable strategy for reading records from the database and batch aggregator with streaming to write to FTPS
  B. Use streaming with an in-memory reputable store strategy for reading records from the database and batch aggregator with streaming to write to FTPS
  C. Use streaming with a file store repeatable strategy for reading records from the database and batch aggregator with an optimal size
  D. Use streaming with a file store repeatable strategy reading records from the database and batch aggregator without any required configuration
  A. Use streaming with a file storage repeatable strategy for reading records from the database and batch aggregator with streaming to write to FTPS

  ---

  Explanation/Reference:

  For handling large datasets in a Mule application, streaming is an effective strategy. Streaming allows the application to process large amounts of data in chunks, reducing memory usage and improving performance. Using a file storage repeatable strategy for reading records from the database ensures that the data is read in manageable chunks and stored temporarily in files, which can be re-read if necessary, enhancing reliability. The batch aggregator with streaming to write to an FTPS server ensures that data is written in chunks, aligning with the processing capabilities of the application running in CloudHub with 0.2 vCore and 8 GB storage. This configuration optimizes performance by balancing the load and managing the dataset size effectively, ensuring that the high rate of records can be processed and written to the FTPS server without overwhelming the system. References: MuleSoft Documentation on Streaming MuleSoft Documentation on Batch Processing

• Question 195:

  The implementation of a Process API must change. What is a valid approach that minimizes the impact of this change on API clients?

  A. Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
  B. Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
  C. Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
  D. Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 -Moved Permanently to inform API clients they should be calling the new API implementation
  A. Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged

  ---

  Explanation/Reference:

  *

  Option B shouldn't be used unless extremely needed, if RAML is changed, client needs to accommodate changes. Question is about minimizing impact on Client. So this is not a valid choice.

  *

  Option C isn't valid as Business can't stop for consumers acknowledgment.

  *

  Option D again needs Client to accommodate changes and isn't viable option.

  *

  Best choice is A where RAML definition isn't changed and underlined functionality is changed without any dependency on client and without impacting client.

• Question 196:

  In Anypoint Platform, a company wants to configure multiple identity providers (IdPs) for multiple lines of business (LOBs). Multiple business groups, teams, and environments have been defined for these LOBs. What Anypoint Platform feature can use multiple IdPs across the company's business groups, teams, and environments?

  A. MuleSoft-hosted (CloudHub) dedicated load balancers
  B. Client (application) management
  C. Virtual private clouds
  D. Permissions
  A. MuleSoft-hosted (CloudHub) dedicated load balancers

  ---

  Explanation/Reference:

  To use a dedicated load balancer in your environment, you must first create an Anypoint VPC. Because you can associate multiple environments with the same Anypoint VPC, you can use the same dedicated load balancer for your different environments.

  Reference: https://docs.mulesoft.com/runtime-manager/cloudhub-dedicated-load-balancer

• Question 197:

  What is an advantage that Anypoint Platform offers by providing universal API management and Integration-Platform-as-a-Service (iPaaS) capabilities in a unified platform?

  A. Ability to use a single iPaaS to manage and integrate all API gateways
  B. Ability to use a single connector to manage and integrate all APis
  C. Ability to use a single control plane for both full-lifecycle AP] management and integration
  D. Ability to use a single iPaaS to manage all API developer portals
  C. Ability to use a single control plane for both full-lifecycle AP] management and integration

  ---

  Explanation/Reference:

  Anypoint Platform offers universal API management and Integration-Platform-as-a-Service (iPaaS) capabilities in a unified platform, meaning that it provides a single control plane to manage both full-lifecycle API management and integration. This allows organizations to easily manage their APIs and integrations, as well as deploy APIs and integrations quickly and efficiently. According to the MuleSoft Certified Integration Architect -Level 1 Course Book, "Anypoint Platform provides a unified platform for managing, deploying, and monitoring both API and integration solutions, allowing organizations to quickly and easily build and manage their APIs and integrations."

• Question 198:

  An organization is in the process of building automated deployments using a CI/CD process. As a part of automated deployments, it wants to apply policies to API Instances.

  What tool can the organization use to promote and deploy API Manager policies?

  A. Anypoint CLI
  B. MUnit Maven plugin
  C. Mule Maven plugin
  D. Runtime Manager agent
  A. Anypoint CLI

  ---

  Explanation/Reference:

  To automate the promotion and deployment of API Manager policies as part of a CI/CD process, an organization can use the Anypoint CLI (Command Line Interface). The Anypoint CLI provides a set of commands to interact with various

  components of the Anypoint Platform, including API Manager.

  Using the Anypoint CLI, you can:

  Apply policies to API instances.

  Promote APIs and their associated policies across different environments. Script these actions as part of the CI/CD pipeline to ensure consistency and automation in managing API policies. Other tools like the MUnit Maven plugin, Mule

  Maven plugin, and Runtime Manager agent do not provide direct capabilities to manage API Manager policies.

  References:

  MuleSoft Anypoint CLI Documentation

  Automating API Management with Anypoint CLI

• Question 199:

  49 of A popular retailer is designing a public API for its numerous business partners. Each business partner will invoke the API at the URL 58. https://api.acme.com/partnefs/vl. The API implementation is estimated to require deployment to 5 CloudHub workers.

  The retailer has obtained a public X.509 certificate for the name apl.acme.com, signed by a reputable CA, to be used as the server certificate.

  Where and how should the X.509 certificate and Mule applications be used to configure load balancing among the 5 CloudHub workers, and what DNS entries should be configured in order for the retailer to support its numerous business partners?

  A. Add the X.509 certificate to the Mule application's deployable archive, then configure a CloudHub Dedicated Load Balancer (DLB) for each of the Mule application's CloudHub workers Create a CNAME for api.acme.com pointing to the DLB's A record
  B. Add the X.509 certificate to the CloudHub Shared Load Balancer (SLB), not to the Mule application Create a CNAME for api.acme.com pointing to the SLB's A record
  C. Add the X.509 certificate to a CloudHub Dedicated Load Balancer (DLB), not to the Mule application Create a CNAME for api.acme.com pointing to the DLB's A record
  D. Add the x.509 certificate to the Mule application's deployable archive, then configure the CloudHub Shared Load Balancer (SLB) for each of the Mule application's CloudHub workers Create a CNAME for api.acme.com pointing to the SLB's A record
  C. Add the X.509 certificate to a CloudHub Dedicated Load Balancer (DLB), not to the Mule application Create a CNAME for api.acme.com pointing to the DLB's A record

  ---

  Explanation/Reference:

  *

  An X.509 certificate is a vital safeguard against malicious network impersonators. Without x.509 server authentication, man-in-the-middle attacks can be initiated by malicious access points, compromised routers, etc.

  *

  X.509 is most used for SSL/TLS connections to ensure that the client (e.g., a web browser) is not fooled by a malicious impersonator pretending to be a known, trustworthy website.

  *

  Coming to the question , we can not use SLB here as SLB does not allow to define vanity domain names. * Hence we need to use DLB and add certificate in there Hence correct answer is Add the X 509 certificate to the cloudhub Dedicated Load Balancer (DLB), not the Mule application. Create the CNAME for api.acme.com pointing to the DLB's record

• Question 200:

  Refer to the exhibit.

  

  An organization uses a 2-node Mute runtime cluster to host one stateless API implementation. The API is accessed over HTTPS through a load balancer that uses round-robin for load distribution.

  Two additional nodes have been added to the cluster and the load balancer has been configured to recognize the new nodes with no other change to the load balancer.

  What average performance change is guaranteed to happen, assuming all cluster nodes are fully operational?

  A. 50% reduction in the response time of the API
  B. 100% increase in the throughput of the API
  C. 50% reduction In the JVM heap memory consumed by each node
  D. 50% reduction In the number of requests being received by each node
  D. 50% reduction In the number of requests being received by each node