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

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

• Question 121:

  An organization designing a hybrid, load balanced, single cluster production environment. Due to performance service level agreement goals, it is looking into running the Mule applications in an active-active multi node cluster configuration.

  What should be considered when running its Mule applications in this type of environment?

  A. All event sources, regardless of time , can be configured as the target source by the primary node in the cluster
  B. An external load balancer is required to distribute incoming requests throughout the cluster nodes
  C. A Mule application deployed to multiple nodes runs in an isolation from the other nodes in the cluster
  D. Although the cluster environment is fully installed configured and running, it will not process any requests until an outage condition is detected by the primary node in the cluster.
  B. An external load balancer is required to distribute incoming requests throughout the cluster nodes

  ---

  Explanation/Reference:

  In a hybrid, load-balanced, single cluster production environment running Mule applications in an active-active multi-node configuration, several considerations are critical for ensuring performance and reliability. The key consideration is the

  use of an external load balancer:

  Active-Active Multi-Node Cluster Configuration:

  External Load Balancer Requirement:

  Load Balancer Configuration:

  Mule Application Isolation:

  Handling Requests:

  Benefits:

  References:

  MuleSoft Documentation on Mule Clustering

  Best Practices for Load Balancing

• Question 122:

  A REST API is being designed to implement a Mule application.

  What standard interface definition language can be used to define REST APIs?

  A. Web Service Definition Language(WSDL)
  B. OpenAPI Specification (OAS)
  C. YAML
  D. AsyncAPI Specification
  B. OpenAPI Specification (OAS)

• Question 123:

  An API has been unit tested and is ready for integration testing. The API is governed by a Client ID Enforcement policy in all environments.

  What must the testing team do before they can start integration testing the API in the Staging environment?

  A. They must access the API portal and create an API notebook using the Client ID and Client Secret supplied by the API portal in the Staging environment
  B. They must request access to the API instance in the Staging environment and obtain a Client ID and Client Secret to be used for testing the API
  C. They must be assigned as an API version owner of the API in the Staging environment
  D. They must request access to the Staging environment and obtain the Client ID and Client Secret for that environment to be used for testing the API
  B. They must request access to the API instance in the Staging environment and obtain a Client ID and Client Secret to be used for testing the API

  ---

  Explanation/Reference:

  *

  It's mentioned that the API is governed by a Client ID Enforcement policy in all environments.

  *

  Client ID Enforcement policy allows only authorized applications to access the deployed API implementation.

  *

  Each authorized application is configured with credentials: client_id and client_secret.

  *

  At runtime, authorized applications provide the credentials with each request to the API implementation. MuleSoft Reference: https://docs.mulesoft.com/api-manager/2.x/policy-mule3-client-id-based-policies

• Question 124:

  What is an example of data confidentiality?

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

  ---

  Explanation/Reference:

  Data confidentiality involves protecting information from unauthorized access and disclosure. Encrypting a file containing personally identifiable information (PII) is a prime example of ensuring data confidentiality. Encryption transforms the

  data into a format that is unreadable without the appropriate decryption key, thereby safeguarding sensitive information such as PII from being accessed by unauthorized parties. This measure is essential for compliance with data protection

  regulations and maintaining the privacy and security of personal data.

  References:

  MuleSoft Security Best Practices Data Protection and Encryption Standards Documentation

• Question 125:

  An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields. The data is available partially in a database and partially in a 3rd-party CRM system. What APIs should be created to best fit these design requirements?

  

  A. A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changes.
  B. One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile app.
  C. Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system
  D. A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System.
  C. Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

  ---

  Explanation/Reference:

  Lets analyze the situation in regards to the different options available Option : A common Experience API but separate Process APIs Analysis : This solution will not work because having common experience layer will not help the purpose as mobile and web applications will have different set of requirements which cannot be fulfilled by single experience layer API Option : Common Process API Analysis : This solution will not work because creating a common process API will impose limitations in terms of flexibility to customize API;s as per the requirements of different applications. It is not a recommended approach. Option : Separate set of API's for both the applications Analysis : This goes against the principle of Anypoint API-led connectivity approach which promotes creating reusable assets. This solution may work but this is not efficient solution and creates duplicity of code. Hence the correct answer is: Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

  

  A screenshot of a computer

  Description automatically generated with low confidence Lets analyze the situation in regards to the different options available Option : A common Experience API but separate Process APIs Analysis : This solution will not work because having common experience layer will not help the purpose as mobile and web applications will have different set of requirements which cannot be fulfilled by single experience layer API Option : Common Process API Analysis : This solution will not work because creating a common process API will impose limitations in terms of flexibility to customize API;s as per the requirements of different applications. It is not a recommended approach. Option : Separate set of API's for both the applications Analysis : This goes against the principle of Anypoint API-led connectivity approach which promotes creating reusable assets. This solution may work but this is not efficient solution and creates duplicity of code. Hence the correct answer is: Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

  

• Question 126:

  According to MuleSoft, which system integration term describes the method, format, and protocol used for communication between two system?

  A. Component
  B. interaction
  C. Message
  D. Interface
  D. Interface

  ---

  Explanation/Reference:

  According to MuleSoft, the term "interface" describes the method, format, and protocol used for communication between two systems. An interface defines how systems interact, specifying the data formats (e.g., JSON, XML), protocols (e.g.,

  HTTP, FTP), and methods (e.g., GET, POST) that are used to exchange information. Properly designed interfaces ensure compatibility and seamless communication between integrated systems.

  References:

  MuleSoft Glossary of Integration Terms

  System Interfaces and APIs

• Question 127:

  Refer to the exhibit.

  

  A Mule application has an HTTP Listener that accepts HTTP DELETE requests. This Mule application Is deployed to three CloudHub workers under the control of the CloudHub Shared Load Balancer.

  A web client makes a sequence of requests to the Mule application's public URL.

  How is this sequence of web client requests distributed among the HTTP Listeners running in the three CloudHub workers?

  A. Each request is routed to the PRIMARY CloudHub worker in the PRIMARY Availability Zone (AZ)
  B. Each request is routed to ONE ARBiTRARY CloudHub worker in the PRIMARY Availability Zone (AZ)
  C. Each request Is routed to ONE ARBiTRARY CloudHub worker out of ALL three CloudHub workers
  D. Each request is routed (scattered) to ALL three CloudHub workers at the same time
  C. Each request Is routed to ONE ARBiTRARY CloudHub worker out of ALL three CloudHub workers

  ---

  Explanation/Reference:

  Correct behavior is Each request is routed to ONE ARBITRARY CloudHub worker out of ALL three CloudHub workers

• Question 128:

  Refer to the exhibit.

  

  A Mule 4 application has a parent flow that breaks up a JSON array payload into 200 separate items, then sends each item one at a time inside an Async scope to a VM queue.

  A second flow to process orders has a VM Listener on the same VM queue. The rest of this flow processes each received item by writing the item to a database.

  This Mule application is deployed to four CloudHub workers with persistent queues enabled.

  What message processing guarantees are provided by the VM queue and the CloudHub workers, and how are VM messages routed among the CloudHub workers for each invocation of the parent flow under normal operating conditions where all the CloudHub workers remain online?

  A. EACH item VM message is processed AT MOST ONCE by ONE CloudHub worker, with workers chosen in a deterministic round-robin fashion Each of the four CloudHub workers can be expected to process 1/4 of the Item VM messages (about 50 items)
  B. EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages
  C. ALL Item VM messages are processed AT LEAST ONCE by the SAME CloudHub worker where the parent flow was invoked This one CloudHub worker processes ALL 200 item VM messages
  D. ALL item VM messages are processed AT MOST ONCE by ONE ARBITRARY CloudHub worker This one CloudHub worker processes ALL 200 item VM messages
  B. EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker Each of the four CloudHub workers can be expected to process some item VM messages

  ---

  Explanation/Reference:

  Correct answer is EACH item VM message is processed AT LEAST ONCE by ONE ARBITRARY CloudHub worker. Each of the four CloudHub workers can be expected to process some item VM messages In Cloudhub, each persistent VM queue is listened on by every CloudHub worker -But each message is read and processed at least once by only one CloudHub worker and the duplicate processing is possible -If the CloudHub worker fails , the message can be read by another worker to prevent loss of messages and this can lead to duplicate processing -By default , every CloudHub worker's VM Listener receives different messages from VM Queue Referenece: https://dzone.com/articles/deploying-mulesoft-application-on-1-worker-vs-mult

• Question 129:

  Refer to the exhibit.

  An organization is designing a Mule application to receive data from one external business partner. The two companies currently have no shared IT infrastructure and do not want to establish one. Instead, all communication should be over the public internet (with no VPN).

  What Anypoint Connector can be used in the organization's Mule application to securely receive data from this external business partner?

  

  A. File connector
  B. VM connector
  C. SFTP connector
  D. Object Store connector
  C. SFTP connector

  ---

  Explanation/Reference:

  *

  Object Store and VM Store is used for sharing data inter or intra mule applications in same setup. Can't be used with external Business Partner

  *

  Also File connector will not be useful as the two companies currently have no shared IT infrastructure. It's specific for local use.

  *

  Correct answer is SFTP connector. The SFTP Connector implements a secure file transport channel so that your Mule application can exchange files with external resources. SFTP uses the SSH security protocol to transfer messages. You can implement the SFTP endpoint as an inbound endpoint with a one-way exchange pattern, or as an outbound endpoint configured for either a one-way or request-response exchange pattern.

• Question 130:

  Which role is primarily responsible for building API implementation as part of a typical MuleSoft integration project?

  A. API Developer
  B. API Designer
  C. Integration Architect
  D. Operations
  A. API Developer

  ---

  Explanation/Reference:

  In a typical MuleSoft integration project, the role primarily responsible for building API implementations is the API Developer. The API Developer focuses on writing the code that implements the logic, data transformations, and business processes defined in the API specifications. They use tools like Anypoint Studio to develop and test Mule applications, ensuring that the APIs function as required and integrate seamlessly with other systems and services. While the API Designer is responsible for defining the API specifications and the Integration Architect for designing the overall integration solution, the API Developer translates these designs into working software. The Operations team typically manages the deployment, monitoring, and maintenance of the APIs in production environments. References: MuleSoft Documentation on Roles and Responsibilities Anypoint Platform Development Best Practices