Mulesoft MCIA-LEVEL1 Online Practice Questions and Exam Preparation

Mulesoft MCIA-LEVEL1 Online Questions & Answers

• Question 171:

  A team has completed the build and test activities for a Mule application that implements a System API for its application network. Which Anypoint Platform component should the team now use to both deploy and monitor the System AP\ implementation?

  A. API Manager
  B. Design Center
  C. Anypoint Exchange
  D. Runtime Manager
  D. Runtime Manager

• Question 172:

  What is the MuleSoft-recommended best practice to share the connector and configuration information among the APIs?

  A. Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API
  B. Build a separate Mule domain project for each API, and configure each of them to use a file on a shared file store to load the configuration information dynamically
  C. Build another System API that connects to the database, and refactor all the other APIs to make requests through the new System API to access the database
  D. Create an API proxy for each System API and share the Database connector configuration with all the API proxies via an automated policy
  A. Build a Mule domain project, add the Database connector and configuration to it, and reference this one domain project from each System API

  ---

  The MuleSoft-recommended best practice for sharing the connector and configuration information among multiple APIs is to use a Mule domain project. The steps are:

  Create a Mule domain project.

  Add the Database connector and its configuration to the domain project.

  Reference this domain project from each System API that needs to use the Database connector and configuration.

  By using a domain project, you centralize the configuration and reuse it across multiple APIs. This approach ensures consistency, reduces duplication, and simplifies maintenance and updates to the connector configuration.

  References

  MuleSoft Documentation on Domain Projects Best Practices for Reusable Configuration in MuleSoft

• Question 173:

  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.

  ---

  # 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

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

  Additional Info:

  When to use Object Store and when to use VM

• Question 174:

  An insurance provider is implementing Anypoint platform to manage its application infrastructure and is using the customer hosted runtime for its business due to certain financial requirements it must meet. It has built a number of synchronous API's and is currently hosting these on a mule runtime on one server.

  These applications make use of a number of components including heavy use of object stores and VM queues.

  Business has grown rapidly in the last year and the insurance provider is starting to receive reports of reliability issues from its applications.

  The DevOps team indicates that the API's are currently handling too many requests and this is over loading the server. The team has also mentioned that there is a significant downtime when the server is down for maintenance.

  As an integration architect, which option would you suggest to mitigate these issues?

  A. Add a load balancer and add additional servers in a server group configuration
  B. Add a load balancer and add additional servers in a cluster configuration
  C. Increase physical specifications of server CPU memory and network
  D. Change applications by use an event-driven model
  B. Add a load balancer and add additional servers in a cluster configuration

• Question 175:

  When deploying Mule applications to CloudHub, which factor primarily determines scalability?

  A. Number of deployed APIs
  B. Worker size and number of workers
  C. Number of flows in the application
  D. Logging configuration
  B. Worker size and number of workers

  ---

  CloudHub scalability is achieved by adjusting worker size (vertical scaling) and the number of workers (horizontal scaling).

• Question 176:

  An organization has various integrations implemented as Mule applications. Some of these Mule applications are deployed to custom hosted Mule runtimes (on-premises) while others execute in the MuleSoft-hosted runtime plane (CloudHub). To perform the Integra functionality, these Mule applications connect to various backend systems, with multiple applications typically needing to access the backend systems.

  How can the organization most effectively avoid creating duplicates in each Mule application of the credentials required to access the backend systems?

  A. Create a Mule domain project that maintains the credentials as Mule domain-shared resources Deploy the Mule applications to the Mule domain, so the credentials are available to the Mule applications
  B. Store the credentials in properties files in a shared folder within the organization's data center Have the Mule applications load properties files from this shared location at startup
  C. Segregate the credentials for each backend system into environment-specific properties files Package these properties files in each Mule application, from where they are loaded at startup
  D. Configure or create a credentials service that returns the credentials for each backend system, and that is accessible from customer-hosted and MuleSoft-hosted Mule runtimes Have the Mule applications toad the properties at startup by invoking that credentials service
  D. Configure or create a credentials service that returns the credentials for each backend system, and that is accessible from customer-hosted and MuleSoft-hosted Mule runtimes Have the Mule applications toad the properties at startup by invoking that credentials service

  ---

  "Create a Mule domain project that maintains the credentials as Mule domain-shared resources" is wrong as domain project is not supported in Cloudhub # We should Avoid Creating duplicates in each Mule application but below two options cause duplication of credentials - Store the credentials in properties files in a shared folder within the organization's data center. Have the Mule applications load properties files from this shared location at startup - Segregate the credentials for each backend system into environment- specific properties files. Package these properties files in each Mule application, from where they are loaded at startup So these are also wrong choices # Credentials service is the best approach in this scenario. Mule domain projects are not supported on CloudHub. Also its is not recommended to have multiple copies of configuration values as this makes difficult to maintain Use the Mule Credentials Vault to encrypt data in a .properties file. (In the context of this document, we refer to the .properties file simply as the properties file.) The properties file in Mule stores data as key-value pairs which may contain information such as usernames, first and last names, and credit card numbers. A Mule application may access this data as it processes messages, for example, to acquire login credentials for an external Web service. However, though this sensitive, private data must be stored in a properties file for Mule to access, it must also be protected against unauthorized ?and potentially malicious ? use by anyone with access to the Mule application

• Question 177:

  Organization wants to achieve high availability goal for Mule applications in customer hosted runtime plane. Due to the complexity involved, data cannot be shared among of different instances of same Mule application. What option best suits to this requirement considering high availability is very much critical to the organization?

  A. The cluster can be configured
  B. Use third party product to implement load balancer
  C. High availability can be achieved only in CloudHub
  D. Use persistent object store
  B. Use third party product to implement load balancer

  ---

  High availability is about up-time of your application A) High availability can be achieved only in CloudHub isn't correct statement. It can be achieved in customer hosted runtime planes as well B) An object store is a facility for storing objects in or across Mule applications. Mule runtime engine (Mule) uses object stores to persist data for eventual retrieval. It can be used for disaster recovery but not for High Availability. Using object store can't guarantee that all instances won't go down at once. So not an appropriate choice.

  https://docs.mulesoft.com/mule-runtime/4.3/mule-object-stores

  C) High availability can be achieved by below two models for on-premise MuleSoft implementations.

  1) Mule Clustering ?Where multiple Mule servers are available within the same cluster environment and the routing of requests will be done by the load balancer. A cluster is a set of up to eight servers that act as a single deployment target and high-availability processing unit. Application instances in a cluster are aware of each other, share common information, and synchronize statuses. If one server fails, another server takes over processing applications. A cluster can run multiple applications. ( refer left half of the diagram)

  In given scenario, it's mentioned that 'data cannot be shared among of different instances'.

  So this is not a correct choice.

  https://docs.mulesoft.com/runtime-manager/cluster-about

  2) Load balanced standalone Mule instances ?The high availability can be achieved even without cluster, with the usage of third party load balancer pointing requests to different Mule servers. This approach does not share or synchronize data between Mule runtimes. Also high availability achieved as load balanced algorithms can be implemented using external load balancer. ( refer right half of the diagram)

• Question 178:

  An organization is sizing an Anypoint VPC to extend their internal network to Cloudhub.

  For this sizing calculation, the organization assumes 150 Mule applications will be deployed among three(3) production environments and will use Cloudhub's default zero- downtime feature. Each Mule application is expected to be configured with two(2) Cloudhub workers.This is expected to result in several Mule application deployments per hour.

  A. 10.0.0.0/21(2048 IPs)
  B. 10.0.0.0/22(1024IPs)
  C. 10.0.0.0/23(512 IPs)
  D. 10.0.0.0/24(256 IPs)
  A. 10.0.0.0/21(2048 IPs)

  ---

  # When you create an Anypoint VPC, the range of IP addresses for the network must be specified in the form of a Classless Inter-Domain Routing (CIDR) block, using CIDR notation.

  # This address space is reserved for Mule workers, so it cannot overlap with any address space used in your data center if you want to peer it with your VPC.

  # To calculate the proper sizing for your Anypoint VPC, you first need to understand that the number of dedicated IP addresses is not the same as the number of workers you have deployed.

  # For each worker deployed to CloudHub, the following IP assignation takes place: For better fault tolerance, the VPC subnet may be divided into up to four Availability Zones.

  # A few IP addresses are reserved for infrastructure. At least two IP addresses per worker to perform at zero-downtime.

  # Hence in this scenario 2048 IP's are required to support the requirement.

• Question 179:

  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

• Question 180:

  An organization is in the process of building automated deployments using a CI/CD process. As a part of automated deployments, it wants to apply policies to API Instances. What tool can the organization use to promote and deploy API Manager policies?

  A. Anypoint CLI
  B. MUnit Maven plugin
  C. Mule Maven plugin
  D. Runtime Manager agen
  A. Anypoint CLI

  ---

  To automate the promotion and deployment of API Manager policies as part of a CI/CD process, an organization can use the Anypoint CLI (Command Line Interface). The Anypoint CLI provides a set of commands to interact with various components of the Anypoint Platform, including API Manager.

  Using the Anypoint CLI, you can:

  Apply policies to API instances.

  Promote APIs and their associated policies across different environments.

  Script these actions as part of the CI/CD pipeline to ensure consistency and automation in managing API policies.

  Other tools like the MUnit Maven plugin, Mule Maven plugin, and Runtime Manager agent do not provide direct capabilities to manage API Manager policies.

  References: MuleSoft Anypoint CLI Documentation Automating API Management with Anypoint CLI