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

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

• Question 91:

  Customer has deployed mule applications to different customer hosted mule run times.

  Mule applications are managed from Anypoint platform.

  What needs to be configured to monitor these Mule applications from Anypoint monitoring and what sends monitoring data to Anypoint monitoring?

  A. Enable monitoring of individual applications from runtime manager application settings Runtime manager agent sends monitoring data from the mule applications to Anypoint monitoring
  B. Install runtime manager agent on each mule runtime Runtime manager agent since monitoring data from the mule applications to Anypoint monitoring
  C. Anypoint monitoring agent on each mule runtime Anypoint monitoring agent sends monitoring data from the mule applications to Anypoint monitoring
  D. By default, Anypoint monitoring agent will be installed on each Mule run time Anypoint Monitoring agent automatically sends monitoring data from the Mule applications to Anypoint monitoring
  A. Enable monitoring of individual applications from runtime manager application settings Runtime manager agent sends monitoring data from the mule applications to Anypoint monitoring

  ---

  Explanation/Reference:

  To monitor Mule applications deployed on customer-hosted Mule runtimes from Anypoint Platform, you need to enable monitoring for each application within the Runtime Manager's application settings. This step ensures that the Runtime Manager Agent, which is already part of the Mule runtime, will collect and send monitoring data to Anypoint Monitoring. The Runtime Manager Agent acts as the intermediary, collecting metrics and operational data from the Mule applications and transmitting this data to Anypoint Monitoring for analysis and visualization. This setup provides real-time insights and allows for effective monitoring and management of Mule applications. References: MuleSoft Documentation on Anypoint Monitoring

• Question 92:

  Which component of Anypoint platform belongs to the platform control plane?

  A. Runtime Fabric
  B. Runtime Replica
  C. Anypoint Connectors
  D. API Manager
  D. API Manager

  ---

  Explanation/Reference:

  API Manager is a component of the Anypoint Platform's control plane. The control plane in Anypoint Platform is responsible for managing, securing, and monitoring APIs and integrations. API Manager specifically provides tools for API governance, including policy enforcement, analytics, security, and lifecycle management. It allows organizations to manage APIs centrally, ensuring they adhere to compliance and security standards while providing insights into API usage and performance. References: Anypoint Platform Control Plane Managing APIs with API Manager

• Question 93:

  A banking company is developing a new set of APIs for its online business. One of the critical API's is a master lookup API which is a system API. This master lookup API uses persistent object store. This API will be used by all other APIs to provide master lookup data.

  

  Master lookup API is deployed on two cloudhub workers of 0.1 vCore each because there is a lot of master data to be cached. Master lookup data is stored as a key value pair. The cache gets refreshed if they key is not found in the cache.

  Doing performance testing it was observed that the Master lookup API has a higher response time due to database queries execution to fetch the master lookup data.

  Due to this performance issue, go-live of the online business is on hold which could cause potential financial loss to Bank.

  As an integration architect, which of the below option you would suggest to resolve performance issue?

  A. Implement HTTP caching policy for all GET endpoints for the master lookup API and implement locking to synchronize access to object store
  B. Upgrade vCore size from 0.1 vCore to 0,2 vCore
  C. Implement HTTP caching policy for all GET endpoints for master lookup API
  D. Add an additional Cloudhub worker to provide additional capacity
  A. Implement HTTP caching policy for all GET endpoints for the master lookup API and implement locking to synchronize access to object store

  ---

  Explanation/Reference:

  A. Implement HTTP caching policy for all GET endpoints for the master lookup API and implement locking to synchronize access to object store Comprehensive Detailed Step by Step ExplanationTo resolve the performance issue observed

  during the performance testing of the Master lookup API, the best approach involves caching and synchronization:

  HTTP Caching Policy:

  Object Store Locking:

  By implementing these two strategies, the response time of the Master lookup API will be significantly improved, and the performance issue will be resolved.

  References:

  MuleSoft HTTP Caching Policy

  MuleSoft Object Store Connector

• Question 94:

  A system API EmployeeSAPI is used to fetch employee's data from an underlying SQL database.

  The architect must design a caching strategy to query the database only when there is an update to the employees stable or else return a cached response in order to minimize the number of redundant transactions being handled by the database.

  What must the architect do to achieve the caching objective?

  A. Use an On Table Row on employees table and call invalidate cache Use an object store caching strategy and expiration interval to empty
  B. Use a Scheduler with a fixed frequency every hour triggering an invalidate cache flow Use an object store caching strategy and expiration interval to empty
  C. Use a Scheduler with a fixed frequency every hour triggering an invalidate cache flow Use an object store caching strategy and set expiration interval to 1-hour
  D. Use an on table rule on employees table call invalidate cache and said new employees data to cache Use an object store caching strategy and set expiration interval to 1-hour
  A. Use an On Table Row on employees table and call invalidate cache Use an object store caching strategy and expiration interval to empty

  ---

  Explanation/Reference:

  To achieve efficient caching and reduce redundant database transactions, the following strategy can be implemented:

  On Table Row Listener: Implement an "On Table Row" trigger on the employees' table. This trigger will monitor changes (inserts, updates, deletes) in the employee records. Invalidate Cache: Upon detecting changes in the employees' table,

  the trigger will call a flow to invalidate the current cache. Object Store for Caching: Utilize MuleSoft's object store to cache the employee data. This store can hold the data for quick retrieval. Set Expiration Interval: Configure the expiration

  interval for the cached data to ensure it is cleared when necessary. For this scenario, since we are invalidating cache on actual data changes, setting the expiration interval to empty can be suitable.

  Return Cached Data: If there are no updates, the cached response is returned, reducing database load.

  References:

  MuleSoft Documentation on Object Store

  Caching Strategies

• Question 95:

  A Mule application name Pub uses a persistence object store. The Pub Mule application is deployed to Cloudhub and it configured to use Object Store v2.

  Another Mule application name sub is being developed to retrieve values from the Pub Mule application persistence object Store and will also be deployed to cloudhub. What is the most direct way for the Sub Mule application to retrieve values from the Pub Mule application persistence object store with the least latency?

  A. Use an object store connector configured to access the Pub Mule application persistence object store
  B. Use a VM connector configured to directly access the persistence queue of the Pub Mule application persistence object store.
  C. Use an Anypoint MQ connector configured to directly access the Pub Mule application persistence object store
  D. Use the Object store v2 REST API configured to access the Pub Mule application persistence object store.
  D. Use the Object store v2 REST API configured to access the Pub Mule application persistence object store.

  ---

  Explanation/Reference:

  *

  The Object Store V2 API enables API access to Anypoint Platform Object Store v2.

  *

  You can configure a Mule app to use the Object Store REST API to store and retrieve values from an object store in another Mule app. However, Object Store v2 is not designed for app-to-app communication. To share data between two

  Mule4 apps, use a queue in Anypoint MQ.

  *

  The Object Store v2 APIs enable you to use REST to perform the following:

  -Retrieve a list of object stores and keys associated with an application.

  -Store and retrieve key-value pairs in an object store.

  -Delete key-value pairs from an object store.

  -Retrieve Object Store usage statistics for your organization.

  -Object Store provides these APIs:

  Object Store API

  Object Store Stats API

  Reference: https://docs.mulesoft.com/object-store/osv2-apis

  Additional Info:

  When to use Object Store and when to use VM

• Question 96:

  An organization is creating a Mule application that will be deployed to CloudHub. The Mule application has a property named dbPassword that stores a database user's password. The organization's security standards indicate that the dbPassword property must be hidden from every Anypoint Platform user after the value is set in the Runtime Manager Properties tab.

  What configuration in the Mule application helps hide the dbPassword property value in Runtime Manager?

  A. Use secure::dbPassword as the property placeholder name and store the cleartext (unencrypted) value in a secure properties placeholder file
  B. Use secure::dbPassword as the property placeholder name and store the property encrypted value in a secure properties placeholder file
  C. Add the dbPassword property to the secureProperties section of the pom.xml file
  D. Add the dbPassword property to the secureProperties section of the mule-artifact.json file
  B. Use secure::dbPassword as the property placeholder name and store the property encrypted value in a secure properties placeholder file

  ---

  Explanation/Reference:

  Reference: https://docs.mulesoft.com/runtime-manager/secure-application-properties

• Question 97:

  What API policy would LEAST likely be applied to a Process API?

  A. Custom circuit breaker
  B. Client ID enforcement
  C. Rate limiting
  D. JSON threat protection
  D. JSON threat protection

  ---

  Explanation/Reference:

  Key to this question lies in the fact that Process API are not meant to be accessed directly by clients. Lets analyze options one by one. Client ID enforcement : This is applied at process API level generally to ensure that identity of API clients is always known and available for API-based analytics Rate Limiting : This policy is applied on Process Level API to secure API's against degradation of service that can happen in case load received is more than it can handle Custom circuit breaker : This is also quite useful feature on process level API's as it saves the API client the wasted time and effort of invoking a failing API. JSON threat protection : This policy is not required at Process API and rather implemented as Experience API's. This policy is used to safeguard application from malicious attacks by injecting malicious code in JSON object. As ideally Process API's are never called from external world , this policy is never used on Process API's Hence correct answer is JSON threat protection MuleSoft Documentation Reference : https://docs.mulesoft.com/api-manager/2.x/policy-mule3-json-threat

• Question 98:

  A project uses Jenkins to implement CI/CD process. It was observed that each Mule package contains some of the Jenkins files and folders for configurations of CI/CD jobs.

  As these files and folders are not part of the actual package, expectation is that these should not be part of deployed archive.

  Which file can be used to exclude these files and folders from the deployed archive?

  A. muleignore
  B. _unTrackMule
  C. mulelnclude
  D. _muleExclude
  A. muleignore

  ---

  Explanation/Reference:

  Requirement Analysis: Jenkins files and folders used for CI/CD configurations are not part of the actual Mule package and should be excluded from the deployed archive. Solution: MuleSoft provides the .muleignore file to specify files and

  directories that should be excluded from the packaged application.

  Implementation Steps:

  # .muleignore example /path/to/jenkins/file1 /path/to/jenkins/folder/* uk.co.certification.simulator.questionpool.PList@1a433440

  Advantages:

  References:

  MuleSoft Documentation on .muleignore

• Question 99:

  A Kubernetes controller automatically adds another pod replica to the resource pool in response to increased application load.

  Which scalability option is the controller implementing?

  A. Down
  B. Diagonal
  C. Vertical
  D. Horizontal
  D. Horizontal

  ---

  Explanation/Reference:

  The Kubernetes controller is implementing horizontal scalability by adding another pod replica in response to increased application load. Horizontal scaling involves adding more instances of a service or application to handle the increased load, as opposed to vertical scaling, which would involve adding more resources (CPU, RAM) to a single instance. Horizontal scaling is a key feature of cloud-native applications and is supported by Kubernetes to ensure high availability and performance. References: Kubernetes Horizontal Pod Autoscaling Understanding Horizontal vs. Vertical Scaling

• Question 100:

  What is true about the network connections when a Mule application uses a JMS connector to interact with a JMS provider (message broker)?

  A. To complete sending a JMS message, the JMS connector must establish a network connection with the JMS message recipient
  B. To receive messages into the Mule application, the JMS provider initiates a network connection to the JMS connector and pushes messages along this connection
  C. The JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider
  D. The AMQP protocol can be used by the JMS connector to portably establish connections to various types of JMS providers
  C. The JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider

  ---

  Explanation/Reference:

  *

  To send message or receive JMS (Java Message Service) message no separate network connection need to be established. So option A, C and D are ruled out.

  Correct Answer: The JMS connector supports both sending and receiving of JMS messages over the protocol determined by the JMS provider.

  *

  JMS Connector enables sending and receiving messages to queues and topics for any message service that implements the JMS specification.

  *

  JMS is a widely used API for message-oriented middleware.

  *

  It enables the communication between different components of a distributed application to be loosely coupled, reliable, and asynchronous. MuleSoft Doc Reference: https://docs.mulesoft.com/jms-connector/1.7/