[Jul 17, 2022] New 2022 MuleSoft MCIA-Level-1 Exam Dumps with PDF from PremiumVCEDump (Updated 132 Questions) [Q44-Q63]

NO.44 A Mule application is deployed to a cluster of two(2) cusomter-hosted Mule runtimes. Currently the node name Alice is the primary node and node named bob is the secondary node. The mule application has a flow that polls a directory on a file system for new files.
The primary node Alice fails for an hour and then restarted.
After the Alice node completely restarts, from what node are the files polled, and what node is now the primary node for the cluster?

Files are polled from Alice node
Alice is now the primary node

Files are polled form Bob node
Alice is now the primary node

Files are polled from Alice node
Bob is the now the primary node

Files are polled form Bob node
Bob is now the primary node

NO.45 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?

Persistent Anypoint MQ Queue

Persistent Object Store

Persistent Cache Scope

Persistent VM Queue

NO.46 An organization has decided on a cloud migration strategy that aims to minimize the organization’s own IT resources. Currently, the organization has all of its Mule applications running on its own premises and uses an on-premises load balancer that exposes all APIs under the base URL https://api.acme.com.
As part of the migration strategy, the organization plans to migrate all of its Mule applications and load balancer to CloudHub.
What is the most straight-forward and cost-effective approach to Mule application deployment and load balancing that preserves the public URLs?

Deploy the Mule applications to CloudHub
Update the CNAME record for api.acme.com in the organization’s DNS server pointing to the A record of the CloudHub Shared Load Balancer (SLB) Apply mapping rules in the SLB to map URLs to their corresponding Mule applications

Deploy the Mule applications to CloudHub
Create a CNAME record for api.acme.com in the CloudHub Shared Load Balancer (SLB) pointing to the A record of the on-premises load balancer Apply mapping rules in the SLB to map URLs to their corresponding Mule applications

Deploy the Mule applications to CloudHub
Update the CNAME record for api.acme.com in the organization’s DNS server pointing to the A record of a CloudHub dedicated load balancer (DLB) Apply mapping rules in the DLB to map URLs to their corresponding Mule applications

For each migrated Mule application, deploy an API Proxy Mule application to CloudHub, with all applications under the control of a CloudHub dedicated load balancer (DLB) Update the CNAME record for api.acme.com in the organization’s DNS server pointing to the A record of a CloudHub dedicated load balancer (DLB) Apply mapping rules in the DLB to map each API Proxy application to its corresponding Mule application

NO.47 Refer to the exhibit.

A Mule application is deployed to a cluster of two customer-hosted Mute runtimes. The Mute application has a flow that polls a database and another flow with an HTTP Listener.
HTTP clients send HTTP requests directly to individual cluster nodes.
What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has railed, but before that node is restarted?

Database polling continues Only HTTP requests sent to the remaining node continue to be accepted

Database polling stops All HTTP requests continue to be accepted

Database polling continues All HTTP requests continue to be accepted, but requests to the failed node Incur increased latency

Database polling stops All HTTP requests are rejected

NO.48 Refer to the exhibit.

An organization uses a 2-node Mute runtime cluster to host one stateless API implementation. The API is accessed over HTTPS through a load balancer that uses round-robin for load distribution.
Two additional nodes have been added to the cluster and the load balancer has been configured to recognize the new nodes with no other change to the load balancer.
What average performance change is guaranteed to happen, assuming all cluster nodes are fully operational?

50% reduction in the response time of the API

100% increase in the throughput of the API

50% reduction In the JVM heap memory consumed by each node

50% reduction In the number of requests being received by each node

NO.49 In a Mule Application, a flow contains two (2) JMS consume operations that are used to connect to a JMS broker and consume messages from two(2) JMS destination. The Mule application then joins the two JMS messages together.
The JMS broker does not implement high availability (HA) and periodically experiences scheduled outages of upto 10 mins for routine maintenance.
What is the most idiomatic (used for its intented purpose) way to build the mule flow so it can best recover from the expected outages?

Configure a reconnection strategy for the JMS connector

Enclose the two(2) JMS operation in an Until Successful scope

Consider a transaction for the JMS connector

Enclose the two(2) JMS operations in a Try scope with an Error Continue error handler

NO.50 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?

Use an object store connector configured to access the Pub Mule application persistence object store

Use a VM connector configured to directly access the persistence queue of the Pub Mule application persistence object store.

Use an Anypoint MQ connector configured to directly access the Pub Mule application persistence object store

Use the Object store v2 REST API configured to access the Pub Mule application persistence object store.

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

Support for TLS mutual (two-way) authentication with HTTP clients

Encryption of requests to both subdomains and API resource endpoints fhttPs://aDi.customer.com/ and
https://customer.com/api)

Encryption of both HTTP request and HTTP response bodies for all HTTP clients

Encryption of both HTTP request header and HTTP request body for all HTTP clients

NO.52 A set of integration Mule applications, some of which expose APIs, are being created to enable a new business process. Various stakeholders may be impacted by this. These stakeholders are a combination of semi-technical users (who understand basic integration terminology and concepts such as JSON and XML) and technically skilled potential consumers of the Mule applications and APIs.
What Is an effective way for the project team responsible for the Mule applications and APIs being built to communicate withthese stakeholders using Anypoint Platform and its supplied toolset?

Use Anypoint Design Center to implement the Mule applications and APIs and give the various stakeholders access to these Design Center projects, so they can collaborate and provide feedback

Create Anypoint Exchange entries with pages elaborating the integration design, including API notebooks (where applicable) to help the stakeholders understand and interact with the Mule applications and APIs at various levels of technical depth

Use Anypoint Exchange to register the various Mule applications and APIs and share the RAML definitions with the stakeholders, so they can be discovered

Capture documentation about the Mule applications and APIs inline within the Mule integration flows and use Anypoint Studio’s Export Documentation feature to provide an HTML version of this documentation to the stakeholders

NO.53 Refer to the exhibit.

An organization deploys multiple Mule applications to the same customer -hosted Mule runtime. Many of these Mule applications must expose anHTTPS 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?

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 thatneed to expose an HTTPS endpoint

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 theMule runtime’s classpath, OUTSIDE the Mule DOMAIN or any Mule APPLICATION

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

Packagethe 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

NO.54 Refer to the exhibit.
A Mule application is deployed to a multi-node Mule runtime cluster. The Mule application uses the competing consumer pattern among its cluster replicas to receive JMS messages from a JMS queue. To process each received JMS message, the following steps are performed in a flow:
Step l: The JMS Correlation ID header is read from the received JMS message.
Step 2: The Mule application invokes an idempotent SOAP webservice over HTTPS, passing the JMS Correlation ID as one parameter in the SOAP request.
Step 3: The response from the SOAP webservice also returns the same JMS Correlation ID.
Step 4: The JMS Correlation ID received from the SOAP webservice is validated to be identical to the JMS Correlation ID received in Step 1.
Step 5: The Mule application creates a response JMS message, setting the JMS Correlation ID message header to the validated JMS Correlation ID and publishes that message to a response JMS queue.
Where should the Mule application store the JMS Correlation ID values received in Step 1 and Step 3 so that the validation in Step 4 can be performed, while also making the overall Mule application highly available, fault-tolerant, performant, and maintainable?

Both Correlation ID values should be stored in a persistent object store

Both Correlation ID values should be stored In a non-persistent object store

The Correlation ID value in Step 1 should be stored in a persistent object store The Correlation ID value in step 3 should be stored as a Mule event vanable/attnbute

Both Correlation ID values should be stored as Mule event vanabtes/attnbutes

NO.55 An Organization has previously provisioned its own AWS VPC hosting various servers. The organization now needs to use Cloudhub to host a Mule application that will implement a REST API once deployed to Cloudhub, this Mule application must be able to communicate securely with the customer-provisioned AWS VPC resources within the same region, without being interceptable on the public internet.
What Anypoint Platform features should be used to meet these network communication requirements between Cloudhub and the existing customer-provisioned AWS VPC?

Add a Mulesoft hosted Anypoint VPC configured and with VPC Peering to the AWS VPC

Configure an external identity provider (IDP) in Anypoint Platform with certificates from the customer provisioned AWS VPC

Add a default API Whitelisting policy to API Manager to automatically whitelist the customer provisioned AWS VPC IP ranges needed by the Mule applicaton

Use VM queues in the Mule application to allow any non-mule assets within the customer provisioned AWS VPC to subscribed to and receive messages

NO.56 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?

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

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

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

Package the HTTPS Listener configuration in a MuleDOMAIN project, referencing It from all Mule applications that need to expose an HTTPS endpoint Package the server-side certificatein the SAME Mule DOMAIN projectGo to Set

NO.57 A set of integration Mule applications, some of which expose APIs, are being created to enable a new business process. Various stakeholders may be impacted by this. These stakeholders are a combination of semi-technical users (who understand basic integration terminology and concepts such as JSON and XML) and technically skilled potential consumers of the Mule applications and APIs.
What Is an effective way for the project team responsible for the Mule applications and APIs being built to communicate with these stakeholders using Anypoint Platform and its supplied toolset?

Use Anypoint Design Center to implement the Mule applications and APIs and give the various stakeholders access to these Design Center projects, so they can collaborate and provide feedback

Create Anypoint Exchange entries with pages elaborating the integration design, including API notebooks (where applicable) to help the stakeholders understand and interact with the Mule applications and APIs at various levels of technical depth

Use Anypoint Exchange to register the various Mule applications and APIs and share the RAML definitions with the stakeholders, so they can be discovered

Capture documentation about the Mule applications and APIs inline within the Mule integration flows and use Anypoint Studio’s Export Documentation feature to provide an HTML version of this documentation to the stakeholders

NO.58 An organization has various integrations implemented as Mule applications. Some of these Mule applications are deployed to customer-hosted Mule runtimes (on-premises) while others execute in the MuleSoft-hosted runtime plane (CloudHub). To perform the integration functionality, these Mule applications connect to various backend systems, with multiple applications typically needing to access the same backend systems.
How can the organization most effectively avoid creating duplicates in each Mule application of the credentials required to access the backend systems?

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

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 load the properties at startup by invoking that credentials service

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

NO.59 When using Anypoint Platform across various lines of business with their own Anypoint Platform business groups, what configuration of Anypoint Platform is always performed at the organization level as opposed to at the business group level?

Environment setup

Identity management setup

Role and permission setup

Dedicated Load Balancer setup

NO.60 Refer to the exhibit.

A Mule application is deployed to a cluster of two customer-hosted Mute runtimes. The Mute application has a flow that polls a database and another flow with an HTTP Listener.
HTTP clients send HTTP requests directly to individual cluster nodes.
What happens to database polling and HTTP request handling in the time after the primary (master) node of the cluster has railed, but before that node is restarted?

Database polling continues Only HTTP requests sent to the remaining node continue to be accepted

Database polling stops All HTTP requests continue to be accepted

Database polling continues All HTTP requests continue to be accepted, but requests to the failed node Incur increased latency

Database polling stops All HTTP requests are rejected

NO.61 A Mule application is being designed to do the following:
Step 1: Read a SalesOrder message from a JMS queue, where each SalesOrder consists of a header and a list of SalesOrderLineltems.
Step 2: Insert the SalesOrder header and each SalesOrderLineltem into different tables in an RDBMS.
Step 3: Insert the SalesOrder header and the sum of the prices of all its SalesOrderLineltems into a table In a different RDBMS.
No SalesOrder message can be lost and the consistency of all SalesOrder-related information in both RDBMSs must be ensured at all times.
What design choice (including choice of transactions) and order of steps addresses these requirements?

1. Read the JMS message (NOT in an XA transaction)
2. Perform BOTH DB inserts in ONE DB transaction
3. Acknowledge the JMS message

1- Read the JMS message (NOT in an XA transaction)
2. Perform EACH DB insert in a SEPARATE DB transaction
3. Acknowledge the JMS message

1. Read the JMS message in an XA transaction
2. In the SAME XA transaction, perform BOTH DB inserts but do NOT acknowledge the JMS message

1. Read and acknowledge the JMS message (NOT in an XA transaction)
2. In a NEW XA transaction, perform BOTH DB inserts

NO.62 A Mule application uses the Database connector.
What condition can the Mule application automatically adjust to or recover from without needing to restart or redeploy the Mule application?

One of the stored procedures being called by the Mule application has been renamed

The database server was unavailable for four hours due to a major outage but is now fully operational again

The credentials for accessing the database have been updated and the previous credentials are no longer valid

The database server has been updated and hence the database driver library/JAR needs a minor version upgrade

NO.63 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?

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

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

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

Search Anypoint Exchange for a suitable existing fallback API and them implement invocations to their fallback API in addition to the Order API