[Feb-2024] MuleSoft MCIA-Level-1 Dumps – Reduce Your Chance of Failure in MCIA-Level-1 Exam [Q145-Q166]

NO.145 A platform architect includes both an API gateway and a service mesh in the architect of a distributed application for communication management.
Which type of communication management does a service mesh typically perform in this architecture?

Between application services and the firewall

Between the application and external API clients

Between services within the application

Between the application and external API implementations.

NO.146 An integration Mule application is deployed to a customer-hosted multi-node Mule 4 runtime duster. The Mule application uses a Listener operation of a JMS connector to receive incoming messages from a JMS queue.
How are the messages consumed by the Mule application?

Depending on the JMS provider’s configuration, either all messages are consumed by ONLY the primary cluster node or else ALL messages are consumed by ALL cluster nodes

Regardless of the Listener operation configuration, all messages are consumed by ALL cluster nodes

Depending on the Listener operation configuration, either all messages are consumed by ONLY the primary cluster node or else EACH message is consumed by ANY ONE cluster node

Regardless of the Listener operation configuration, all messages are consumed by ONLY the primary cluster node

NO.147 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.148 According to MuleSoft, which deployment characteristic applies to a microservices application architecture?

Services exist as independent deployment artifacts and can be scaled -independently of other services

All services of an application can be deployed together as single Java WAR file

A deployment to enhance one capability requires a redeployment of all capabilities

Core business capabilities are encapsulated in a single, deployable application

NO.149 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.150 Refer to the exhibit.

A shopping cart checkout process consists of a web store backend sending a sequence of API invocations to an Experience API, which in turn invokes a Process API. All API invocations are over HTTPS POST. The Java web store backend executes in a Java EE application server, while all API implementations are Mule applications executing in a customer -hosted Mule runtime.
End-to-end correlation of all HTTP requests and responses belonging to each individual checkout Instance is required. This is to be done through a common correlation ID, so that all log entries written by the web store backend, Experience API implementation, and Process API implementation include the same correlation ID for all requests and responses belonging to the same checkout instance.
What is the most efficient way (using the least amount of custom coding or configuration) for the web store backend and the implementations of the Experience API and Process API to participate in end-to-end correlation of the API invocations for each checkout instance?
A)
The web store backend, being a Java EE application, automatically makes use of the thread-local correlation ID generated by the Java EE application server and automatically transmits that to the Experience API using HTTP-standard headers No special code or configuration is included in the web store backend, Experience API, and Process API implementations to generate and manage the correlation ID

B)
The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATlON-lt HTTP request header In each API invocation belonging to that checkout No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID

C)
The Experience API implementation generates a correlation ID for each incoming HTTP request and passes it to the web store backend in the HTTP response, which includes it in all subsequent API invocations to the Experience API.
The Experience API implementation must be coded to also propagate the correlation ID to the Process API in a suitable HTTP request header

D)
The web store backend sends a correlation ID value in the HTTP request body In the way required by the Experience API The Experience API and Process API implementations must be coded to receive the custom correlation ID In the HTTP requests and propagate It in suitable HTTP request headers

Option A

Option B

Option C

Option D

NO.151 What aspects of a CI/CD pipeline for Mule applications can be automated using MuleSoft-provided Maven plugins?

Import from API designer, compile, package, unit test, deploy, publish to Anypoint Exchange

Compile, package, unit test, validate unit test coverage, deploy

Compile, package, unit test, deploy, integration test

Compile, package, unit test, deploy, create associated API instances in API Manager

NO.152 Insurance organization is planning to deploy Mule application in MuleSoft Hosted runtime plane. As a part of requirement , application should be scalable . highly available. It also has regulatory requirement which demands logs to be retained for at least 2 years. As an Integration Architect what step you will recommend in order to achieve this?

It is not possible to store logs for 2 years in CloudHub deployment. External log management system is required.

When deploying an application to CloudHub , logs retention period should be selected as 2 years

When deploying an application to CloudHub, worker size should be sufficient to store 2 years data

Logging strategy should be configured accordingly in log4j file deployed with the application.

NO.153 When designing an upstream API and its implementation, the development team has been advised to not set timeouts when invoking downstream API. Because the downstream API has no SLA that can be relied upon. This is the only donwstream API dependency of that upstream API. Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

The invocation of the downstream API will run to completion without timing out.

An SLA for the upstream API CANNOT be provided.

A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes.

A load-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes.

NO.154 An organization is designing the following two Mule applications that must share data via a common persistent object store instance:
– Mule application P will be deployed within their on-premises datacenter.
– Mule application C will run on CloudHub in an Anypoint VPC.
The object store implementation used by CloudHub is the Anypoint Object Store v2 (OSv2).
what type of object store(s) should be used, and what design gives both Mule applications access to the same object store instance?

Application P uses the Object Store connector to access a persistent object store Application C accesses this persistent object store via the Object Store REST API through an IPsec tunnel

Application C and P both use the Object Store connector to access the Anypoint Object Store v2

Application C uses the Object Store connector to access a persistent object Application P accesses the persistent object store via the Object Store REST API

Application C and P both use the Object Store connector to access a persistent object store

NO.155 What is not true about Mule Domain Project?

This allows Mule applications to share resources

Expose multiple services within the Mule domain on the same port

Only available Anypoint Runtime Fabric

Send events (messages) to other Mule applications using VM queues

* 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

NO.156 Refer to the exhibit.
A Mule application is being designed to expose a SOAP web service to its clients.
What language is typically used inside the web service’s interface definition to define the data structures that the web service Is expected to exchange with its clients?

WSDL

XSD

JSON Schema

RAMI

NO.157 A rale limiting policy has been applied to a soap VI.2 API published in Clondhub. The API implementation catches errors in a global error handler on error propagate in the main flow for HTTP: RETRY_EXHAUSTED with HTTP status set to 429 and any with the HTTP status set to 500.
What is the expected H1TP status when the client exceeds the quota of the API calls?

HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API

HTTP status 500 as defined in the ANY error handler in the API since an API:RETRY_EXHAUSTED will be generated

HTTP status 401 unauthorized for policy violation

HTTP status 400 from the rate-limiting policy violation since the call does not reach the back-end

NO.158 An application deployed to a runtime fabric environment with two cluster replicas is designed to periodically trigger of flow for processing a high-volume set of records from the source system and synchronize with the SaaS system using the Batch job scope After processing 1000 records in a periodic synchronization of 1 lakh records, the replicas in which batch job instance was started went down due to unexpected failure in the runtime fabric environment What is the consequence of losing the replicas that run the Batch job instance?

The remaining 99000 records will be lost and left and processed

The second replicas will take over processing the remaining 99000 records

A new replacement replica will be available and will be process all 1,00,000 records from scratch leading to duplicate record processing

A new placement replica will be available and will take or processing the remaining 99,000 records

NO.159 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.160 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.161 Mule application A receives a request Anypoint MQ message REQU with a payload containing a variable-length list of request objects. Application A uses the For Each scope to split the list into individual objects and sends each object as a message to an Anypoint MQ queue.
Service S listens on that queue, processes each message independently of all other messages, and sends a response message to a response queue.
Application A listens on that response queue and must in turn create and publish a response Anypoint MQ message RESP with a payload containing the list of responses sent by service S in the same order as the request objects originally sent in REQU.
Assume successful response messages are returned by service S for all request messages.
What is required so that application A can ensure that the length and order of the list of objects in RESP and REQU match, while at the same time maximizing message throughput?

Use a Scatter-Gather within the For Each scope to ensure response message order Configure the Scatter-Gather with a persistent object store

Perform all communication involving service S synchronously from within the For Each scope, so objects in RESP are in the exact same order as request objects in REQU

Use an Async scope within the For Each scope and collect response messages in a second For Each scope in the order In which they arrive, then send RESP using this list of responses

Keep track of the list length and all object indices in REQU, both in the For Each scope and in all communication involving service Use persistent storage when creating RESP

NO.162 An auto mobile company want to share inventory updates with dealers Dl and D2 asynchronously and concurrently via queues Q1 and Q2. Dealer Dl must consume the message from the queue Q1 and dealer D2 to must consume a message from the queue Q2.
Dealer D1 has implemented a retry mechanism to reprocess the transaction in case of any errors while processing the inventers updates. Dealer D2 has not implemented any retry mechanism.
How should the dealers acknowledge the message to avoid message loss and minimize impact on the current implementation?

Dealer D1 must use auto acknowledgement and dealer D2 can use manual acknowledgement and acknowledge the message after successful processing

Dealer D1 can use auto acknowledgement and dealer D2 can use IMMEDIATE acknowledgement and acknowledge the message of successful processing

Dealer D1 and dealer D2 must use AUTO acknowledgement and acknowledge the message after successful processing

Dealer D1 can use AUTO acknowledgement and dealer D2 must use manual acknowledgement and acknowledge the message

NO.163 In preparation for a digital transformation initiative, an organization is reviewing related IT integration projects that failed for various for reason.
According to MuleSoft’s surveys of global IT leaders, what is a common cause of IT project failure that this organization may likely discover in its assessment?

Following an Agile delivery methodology

Reliance on an Integration-Platform-as-a-Service (iPaaS)

Spending too much time on enablement

Lack of alignment around business outcomes

NO.164 An external web UI application currently accepts occasional HTTP requests from client web browsers to change (insert, update, or delete) inventory pricing information in an inventory system’s database. Each inventory pricing change must be transformed and then synchronized with multiple customer experience systems in near real-time (in under 10 seconds). New customer experience systems are expected to be added in the future.
The database is used heavily and limits the number of SELECT queries that can be made to the database to 10 requests per hour per user.
What is the most scalable, idiomatic (used for its intended purpose), decoupled. reusable, and maintainable integration mechanism available to synchronize each inventory pricing change with the various customer experience systems in near real-time?

Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the watermark attribute set to an appropriate database column In the same now, use a Scatter-Gather to call each customer experience system’s REST API with transformed inventory-pricing records

Add a trigger to the inventory-pricing database table so that for each change to the inventory pricing database, a stored procedure is called that makes a REST call to a Mule application Write the Mule application to publish each Mule event as a message to an Anypoint MQ exchange Write other Mule applications to subscribe to the Anypoint MQ exchange, transform each received message, and then update the Mule application’s corresponding customer experience system(s)

Replace the external web UI application with a Mule application to accept HTTP requests from client web browsers In the same Mule application, use a Batch Job scope to test if the database request will succeed, aggregate pricing changes within a short time window, and then update both the inventory pricing database and each customer experience system using a Parallel For Each scope

Write a Mule application with a Database On Table Row event source configured for the inventory pricing database, with the ID attribute set to an appropriate database column In the same flow, use a Batch Job scope to publish transformed Inventory-pricing records to an Anypoint MQ queue Write other Mule applications to subscribe to the Anypoint MQ queue, transform each received message, and then update the Mule application’s corresponding customer experience system(s)

NO.165 What is an advantage of using OAuth 2.0 client credentials and access tokens over only API keys for API authentication?

If the access token is compromised, the client credentials do not to be reissued.

If the access token is compromised, I can be exchanged for an API key.

If the client ID is compromised, it can be exchanged for an API key

If the client secret is compromised, the client credentials do not have to be reissued.

NO.166 A team would like to create a project skeleton that developers can use as a starting point when creating API Implementations with Anypoint Studio. This skeleton should help drive consistent use of best practices within the team.
What type of Anypoint Exchange artifact(s) should be added to Anypoint Exchange to publish the project skeleton?

A custom asset with the default API implementation

A RAML archetype and reusable trait definitions to be reused across API implementations

An example of an API implementation following best practices

a Mule application template with the key components and minimal integration logic

Exam Practice Questions

[Feb-2024] MuleSoft MCIA-Level-1 Dumps – Reduce Your Chance of Failure in MCIA-Level-1 Exam [Q145-Q166]

Leave a Reply Cancel reply

Related Posts

[2022] New MCIA-Level-1 exam dumps Use Updated MuleSoft Exam [Q47-Q69]

Pass Your Exam With 100% Verified MCD-Level-2 Exam Questions [Q21-Q42]

Leave a Reply Cancel reply