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

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

• Question 131:

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

  ---

  Explanation/Reference:

  When a batch job instance running on a runtime fabric environment with two cluster replicas encounters an unexpected failure, the following sequence of events occurs:

  Failure Detection: The runtime fabric environment detects the failure of the replica running the batch job.

  Replica Replacement: A new replica is provisioned to replace the failed one. Batch Job State Recovery: MuleSoft's batch processing mechanism ensures that the state of the batch job is periodically saved (checkpointing). This allows the new

  replica to resume processing from the last saved state.

  Resumption of Processing: The new replica takes over the batch job, continuing from where the previous one left off, thus processing the remaining 99,000 records without starting from scratch or causing duplicate processing.

  References:

  MuleSoft Documentation on Batch Processing

  Runtime Fabric Guide

• Question 132:

  A Mule application uses APIkit for SOAP to implement a SOAP web service. The Mule application has been deployed to a CloudHub worker in a testing environment.

  The integration testing team wants to use a SOAP client to perform Integration testing. To carry out the integration tests, the integration team must obtain the interface definition for the SOAP web service.

  What is the most idiomatic (used for its intended purpose) way for the integration testing team to obtain the interface definition for the deployed SOAP web service in order to perform integration testing with the SOAP client?

  A. Retrieve the OpenAPI Specification file(s) from API Manager
  B. Retrieve the WSDL file(s) from the deployed Mule application
  C. Retrieve the RAML file(s) from the deployed Mule application
  D. Retrieve the XML file(s) from Runtime Manager
  D. Retrieve the XML file(s) from Runtime Manager

  ---

  Explanation/Reference:

  Reference: https://docs.spring.io/spring-framework/docs/4.2.x/spring-framework-reference/html/integration-testing.html

• Question 133:

  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. Analytics
  B. Metrics
  C. Tracing
  D. Data mining
  C. Tracing

  ---

  Explanation/Reference:

  To track the entire lifecycle of each request across different microservices, the DevOps team should consider adopting tracing. Distributed tracing allows teams to follow a request as it travels through the various microservices, providing

  visibility into how long each part of the request lifecycle takes and where any bottlenecks or failures occur. Tools like Zipkin, Jaeger, and AWS X-Ray are commonly used for this purpose. Tracing complements metrics and logging by providing

  detailed insights into the interactions and dependencies between services.

  References:

  Distributed Tracing in Microservices

  What is Distributed Tracing?

• Question 134:

  Which type of communication is managed by a service mesh in a microservices architecture?

  A. Communication between microservices runtime administrators
  B. Communication between microservices developers
  C. Communication between microservices
  D. Communication between trading partner services
  C. Communication between microservices

  ---

  Explanation/Reference:

  In a microservices architecture, a service mesh manages the communication between microservices. This involves handling service discovery, load balancing, failure recovery, metrics, and monitoring. Service meshes also provide more complex operational requirements like A/B testing, canary releases, rate limiting, access control, and end-to-end authentication. By abstracting these functionalities away from individual microservices, a service mesh allows developers to focus on business logic while ensuring reliable and secure inter-service communication. References: Understanding Service Mesh Service Mesh for Microservices

• Question 135:

  Refer to the exhibit.

  

  An organization deploys multiple Mule applications to the same customer -hosted Mule runtime. Many of these Mule applications must expose an HTTPS endpoint on the same port using a server-side certificate that rotates often.

  What is the most effective way to package the HTTP Listener and package or store the server-side certificate when deploying these Mule applications, so the disruption caused by certificate rotation is minimized?

  A. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint Package the server-side certificate in ALL Mule APPLICATIONS that need to expose an HTTPS endpoint
  B. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION
  C. Package an HTTPS Listener configuration In all Mule APPLICATIONS that need to expose an HTTPS endpoint Package the server-side certificate in a NEW Mule DOMAIN project
  D. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing It from all Mule applications that need to expose an HTTPS endpoint. Package the server-side certificate in the SAME Mule DOMAIN project Go to Set
  B. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION

  ---

  Explanation/Reference:

  In this scenario, both A and C will work, but A is better as it does not require repackage to the domain project at all.

  Correct answer is Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the

  Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION.

  What is Mule Domain Project?

  *

  A Mule Domain Project is implemented to configure the resources that are shared among different projects. These resources can be used by all the projects associated with this domain. Mule applications can be associated with only one domain, but a domain can be associated with multiple projects. Shared resources allow multiple development teams to work in parallel using the same set of reusable connectors. Defining these connectors as shared resources at the domain level allows the team to: -Expose multiple services within the domain through the same port. -Share the connection to persistent storage. -Share services between apps through a well-defined interface. -Ensure consistency between apps upon any changes because the configuration is only set in one place.

  *

  Use domains Project to share the same host and port among multiple projects. You can declare the http connector within a domain project and associate the domain project with other projects. Doing this also allows to control thread settings, keystore configurations, time outs for all the requests made within multiple applications. You may think that one can also achieve this by duplicating the http connector configuration across all the applications. But, doing this may pose a nightmare if you have to make a change and redeploy all the applications.

  *

  If you use connector configuration in the domain and let all the applications use the new domain instead of a default domain, you will maintain only one copy of the http connector configuration. Any changes will require only the domain to the redeployed instead of all the applications. You can start using domains in only three steps: 1) Create a Mule Domain project 2) Create the global connector configurations which needs to be shared across the applications inside the Mule Domain project 3) Modify the value of domain in mule-deploy.properties file of the applications

  

  Use a certificate defined in already deployed Mule domain Configure the certificate in the domain so that the API proxy HTTPS Listener References: it, and then deploy the secure API proxy to the target Runtime Fabric, or on-premises target. (CloudHub is not supported with this approach because it does not support Mule domains.)

• Question 136:

  A retail company is implementing a MuleSoft API to get inventory details from two vendors by Invoking each vendor's online applications. Due to network issues, the invocations to the vendor applications are timing out intermittently, but the requests are successful after re-invoking each vendor application.

  What is the most performant way of implementing the API to invoke each vendor application and to retry invocations that generate timeout errors?

  A. Use a For-Each scope to invoke the two vendor applications in series, one after the other. Place the For-Each scope inside an Until-Successful scope to retry requests that raise timeout errors.
  B. Use a Choice scope to Invoke each vendor application on a separate route. Place the Choice scope inside an Until-Successful scope to retry requests that raise timeout errors.
  C. Use a Scatter-Gather scope to invoke each vendor application on a separate route. Use an Until-Successful scope in each route to retry requests that raise timeout errors.
  D. Use a Round-Robin scope to invoke each vendor application on a separate route. Use a Try-Catch scope in each route to retry requests that raise timeout errors.
  C. Use a Scatter-Gather scope to invoke each vendor application on a separate route. Use an Until-Successful scope in each route to retry requests that raise timeout errors.

  ---

  Explanation/Reference:

  To efficiently handle the invocation of vendor applications and retry requests that generate timeout errors, the most performant way is:

  Scatter-Gather Scope: Use a Scatter-Gather scope to invoke each vendor application in parallel. This approach allows the API to send requests to both vendors simultaneously, reducing overall processing time. Until-Successful Scope: Inside

  each route of the Scatter-Gather scope, use an Until-Successful scope to handle retries. The Until-Successful scope will retry the request in case of timeout errors until the request succeeds or the maximum retry limit is reached.

  This combination ensures that the API can handle intermittent network issues efficiently while minimizing redundant transactions and maximizing performance.

  References:

  MuleSoft Documentation on Scatter-Gather Scope

  MuleSoft Documentation on Until-Successful Scope and Error Handling

• Question 137:

  Refer to the exhibit.

  

  A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all API implementations are Mule applications executing in a customer -hosted Mule runtime.

  End-to-end correlation of all HTTP requests and responses belonging to each individual checkout Instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance.

  What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?

  

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  B. Option B

  ---

  Explanation/Reference:

  Correct answer is "The web store backend generates a new correlation ID value at the start of checkout and sets it on the XORRELATION-ID HTTP request header in each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID" : By design, Correlation Ids cannot be changed within a flow in Mule 4 applications and can be set only at source. This ID is part of the Event Context and is generated as soon as the message is received by the application. When a HTTP Request is received, the request is inspected for "X-Correlation-Id" header. If "X-Correlation-Id" header is present, HTTP connector uses this as the Correlation Id. If "X-Correlation-Id" header is NOT present, a Correlation Id is randomly generated. For Incoming HTTP Requests: In order to set a custom Correlation Id, the client invoking the HTTP request must set "X-Correlation-Id" header. This will ensure that the Mule Flow uses this Correlation Id. For Outgoing HTTP Requests: You can also propagate the existing Correlation Id to downstream APIs. By default, all outgoing HTTP Requests send "X-Correlation-Id" header. However, you can choose to set a different value to "X-Correlation-Id" header or set "Send Correlation Id" to NEVER. Mulesoft Reference: https://help.mulesoft.com/s/article/How-to-Set-CustomCorrelation-Id-for-Flows-with-HTTP-Endpoint-in-Mule-4

  

• Question 138:

  A company is using Mulesoft to develop API's and deploy them to Cloudhub and on premises targets. Recently it has decided to enable Runtime Fabric deployment option as well and infrastructure is set up for this option.

  What can be used to deploy Runtime Fabric?

  A. AnypointCLI
  B. Anypoint platform REST API's
  C. Directly uploading ajar file from the Runtime manager
  D. Mule maven plug-in
  A. AnypointCLI

  ---

  Explanation/Reference:

  When deploying to Runtime Fabric, there are several tools available within the Anypoint Platform ecosystem that facilitate the deployment process. These include: AnypointCLI: This command-line interface tool provides comprehensive capabilities for deploying applications to Runtime Fabric. Using AnypointCLI, you can script and automate deployments, which is useful for integrating into CI/CD pipelines. Anypoint Platform REST APIs: These APIs allow for programmatic deployment and management of applications on Runtime Fabric. They provide flexibility for integrating deployment processes with other systems and tools. Mule Maven Plugin: This plugin can be used within a Maven project to package and deploy Mule applications to Runtime Fabric as part of a build process. However, directly uploading a JAR file from the Runtime Manager is not a supported method for deploying to Runtime Fabric. References: Anypoint CLI Documentation Mule Maven Plugin Documentation

• Question 139:

  As a part of design , Mule application is required call the Google Maps API to perform a distance computation. The application is deployed to cloudhub.

  At the minimum what should be configured in the TLS context of the HTTP request configuration to meet these requirements?

  A. The configuration is built-in and nothing extra is required for the TLS context
  B. Request a private key from Google and create a PKCS12 file with it and add it in keyStore as a part of TLS context
  C. Download the Google public certificate from a browser, generate JKS file from it and add it in key store as a part of TLS context
  D. Download the Google public certificate from a browser, generate a JKS file from it and add it in Truststore as part of the TLS context
  D. Download the Google public certificate from a browser, generate a JKS file from it and add it in Truststore as part of the TLS context

  ---

  Explanation/Reference:

  When configuring the TLS context for an HTTP request to the Google Maps API, the primary goal is to ensure that the Mule application can establish a secure connection.

  Here's a detailed explanation of the necessary steps:

  Download Google Public Certificate:

  Generate JKS File from Certificate:

  keytool -importcert -file google.cer -keystore truststore.jks -alias google Add JKS File to Truststore:

  Configure HTTP Request Connector:

  By completing these steps, your

  Mule application will trust the Google Maps API server's certificate, allowing for secure communication.

  References:

  MuleSoft Documentation: Configuring TLS

  Google Maps API Documentation

• Question 140:

  Which Salesforce API is invoked to deploy, retrieve, create, update, or delete customization information, such as custom object definitions using Mule Salesforce Connectors in a Mule application?

  A. sObject Platform Action API
  B. User Interface API
  C. Metadata API
  D. Process Rules API
  C. Metadata API

  ---

  Explanation/Reference:

  The Salesforce API used to deploy, retrieve, create, update, or delete customization information, such as custom object definitions, using Mule Salesforce Connectors in a Mule application, is the Metadata API. The Metadata API enables programmatic access to the metadata of Salesforce organizations, allowing developers to manage customizations and configurations programmatically. Using the Metadata API, Mule applications can automate the deployment and management of Salesforce customizations, facilitating continuous integration and deployment processes within Salesforce environments. References: MuleSoft Documentation on Salesforce Connectors Salesforce Metadata API Developer Guide