Mulesoft MCIA-LEVEL1 Online Practice Questions and Exam Preparation

Mulesoft MCIA-LEVEL1 Online Questions & Answers

• Question 41:

  A manufacturing company is developing a new set of APIs for its retail business. One of the APIs is a Master Look Up API, which is a System API,

  The API uses a persistent object-store. This API will be used by almost all other APIs to provide master lookup data.

  The Master Look Up API is deployed on two CloudHub workers of 0.1 vCore each because there is a lot of master data to be cached. Most of the master

  lookup data is stored as a key-value pair. The cache gets refreshed if the key is not found in the cache.

  During performance testing, it was determined that the Master Look Up API has a high response time due to the latency of database queries executed to fetch the master lookup data.

  

  What two methods can be used to resolve these performance issues? Choose 2 answers

  A. Implement the HTTP caching policy for all GET endpoints for the Master Look Up API
  B. Implement an HTTP caching policy for all GET endpoints in the Master Look Up API
  C. Implement locking to synchronize access to the Object Store
  D. Upgrade the vCore size from 0.1 vCore to 0.2 vCore
  A. Implement the HTTP caching policy for all GET endpoints for the Master Look Up API
  D. Upgrade the vCore size from 0.1 vCore to 0.2 vCore

  ---

  AnTo resolve performance issues with the Master Look Up API, the following methods can be applied:

  Implement the HTTP caching policy for all GET endpoints for the Master Look Up API: This caching policy helps reduce the number of database queries by storing frequently accessed data in cache, thus improving response times for subsequent requests.

  Upgrade the vCore size from 0.1 vCore to 0.2 vCore: Increasing the vCore size can provide more computational resources, which can improve the processing power and overall performance of the API, particularly under high load conditions.

• Question 42:

  A travel company wants to publish a well-defined booking service API to be shared with its business partners. These business partners have agreed to ONLY consume SOAP services and they want to get the service contracts in an easily consumable way before they start any development. The travel company will publish the initial design documents to Anypoint Exchange, then share those documents with the business partners. When using an API-led approach, what is the first design document the travel company should deliver to its business partners?

  A. Create a WSDL specification using any XML editor
  B. Create a RAML API specification using any text editor
  C. Create an OAS API specification in Design Center
  D. Create a SOAP API specification in Design Center
  A. Create a WSDL specification using any XML editor

  ---

  SOAP API specifications are provided as WSDL. Design center doesn't provide the functionality to create WSDL file. Hence WSDL needs to be created using XML editor

• Question 43:

  Refer to the exhibit.

  

  An organization deploys multiple Mule applications to the same customer -hosted Mule runtime. Many of these Mule applications must expose an HTTPS endpoint on the same port using a server-side certificate that rotates often.

  What is the most effective way to package the HTTP Listener and package or store the server-side certificate when deploying these Mule applications, so the disruption caused by certificate rotation is minimized?

  A. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint Package the server- side certificate in ALL Mule APPLICATIONS that need to expose an HTTPS endpoint
  B. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION
  C. Package an HTTPS Listener configuration In all Mule APPLICATIONS that need to expose an HTTPS endpoint Package the server-side certificate in a NEW Mule DOMAIN project
  D. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing It from all Mule applications that need to expose an HTTPS endpoint. Package the server- side certificate in the SAME Mule DOMAIN project Go to Set
  B. Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION

  ---

  In this scenario, both A and C will work, but A is better as it does not require repackage to the domain project at all.

  Correct answer is Package the HTTPS Listener configuration in a Mule DOMAIN project, referencing it from all Mule applications that need to expose an HTTPS endpoint. Store the server-side certificate in a shared filesystem location in the Mule runtime's classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION.

  What is Mule Domain Project?

  # A Mule Domain Project is implemented to configure the resources that are shared among different projects. These resources can be used by all the projects associated with this domain. Mule applications can be associated with only one domain, but a domain can be associated with multiple projects. Shared resources allow multiple development teams to work in parallel using the same set of reusable connectors. Defining these connectors as shared resources at the domain level allows the team to: Expose multiple services within the domain through the same port. - Share the connection to persistent storage. - Share services between apps through a well-defined interface. - Ensure consistency between apps upon any changes because the configuration is only set in one place.

  # Use domains Project to share the same host and port among multiple projects. You can declare the http connector within a domain project and associate the domain project with other projects. Doing this also allows to control thread settings, keystore configurations, time outs for all the requests made within multiple applications. You may think that one can also achieve this by duplicating the http connector configuration across all the applications. But, doing this may pose a nightmare if you have to make a change and redeploy all the applications.

  # If you use connector configuration in the domain and let all the applications use the new domain instead of a default domain, you will maintain only one copy of the http connector configuration. Any changes will require only the domain to the redeployed instead of all the applications. You can start using domains in only three steps: 1) Create a Mule Domain project 2) Create the global connector configurations which needs to be shared across the applications inside the Mule Domain project 3) Modify the value of domain in mule-deploy.properties file of the applications

  

  Use a certificate defined in already deployed Mule domain Configure the certificate in the domain so that the API proxy HTTPS Listener references it, and then deploy the secure API proxy to the target Runtime Fabric, or on-premises target. (CloudHub is not supported with this approach because it does not support Mule domains.)

• Question 44:

  When a Mule application using VM queues is deployed to a customer-hosted cluster or multiple CloudHub v1.0 workers/replicas, how are messages consumed across the nodes?

  A. Sequentially, from a dedicated Anypoint MQ queue
  B. Sequentially, only from the primary node
  C. In a non-deterministic way
  D. Round-robin, within an XA transaction
  C. In a non-deterministic way

  ---

  When a Mule application using VM queues is deployed to a customer-hosted cluster or multiple CloudHub v1.0 workers/replicas, messages are consumed in a non-deterministic way. This means that any of the nodes in the cluster or any of the workers can consume the messages from the VM queues, but there is no guaranteed order or specific pattern (such as round-robin or sequential processing).

  This non-deterministic message consumption helps in distributing the load and handling messages more efficiently across multiple nodes or workers, improving the scalability and reliability of the application.

  References MuleSoft Documentation on VM Queues and Clustering Best Practices for Deploying Mule Applications in Clusters

• Question 45:

  An organization plans to use the Anypoint Platform audit logging service to log Anypoint MQ actions. What consideration must be kept in mind when leveraging Anypoint MQ Audit Logs?

  A. Anypoint MQ Audit Logs include logs for sending, receiving, or browsing messages
  B. Anypoint MQ Audit Logs include fogs for failed Anypoint MQ operations
  C. Anypoint MQ Audit Logs include logs for queue create, delete, modify, and purge operations
  C. Anypoint MQ Audit Logs include logs for queue create, delete, modify, and purge operations

  ---

  When leveraging Anypoint MQ Audit Logs, it's important to note that they include logs for operations such as creating, deleting, modifying, and purging queues. These logs are crucial for auditing and monitoring the state and changes made to the message queues within Anypoint MQ. However, they do not include logs for individual message actions like sending, receiving, or browsing messages.

  References MuleSoft Documentation on Anypoint MQ Audit Logs Anypoint Platform Audit Logging Overview

• Question 46:

  What is the primary benefit of decoupling Experience APIs from System APIs?

  A. Reduced latency
  B. Independent evolution of consumer and backend layers
  C. Elimination of API governance
  D. Simplified deployment pipelines
  B. Independent evolution of consumer and backend layers

  ---

  Decoupling allows Experience APIs and System APIs to evolve independently, improving agility and reducing the impact of changes.

• Question 47:

  According to MuleSoft, what is a major distinguishing characteristic of an application network in relation to the integration of systems, data, and devices?

  A. It uses a well-organized monolithic approach with standards
  B. It is built for change and self-service
  C. It leverages well-accepted internet standards like HTTP and JSON
  D. It uses CI/CD automation for real-time project delivery
  B. It is built for change and self-service

• Question 48:

  A marketing organization is designing a Mule application to process campaign data. The Mule application will periodically check for a file in a SFTP location and process the records in the file. The size of the file can vary from 10MB to 5GB. Due to the limited availabiltty of vCores, the Mule application is deployed to a single CloudHub worker configured with vCore size 0.2.

  The application must transform and send different formats of this file to three different downstream SFTP locations.

  What is the most idiomatic (used for its intended purpose) and performant way to configure the SFTP operations or event sources to process the large files to support these deployment requirements?

  A. Use an in-memory repeatable stream
  B. Use a file-stored non-repeatable stream
  C. Use an in-memory non-repeatable stream
  D. Use a file-stored repeatable stream
  A. Use an in-memory repeatable stream

  ---

  https://docs.mulesoft.com/mule-runtime/4.4/streaming-about

• Question 49:

  According to MuleSoft, which major benefit does a Center for Enablement (C4E) provide for an enterprise and its lines of business?

  A. Enabling Edge security between the lines of business and public devices
  B. Centralizing project management across the lines of business
  C. Centrally managing return on investment (ROI) reporting from lines of business to leadership
  D. Accelerating self-service by the lines of business
  B. Centralizing project management across the lines of business

• Question 50:

  What is not true about Mule Domain Project?

  A. This allows Mule applications to share resources
  B. Expose multiple services within the Mule domain on the same port
  C. Only available Anypoint Runtime Fabric
  D. Send events (messages) to other Mule applications using VM queues
  C. Only available Anypoint Runtime Fabric

  ---

  # Mule Domain Project is ONLY available for customer-hosted Mule runtimes, but not for Anypoint Runtime Fabric

  # Mule domain project is available for Hybrid and Private Cloud (PCE). Rest all provide application isolation and can't support domain project. What is Mule Domain Project?

  # A Mule Domain Project is implemented to configure the resources that are shared among different projects. These resources can be used by all the projects associated with this domain. Mule applications can be associated with only one domain, but a domain can be associated with multiple projects. Shared resources allow multiple development teams to work in parallel using the same set of reusable connectors. Defining these connectors as shared resources at the domain level allows the team to: Expose multiple services within the domain through the same port. - Share the connection to persistent storage. - Share services between apps through a well-defined interface. - Ensure consistency between apps upon any changes because the configuration is only set in one place.

  # Use domains Project to share the same host and port among multiple projects. You can declare the http connector within a domain project and associate the domain project with other projects. Doing this also allows to control thread settings, keystore configurations, time outs for all the requests made within multiple applications. You may think that one can also achieve this by duplicating the http connector configuration across all the applications. But, doing this may pose a nightmare if you have to make a change and redeploy all the applications.

  # If you use connector configuration in the domain and let all the applications use the new domain instead of a default domain, you will maintain only one copy of the http connector configuration. Any changes will require only the domain to the redeployed instead of all the applications. You can start using domains in only three steps: 1) Create a Mule Domain project 2) Create the global connector configurations which needs to be shared across the applications inside the Mule Domain project 3) Modify the value of domain in mule-deploy.properties file of the applications