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

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

• Question 201:

  According to the National Institute of Standards and Technology (NIST), which cloud computing deployment model describes a composition of two or more distinct clouds that support data and application portability?

  A. Private cloud
  B. Hybrid cloud 4
  C. Public cloud
  D. Community cloud
  B. Hybrid cloud 4

  ---

  Explanation/Reference:

  According to the National Institute of Standards and Technology (NIST), a hybrid cloud is a cloud computing deployment model that describes a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability. Hybrid clouds allow organizations to leverage the advantages of multiple cloud environments, such as combining the scalability and cost-efficiency of public clouds with the security and control of private clouds. This model facilitates flexibility and dynamic scalability, supporting diverse workloads and business needs while ensuring that sensitive data and applications can remain in a controlled private environment. References: NIST Definition of Cloud Computing Hybrid Cloud Overview and Benefits

• Question 202:

  An organization plans to migrate all its Mule applications to Runtime Fabric (RTF). Currently, all Mule applications have been deployed to CloudHub using automated CI/CD scripts.

  What steps should be taken to properly migrate the applications from CloudHub to RTF, while keeping the same automated CI/CD deployment strategy?

  A. A runtimefabric dependency should be added as a mule-plugin to the pom.xml file in all the Mule applications.
  B. runtimeFabric command-line parameter should be added to the CI/CD deployment scripts.
  C. A runtimefFabricDeployment profile should be added to Mule configuration properties YAML files in all the Mule applications. CI/CD scripts must be modified to use the new configuration properties.
  D. runtimefabricDeployment profile should be added to the pom.xml file in all the Mule applications. CI/CD scripts must be modified to use the new RTF profile.
  E. The pom.xml and Mule configuration YAML files can remain unchanged in each Mule application. A --runtimeFabric command-line parameter should be added to the CI/CD deployment scripts
  D. runtimefabricDeployment profile should be added to the pom.xml file in all the Mule applications. CI/CD scripts must be modified to use the new RTF profile.

  ---

  Explanation/Reference:

  To migrate Mule applications from CloudHub to Runtime Fabric (RTF) while maintaining the same automated CI/CD deployment strategy, follow these steps:

  Add runtimefabricDeployment Profile: Add a runtimefabricDeployment profile to the pom.xml file in all Mule applications. This profile will include the necessary configurations specific to RTF deployments. Modify CI/CD Scripts: Update the CI/

  CD deployment scripts to use the new runtimefabricDeployment profile. This modification ensures that the deployment process will correctly reference the RTF-specific configurations when deploying applications.

  Keep Configuration Files Unchanged: There is no need to change the pom.xml and Mule configuration YAML files other than adding the runtimefabricDeployment profile. This maintains consistency and reduces the risk of errors during the

  migration.

  This approach ensures a smooth transition to RTF while leveraging existing CI/CD scripts with minimal changes, maintaining the automated deployment strategy.

  References:

  MuleSoft Documentation on Runtime Fabric Deployment

  Best Practices for CI/CD with MuleSoft

• Question 203:

  What Anypoint Connectors support transactions?

  A. Database, JMS, VM
  B. Database, 3MS, HTTP
  C. Database, JMS, VM, SFTP
  D. Database, VM, File
  A. Database, JMS, VM

  ---

  Explanation/Reference:

  Below Anypoint Connectors support transactions JMS ?Publish ?Consume VM ?Publish ?Consume Database ?All operations

• Question 204:

  An organization is building a test suite for their applications using m-unit. The integration architect has recommended using test recorder in studio to record the processing flows and then configure unit tests based on the capture events

  What are the two considerations that must be kept in mind while using test recorder

  (Choose two answers)

  A. Tests for flows cannot be created with Mule errors raised inside the flow or already existing in the incoming event
  B. Recorder supports smoking a message before or inside a ForEach processor
  C. The recorder support loops where the structure of the data been tested changes inside the iteration
  D. A recorded flow execution ends successfully but the result does not reach its destination because the application is killed
  E. Mocking values resulting from parallel processes are possible and will not affect the execution of the processes that follow in the test
  A. Tests for flows cannot be created with Mule errors raised inside the flow or already existing in the incoming event
  D. A recorded flow execution ends successfully but the result does not reach its destination because the application is killed

  ---

  Explanation/Reference:

  When using MUnit's test recorder in Anypoint Studio to create unit tests, consider the following points:

  A. Tests for flows cannot be created with Mule errors raised inside the flow or already existing in the incoming event:

  The test recorder cannot record flows if Mule errors are raised during the flow execution or if the incoming event already contains errors. This limitation requires users to handle or clear errors before recording the flow to ensure accurate test

  creation.

  D. A recorded flow execution ends successfully but the result does not reach its destination because the application is killed:

  If the application is killed before the recorded flow execution completes, the recorder captures the flow up to the point of termination. However, the final result may not be reached or recorded. This scenario should be avoided to ensure

  complete and reliable test recordings.

  These considerations help ensure the accuracy and reliability of tests created using the test recorder.

  References:

  MUnit Documentation: https://docs.mulesoft.com/munit/2.2/

  MUnit Test Recorder: https://blogs.mulesoft.com/dev/mule-dev/using-the-munit-test-recorder/

• Question 205:

  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. CloudHub VM queues
  B. Anypoint MQ
  C. Anypoint Exchange
  D. CloudHub Shared Load Balancer
  B. Anypoint MQ

  ---

  Explanation/Reference:

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

  Reference: https://docs.mulesoft.com/mq/

• Question 206:

  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. Controlling the business group within Anypoint Platform to which the user belongs
  B. Assigning Anypoint Platform permissions to a role
  C. Assigning Anypoint Platform role(s) to a user
  D. Removing a user's access to Anypoint Platform when they no longer work for the organization
  B. Assigning Anypoint Platform permissions to a role

  ---

  Explanation/Reference:

  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

• Question 207:

  An auto mobile company want to share inventory updates with dealers Dl and D2 asynchronously and concurrently via queues Q1 and Q2. Dealer Dl must consume the message from the queue Q1 and dealer D2 to must consume a message from the queue Q2.

  Dealer D1 has implemented a retry mechanism to reprocess the transaction in case of any errors while processing the inventers updates. Dealer D2 has not implemented any retry mechanism.

  How should the dealers acknowledge the message to avoid message loss and minimize impact on the current implementation?

  A. Dealer D1 must use auto acknowledgement and dealer D2 can use manual acknowledgement and acknowledge the message after successful processing
  B. Dealer D1 can use auto acknowledgement and dealer D2 can use IMMEDIATE acknowledgement and acknowledge the message of successful processing
  C. Dealer D1 and dealer D2 must use AUTO acknowledgement and acknowledge the message after successful processing
  D. Dealer D1 can use AUTO acknowledgement and dealer D2 must use manual acknowledgement and acknowledge the message after successful processing
  D. Dealer D1 can use AUTO acknowledgement and dealer D2 must use manual acknowledgement and acknowledge the message after successful processing

  ---

  Explanation/Reference:

  Dealer D1 -AUTO Acknowledgment:

  Dealer D2 -Manual Acknowledgment:

  Ensuring Message Delivery:

  References:

  MuleSoft Documentation on JMS Acknowledgment

  Best practices for Reliable Messaging

• Question 208:

  What are two reasons why a typical MuleSoft customer favors a MuleSoft-hosted Anypoint Platform runtime plane over a customer-hosted runtime for its Mule application deployments? (Choose two.)

  A. Reduced application latency
  B. Increased application isolation
  C. Reduced time-to-market for the first application
  D. Increased application throughput
  E. Reduced IT operations effort
  C. Reduced time-to-market for the first application
  E. Reduced IT operations effort

  ---

  Explanation/Reference:

  MuleSoft customers often favor a MuleSoft-hosted Anypoint Platform runtime plane over a customer-hosted runtime for the following reasons:

  Reduced time-to-market for the first application (C): Using a MuleSoft-hosted runtime plane accelerates the deployment process because MuleSoft manages the infrastructure, allowing customers to focus on developing and deploying their

  applications quickly. This leads to faster time-to-market for the initial application and subsequent updates.

  Reduced IT operations effort (E): By leveraging a MuleSoft-hosted environment, customers offload the operational responsibilities, such as infrastructure maintenance, updates, and scalability management, to MuleSoft. This reduces the IT

  operations workload and allows internal teams to focus on more strategic initiatives.

  In contrast, other options like reduced application latency and increased application throughput are not directly influenced by whether the runtime plane is MuleSoft-hosted or customer-hosted.

  References:

  MuleSoft Anypoint Platform Documentation

  MuleSoft Hosted vs. Customer Hosted Deployment Guides

• Question 209:

  A new upstream API Is being designed to offer an SLA of 500 ms median and 800 ms maximum (99th percentile) response time. The corresponding API implementation needs to sequentially invoke 3 downstream APIs of very similar complexity. The first of these downstream APIs offers the following SLA for its response time: median: 100 ms, 80th percentile: 500 ms, 95th percentile: 1000 ms. If possible, how can a timeout be set in the upstream API for the invocation of the first downstream API to meet the new upstream API's desired SLA?

  A. Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete
  B. Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds
  C. Set a timeout of 50 ms; this times out more invocations of that API but gives additional room for retries
  D. No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API
  A. Set a timeout of 100 ms; that leaves 400 ms for the other two downstream APIs to complete
  B. Do not set a timeout; the Invocation of this API Is mandatory and so we must wait until it responds
  D. No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

  ---

  * Now consider, if API times out in first API and can't fetch customer number, in this case, it's useless to call API 2 and 3 and that is why question mentions specifically that all APIs need to be executed sequentially. 3) Set a timeout of 50 ms --> Again not possible due to the same reason as above Hence correct answer is No timeout is possible to meet the upstream API's desired SLA; a different SLA must be negotiated with the first downstream API or invoke an alternative API

• Question 210:

  What is required before an API implemented using the components of Anypoint Platform can be managed and governed (by applying API policies) on Anypoint Platform?

  A. The API must be published to Anypoint Exchange and a corresponding API instance ID must be obtained from API Manager to be used in the API implementation
  B. The API implementation source code must be committed to a source control management system (such as GitHub)
  C. A RAML definition of the API must be created in API designer so it can then be published to Anypoint Exchange
  D. The API must be shared with the potential developers through an API portal so API consumers can interact with the API
  A. The API must be published to Anypoint Exchange and a corresponding API instance ID must be obtained from API Manager to be used in the API implementation

  ---

  Explanation/Reference:

  Context of the question is about managing and governing mule applications deployed on Anypoint platform.

  Anypoint API Manager (API Manager) is a component of Anypoint Platform that enables you to manage, govern, and secure APIs. It leverages the runtime capabilities of API Gateway and Anypoint Service Mesh, both of which enforce

  policies, collect and track analytics data, manage proxies, provide encryption and authentication, and manage applications.

  Mule Ref Doc : https://docs.mulesoft.com/api-manager/2.x/getting-started-proxy Reference: https://docs.mulesoft.com/api-manager/2.x/api-auto-discovery-new-concept