Mulesoft MCIA-LEVEL1 Online Practice Questions and Exam Preparation

Mulesoft MCIA-LEVEL1 Online Questions & Answers

• Question 111:

  Refer to the exhibit.

  An organization is designing a Mule application to receive data from one external business partner. The two companies currently have no shared IT infrastructure and do not want to establish one. Instead, all communication should be over the public internet (with no VPN).

  What Anypoint Connector can be used in the organization's Mule application to securely receive data from this external business partner?

  

  A. File connector
  B. VM connector
  C. SFTP connector
  D. Object Store connector
  C. SFTP connector

  ---

  # Object Store and VM Store is used for sharing data inter or intra mule applications in same setup. Can't be used with external Business Partner

  # Also File connector will not be useful as the two companies currently have no shared IT infrastructure. It's specific for local use.

  # Correct answer is SFTP connector. The SFTP Connector implements a secure file transport channel so that your Mule application can exchange files with external resources. SFTP uses the SSH security protocol to transfer messages. You can implement the SFTP endpoint as an inbound endpoint with a one-way exchange pattern, or as an outbound endpoint configured for either a one-way or request-response exchange pattern.

• Question 112:

  Which MuleSoft feature enables automated testing of Mule flows during CI/CD pipelines?

  A. API Designer
  B. MUnit
  C. Anypoint Monitoring
  D. Runtime Manager
  B. MUnit

  ---

  MUnit is MuleSoft's native testing framework that allows developers to write automated unit and integration tests for Mule applications, supporting continuous integration and delivery.

• Question 113:

  An organization's security requirements mandate centralized control at all times over authentication and authorization of external applications when invoking web APIs managed on Anypoint Platform. What Anypoint Platform feature is most idiomatic (used for its intended purpose), straightforward, and maintainable to use to meet this requirement?

  A. Client management configured in access management
  B. Identity management configured in access management
  C. Enterprise Security module coded in Mule applications
  D. External access configured in API Manager
  B. Identity management configured in access management

  ---

  https://blogs.mulesoft.com/dev-guides/api-security-ways-to-authenticate-and-authorize/

• Question 114:

  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

  ---

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

• Question 115:

  An organization plans to extend its Mule APIs to the EU (Frankfurt) region.

  Currently, all Mule applications are deployed to CloudHub 1.0 in the default North American region, from the North America control plane, following this naming convention: {API-name}--{environment} (for example, Orderssapi--dev, Orders-sapi---qa, Orders-sapi---prod, etc.).

  There is no network restriction to block communications between APIs.

  What strategy should be implemented in order to deploy the same Mule APIs to the CloudHub 1.0 EU region from the North America control plane,

  as well as to minimize latency between APIs and target users and systems in Europe?

  A. In Runtime Manager, for each Mule application deployment, set the Region property to EU (Frankfurt) and reuse the same Mule application mame as in the North American region. Communicate the new urls {API-name}--{environment}.de-ci.cloudhub.io to the consuming API clients In Europe.
  B. In API Manager, set the Region property to EU (Frankfurt) to create an API proxy named {API-name}--proxy--{environment} for each Mule application. Communicate the new url {API-name}--proxy--{environment}.de-c1.cloudhub.io to the consuming API clients In Europe.
  C. In Runtime Manager, for each Mule application deployment, leave the Region property blank (default) and change the Mule application name to {API-name}-- {environment).de-cl. Communicate the new urls {API-name}--{environment}.de-ci1.cloudhub.io to the consuming API clients in Europe.
  D. In API Manager, leave the Region property blank (default) to deploy an API proxy named {API-name}~proxy~- (environment}.de-cl for each Mule application. Communicate the new url {API-name}--proxy--{environment}.de-cl.cloudhub.io to the consuming API clients in Europe.
  A. In Runtime Manager, for each Mule application deployment, set the Region property to EU (Frankfurt) and reuse the same Mule application mame as in the North American region. Communicate the new urls {API-name}--{environment}.de-ci.cloudhub.io to the consuming API clients In Europe.

  ---

  To extend Mule APIs to the EU (Frankfurt) region and minimize latency for European users, follow these steps:

  Set Region Property: In Runtime Manager, for each Mule application deployment, set the Region property to EU (Frankfurt). This deploys the application to the desired region, optimizing performance for European users.

  Reuse Application Names: Keep the same Mule application names as used in the North American region. This approach maintains consistency and simplifies management.

  Communicate New URLs: Inform the consuming API clients in Europe of the new URLs in the format {API-name}--{environment}.de-ci.cloudhub.io . These URLs will direct the clients to the applications deployed in the EU region, ensuring reduced latency and improved performance.

  This strategy effectively deploys the same Mule APIs to the CloudHub EU region, leveraging the existing control plane in North America.

• Question 116:

  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
  C. Anypoint monitoring agent on each mule runtime Anypoint monitoring agent sends monitoring data from the mule applications to Anypoint monitoring

• Question 117:

  Refer to the exhibit.

  

  A Mule application is being designed to be deployed to several CIoudHub workers. The Mule application's integration logic is to replicate changed Accounts from Satesforce to a backend system every 5 minutes.

  A watermark will be used to only retrieve those Satesforce Accounts that have been modified since the last time the integration logic ran.

  What is the most appropriate way to implement persistence for the watermark in order to support the required data replication integration logic?

  

  A. Persistent Anypoint MQ Queue
  B. Persistent Object Store
  C. Persistent Cache Scope
  D. Persistent VM Queue
  B. Persistent Object Store

  ---

  # An object store is a facility for storing objects in or across Mule applications. Mule uses object stores to persist data for eventual retrieval.

  # Mule provides two types of object stores:

  1) In-memory store ?stores objects in local Mule runtime memory. Objects are lost on shutdown of the Mule runtime.

  2) Persistent store ?Mule persists data when an object store is explicitly configured to be persistent.

  In a standalone Mule runtime, Mule creates a default persistent store in the file system. If you do not specify an object store, the default persistent object store is used. MuleSoft

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

• Question 118:

  An API implementation is being designed that must invoke an Order API which is known to repeatedly experience downtime. For this reason a fallback API is to be called when the Order API is unavailable. What approach to designing invocation of the fallback API provides the best resilience?

  A. Redirect client requests through an HTTP 303 temporary redirect status code to the fallback API whenever the Order API is unavailable
  B. Set an option in the HTTP Requester component that invokes the order API to instead invoke a fallback API whenever an HTTP 4XX or 5XX response status code is received from Order API
  C. Create a separate entry for the order API in API manager and then invoke this API as a fallback API if the primary Order API is unavailable
  D. Search Anypoint Exchange for a suitable existing fallback API and them implement invocations to their fallback API in addition to the Order API
  A. Redirect client requests through an HTTP 303 temporary redirect status code to the fallback API whenever the Order API is unavailable

  ---

  # Resilience testing is a type of software testing that observes how applications act under stress. It's meant to ensure the product's ability to perform in chaotic conditions without a loss of core functions or data; it ensures a quick recovery after unforeseen, uncontrollable events.

  # In case an API invocation fails -- even after a certain number of retries -- it might be adequate to invoke a different API as a fallback. A fallback API, by definition, will never be ideal for the purpose of the API client, otherwise it would be the primary API.

  # Here are some examples for fallback APIs:

  -An old, deprecated version of the same API.

  - An alternative endpoint of the same API and version (e.g. API in another CloudHub region).

  - An API doing more than required, and therefore not as performant as the primary API.

  - An API doing less than required and therefore forcing the API Client to offer a degraded service, which is still better than no service at all.

  # API clients implemented as Mule applications offer the `Until Successful Scope and Exception' strategies at their disposal, which together allow configuring fallback actions such as a fallback API invocation.

  # All HTTP response status codes within the 3xx category are considered redirection messages. These codes indicate to the user agent (i.e. your web browser) that an additional action is required in order to complete the request and access the desired resource

  

  Hence correct answer is Redirect client requests through an HTTP 303 temporary redirect status code to the fallback API whenever the Order API is unavailable

• Question 119:

  Which Exchange asset type represents configuration modules that extend the functionality of an API and enforce capabilities such as security?

  A. Rulesets
  B. Policies
  C. RESTAPIs
  D. Connectors
  B. Policies

• Question 120:

  Cloud Hub is an example of which cloud computing service model?

  A. Platform as a Service (PaaS)
  B. Software as a Service (SaaS)
  C. Monitoring as a Service (MaaS)
  D. Infrastructure as a Service (laaS)
  A. Platform as a Service (PaaS)