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

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

• Question 111:

  An organization uses Mule runtimes which are managed by Anypoint Platform -Private Cloud Edition. What MuleSoft component is responsible for feeding analytics data to non-MuleSoft analytics platforms?

  A. Anypoint Exchange
  B. The Mule runtimes
  C. Anypoint API Manager
  D. Anypoint Runtime Manager
  D. Anypoint Runtime Manager

  ---

  Explanation/Reference:

  Correct answer is Anypoint Runtime Manager MuleSoft Anypoint Runtime Manager (ARM) provides connectivity to Mule Runtime engines deployed across your organization to provide centralized management, monitoring and analytics reporting. However, most enterprise customers find it necessary for these on-premises runtimes to integrate with their existing non MuleSoft analytics / monitoring systems such as Splunk and ELK to support a single pane of glass view across the infrastructure.

  * You can configure the Runtime Manager agent to export data to external analytics tools. Using either the Runtime Manager cloud console or Anypoint Platform Private Cloud Edition, you can:

  --> Send Mule event notifications, including flow executions and exceptions, to Splunk or ELK.

  --> Send API Analytics to Splunk or ELK. Sending data to third-party tools is not supported for applications deployed on CloudHub.

  You can use the CloudHub custom log appender to integrate with your logging system. Reference: https://docs.mulesoft.com/runtime-manager/ https://docs.mulesoft.com/release-notes/runtime-manager-agent/runtime-manager-agentrelease- notes

  

  Additional Info:

  It can be achieved in 3 steps:

  1) register an agent to a runtime manager,

  2) configure a gateway to enable API analytics to be sent to non MuleSoft analytics platform (Splunk for ex.) ?as highlighted in the following diagram and

  3) setup dashboards.

  

• Question 112:

  An airline is architecting an API connectivity project to integrate its flight data into an online aggregation website. The interface must allow for secure communication high-performance and asynchronous message exchange.

  What are suitable interface technologies for this integration assuming that Mulesoft fully supports these technologies and that Anypoint connectors exist for these interfaces?

  A. AsyncAPI over HTTPS AMQP with RabbitMQ JSON/REST over HTTPS
  B. XML over ActiveMQ XML over SFTP XML/REST over HTTPS
  C. CSV over FTP YAM L over TLS JSON over HTTPS
  D. SOAP over HTTPS HOP over TLS gRPC over HTTPS
  A. AsyncAPI over HTTPS AMQP with RabbitMQ JSON/REST over HTTPS

  ---

  Explanation/Reference:

  For integrating flight data into an online aggregation website with secure, high-performance, and asynchronous message exchange, the most suitable interface technologies supported by MuleSoft are:

  AsyncAPI over HTTPS: AsyncAPI is a specification for asynchronous APIs, which is ideal for high-performance, event-driven communication. Using HTTPS ensures secure communication. AMQP with RabbitMQ: AMQP (Advanced Message

  Queuing Protocol) is a protocol for message-oriented middleware. RabbitMQ is a popular message broker that supports AMQP, allowing for reliable and asynchronous message exchange. JSON/REST over HTTPS: JSON is a lightweight

  data-interchange format, and REST (Representational State Transfer) is an architectural style for designing networked applications. Using HTTPS ensures secure communication.

  Implementation Steps:

  Define the AsyncAPI specification for the flight data events and set up the infrastructure to handle these events over HTTPS.

  Set up RabbitMQ and configure AMQP for message queuing. Ensure that your MuleSoft application is capable of consuming and producing messages using the RabbitMQ connector.

  Implement RESTful APIs using JSON over HTTPS to expose the flight data securely.

  These technologies collectively ensure secure, asynchronous, and high-performance integration.

  References:

  MuleSoft Documentation: AsyncAPI MuleSoft Documentation: RabbitMQ Connector MuleSoft Documentation: JSON and REST APIs

• Question 113:

  An insurance company has an existing API which is currently used by customers. API is deployed to customer hosted Mule runtime cluster. The load balancer that is used to access any APIs on the mule cluster is only configured to point to applications hosted on the server at port 443.

  Mule application team of a company attempted to deploy a second API using port 443 but the application will not start and checking logs shows an error indicating the address is already in use.

  Which steps must the organization take to resolve this error and allow customers to access both the API's?

  A. Change the base path of the HTTP listener configuration in the second API to a different one from the first API
  B. Set HTTP listener configuration in both API's to allow for connections from multiple ports
  C. Move the HTTP listener configurations from the API's and package them in a mule domain project using port 443
  D. Set the HTTP listener of the second API to use different port than the one used in the first API
  C. Move the HTTP listener configurations from the API's and package them in a mule domain project using port 443

  ---

  Explanation/Reference:

  When multiple Mule applications need to listen on the same port (e.g., port 443), configuring them individually will cause a conflict because only one application can bind to a specific port on a server at a time. To resolve this, you can use a

  Mule domain project, which allows multiple Mule applications to share configurations, including HTTP listeners. Here's how you can do it:

  Create a Mule Domain Project:

  Configure the Shared HTTP Listener:

  Reference the Shared HTTP Listener in Mule Applications:

  Deploy the Domain Project and

  Applications:

  By using a domain project to centralize the HTTP listener configuration, you ensure that both APIs can listen on port 443 without conflicts, allowing customers to access both APIs through the same port.

  References:

  MuleSoft Documentation: Domain Projects

  MuleSoft Documentation: HTTP Listener Configuration

• Question 114:

  What requires configuration of both a key store and a trust store for an HTTP Listener?

  A. Support for TLS mutual (two-way) authentication with HTTP clients
  B. Encryption of requests to both subdomains and API resource endpoints fhttPs://aDi.customer.com/ and https://customer.com/api)
  C. Encryption of both HTTP request and HTTP response bodies for all HTTP clients
  D. Encryption of both HTTP request header and HTTP request body for all HTTP clients
  A. Support for TLS mutual (two-way) authentication with HTTP clients

  ---

  Explanation/Reference:

  1 way SSL : The server presents its certificate to the client and the client adds it to its list of trusted certificate. And so, the client can talk to the server. 2-way SSL: The same principle but both ways. i.e. both the client and the server has to establish trust between themselves using a trusted certificate. In this way of a digital handshake, the server needs to present a certificate to authenticate itself to client and client has to present its certificate to server.

  *

  TLS is a cryptographic protocol that provides communications security for your Mule app.

  *

  TLS offers many different ways of exchanging keys for authentication, encrypting data, and guaranteeing message integrity Keystores and Truststores Truststore and keystore contents differ depending on whether they are used for clients or

  servers:

  For servers: the truststore contains certificates of the trusted clients, the keystore contains the private and public key of the server. For clients: the truststore contains certificates of the trusted servers, the keystore contains the private and

  public key of the client. Adding both a keystore and a truststore to the configuration implements two-way TLS authentication also known as mutual authentication.

  *

  in this case, correct answer is Support for TLS mutual (two-way) authentication with HTTP clients.

  

• Question 115:

  A global, high-volume shopping Mule application is being built and will be deployed to CloudHub. To improve performance, the Mule application uses a Cache scope that maintains cache state in a CloudHub object store. Web clients will access the Mule application over HTTP from all around the world, with peak volume coinciding with business hours in the web client's geographic location. To achieve optimal performance, what Anypoint Platform region should be chosen for the CloudHub object store?

  A. Choose the same region as to where the Mule application is deployed
  B. Choose the US-West region, the only supported region for CloudHub object stores
  C. Choose the geographically closest available region for each web client
  D. Choose a region that is the traffic-weighted geographic center of all web clients
  A. Choose the same region as to where the Mule application is deployed

  ---

  Explanation/Reference:

  CloudHub object store should be in same region where the Mule application is deployed.

  This will give optimal performance.

  Before learning about Cache scope and object store in Mule 4 we understand what is in general Caching is and other related things.

  WHAT DOES "CACHING" MEAN?

  Caching is the process of storing frequently used data in memory, file system or database which saves processing time and load if it would have to be accessed from original source location every time. In computing, a cache is a high-speed

  data storage layer which stores a subset of data, so that future requests for that data are served up faster than is possible by accessing the data's primary storage location. Caching allows you to efficiently reuse previously retrieved or

  computed data.

  How does Caching work?

  The data in a cache is generally stored in fast access hardware such as RAM (Random-access memory) and may also be used in correlation with a software component. A cache's primary purpose is to increase data retrieval performance by

  reducing the need to access the underlying slower storage layer.

  Caching in MULE 4

  In Mule 4 caching can be achieved in mule using cache scope and/or object-store. Cache scope internally uses Object Store to store the data.

  What is Object Store

  Object Store lets applications store data and states across batch processes, Mule components, and applications, from within an application. If used on cloud hub, the object store is shared between applications deployed on Cluster.

  Cache Scope is used in below-mentioned cases:

  Need to store the whole response from the outbound processor Data returned from the outbound processor does not change very frequently As Cache scope internally handle the cache hit and cache miss scenarios it is more readable Object

  Store is used in below-mentioned cases:

  Need to store custom/intermediary data

  To store watermarks

  Sharing the data/stage across applications, schedulers, batch. If CloudHub object store is in same region where the Mule application is deployed it will aid in fast access of data and give optimal performance.

• Question 116:

  A mule application designed to fulfil two requirements

  1.

  Processing files are synchronously from an FTPS server to a back-end database using VM intermediary queues for load balancing VM events

  2.

  Processing a medium rate of records from a source to a target system using batch job scope

  Considering the processing reliability requirements for FTPS files, how should VM queues be configured for processing files as well as for the batch job scope if the application is deployed to Cloudhub workers?

  A. Use Cloud hub persistent queues for FTPS files processing There is no need to configure VM queues for the batch jobs scope as it uses by default the worker's disc for VM queueing
  B. Use Cloud hub persistent VM queue for FTPS file processing There is no need to configure VM queues for the batch jobs scope as it uses by default the worker's JVM memory for VM queueing
  C. Use Cloud hub persistent VM queues for FTPS file processing Disable VM queue for the batch job scope
  D. Use VM connector persistent queues for FTPS file processing Disable VM queue for the batch job scope
  A. Use Cloud hub persistent queues for FTPS files processing There is no need to configure VM queues for the batch jobs scope as it uses by default the worker's disc for VM queueing

  ---

  Explanation/Reference:

  When processing files synchronously from an FTPS server to a back-end database using VM intermediary queues for load balancing VM events on CloudHub, reliability is critical. CloudHub persistent queues should be used for FTPS file processing to ensure that no data is lost in case of worker failure or restarts. These queues provide durability and reliability since they store messages persistently. For the batch job scope, it is not necessary to configure additional VM queues. By default, batch jobs on CloudHub use the worker's disk for VM queueing, which is reliable for handling medium-rate records processing from a source to a target system. This approach ensures that both FTPS file processing and batch job processing meet reliability requirements without additional configuration for batch job scope. References: MuleSoft Documentation on CloudHub and VM Queues Anypoint Platform Best Practices

• Question 117:

  An automation engineer needs to write scripts to automate the steps of the API lifecycle, including steps to create, publish, deploy and manage APIs and their implementations in Anypoint Platform.

  What Anypoint Platform feature can be used to automate the execution of all these actions in scripts in the easiest way without needing to directly invoke the Anypoint Platform REST APIs?

  A. Automated Policies in API Manager
  B. Runtime Manager agent
  C. The Mule Maven Plugin
  D. Anypoint CLI
  D. Anypoint CLI

  ---

  Explanation/Reference:

  Anypoint Platform provides a scripting and command-line tool for both Anypoint Platform and Anypoint Platform Private Cloud Edition (Anypoint Platform PCE). The command-line interface (CLI) supports both the interactive shell and standard CLI modes and works with: Anypoint Exchange Access management Anypoint Runtime Manager

• Question 118:

  What operation can be performed through a JMX agent enabled in a Mule application?

  A. View object store entries
  B. Replay an unsuccessful message
  C. Set a particular tog4J2 log level to TRACE
  D. Deploy a Mule application
  A. View object store entries

  ---

  Explanation/Reference:

  JMX Management Java Management Extensions (JMX) is a simple and standard way to manage applications, devices, services, and other resources. JMX is dynamic, so you can use it to monitor and manage resources as they are created, installed, and implemented. You can also use JMX to monitor and manage the Java Virtual Machine (JVM). Each resource is instrumented by one or more Managed Beans, or MBeans. All MBeans are registered in an MBean Server. The JMX server agent consists of an MBean Server and a set of services for handling Mbeans. There are several agents provided with Mule for JMX support. The easiest way to configure JMX is to use the default JMX support agent. Log4J Agent The log4j agent exposes the configuration of the Log4J instance used by Mule for JMX management. You enable the Log4J agent using the element. It does not take any additional properties MuleSoft Reference: https:// docs.mulesoft.com/mule-runtime/3.9/jmx-management

• Question 119:

  A company is designing an integration Mule application to process orders by submitting them to a back-end system for offline processing. Each order will be received by the Mule application through an HTTP5 POST and must be acknowledged immediately.

  Once acknowledged the order will be submitted to a back-end system. Orders that cannot be successfully submitted due to the rejections from the back-end system will need to be processed manually (outside the banking system).

  The mule application will be deployed to a customer hosted runtime and will be able to use an existing ActiveMQ broker if needed. The ActiveMQ broker is located inside the organization's firewall. The back-end system has a track record of unreliability due to both minor network connectivity issues and longer outages.

  Which combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the back-end system while supporting but minimizing manual order processing?

  A. One or more On Error scopes to assist calling the back-end system An Untill successful scope containing VM components for long retries A persistent dead-letter VM queue configure in Cloud hub
  B. An Until Successful scope to call the back-end system One or more ActiveMQ long-retry queues One or more ActiveMQ dead-letter queues for manual processing
  C. One or more on-Error scopes to assist calling the back-end system one or more ActiveMQ long-retry queues A persistent dead-letter Object store configuration in the CloudHub object store service
  D. A batch job scope to call the back in system An Untill successful scope containing Object Store components for long retries. A dead-letter object store configured in the Mule application
  B. An Until Successful scope to call the back-end system One or more ActiveMQ long-retry queues One or more ActiveMQ dead-letter queues for manual processing

  ---

  Explanation/Reference:

  To design an integration Mule application that processes orders and ensures reliability even with an unreliable back-end system, the following components and ActiveMQ queues should be used:

  Until Successful Scope: This scope ensures that the Mule application will continue trying to submit the order to the back-end system until it succeeds or reaches a specified retry limit. This helps in handling transient network issues or minor

  outages of the back-end system.

  ActiveMQ Long-Retry Queues: By placing the orders in long-retry queues, the application can manage retries over an extended period. This is particularly useful when the back-end system experiences longer outages. The ActiveMQ broker,

  located within the organization's firewall, can reliably handle these queues. ActiveMQ Dead-Letter Queues: Orders that cannot be successfully submitted after all retry attempts should be moved to dead-letter queues. This allows for manual

  processing of these orders. The dead-letter queue ensures that no orders are lost and provides a clear mechanism for handling failed submissions.

  Implementation Steps:

  HTTP Listener: Set up an HTTP listener to receive incoming orders. Immediate Acknowledgment: Immediately acknowledge the receipt of the order to the client. Until Successful Scope: Use the Until Successful scope to attempt submitting

  the order to the back-end system. Configure retry intervals and limits. Long-Retry Queues: Configure ActiveMQ long-retry queues to manage retries. Dead-Letter Queues: Set up ActiveMQ dead-letter queues for orders that fail after maximum

  retry attempts, allowing for manual intervention. This approach ensures that the system can handle temporary and prolonged back-end outages while minimizing manual processing.

  References:

  MuleSoft Documentation on Until Successful Scope:

  https://docs.mulesoft.com/mule-runtime/4.3/until-successful-scope ActiveMQ Documentation: https://activemq.apache.org/

• Question 120:

  A Mule application is being designed for deployment to a single CloudHub worker. The Mule application will have a flow that connects to a SaaS system to perform some operations each time the flow is invoked.

  The SaaS system connector has operations that can be configured to request a short-lived token (fifteen minutes) that can be reused for subsequent connections within the fifteen minute time window. After the token expires, a new token must be requested and stored. What is the most performant and idiomatic (used for its intended purpose) Anypoint Platform component or service to use to support persisting and reusing tokens in the Mule application to help speed up reconnecting the Mule application to the SaaS application?

  A. Nonpersistent object store
  B. Persistent object store
  C. Variable
  D. Database
  D. Database

  ---

  Explanation/Reference:

  Reference: https://docs.mulesoft.com/mule-runtime/4.4/reconnection-strategy-about