MCIA-Level-1-Maintenance MuleSoft Certified Integration Architect

MuleSoft Certified Integration Architect - Level 1 MAINTENANCE

Last Update 1 day ago Total Questions : 116

The MuleSoft Certified Integration Architect - Level 1 MAINTENANCE content is now fully updated, with all current exam questions added 1 day ago. Deciding to include MCIA-Level-1-Maintenance practice exam questions in your study plan goes far beyond basic test preparation.

You'll find that our MCIA-Level-1-Maintenance exam questions frequently feature detailed scenarios and practical problem-solving exercises that directly mirror industry challenges. Engaging with these MCIA-Level-1-Maintenance sample sets allows you to effectively manage your time and pace yourself, giving you the ability to finish any MuleSoft Certified Integration Architect - Level 1 MAINTENANCE practice test comfortably within the allotted time.

Question # 1

An organization is designing an integration Mule application to process orders by submitting them to a back-end system for offline processing. Each order will be received by the Mule application through an HTTPS POST and must be acknowledged immediately. Once acknowledged, the order will be submitted to a back-end system. Orders that cannot be successfully submitted due to rejections from the back-end system will need to be processed manually (outside the back-end system).

The Mule application will be deployed to a customer-hosted runtime and is able to use an existing ActiveMQ broker if needed. The ActiveMQ broker is located inside the organization’s firewall. The back-end system has a track record of unreliability due to both minor network connectivity issues and longer outages.

What idiomatic (used for their intended purposes) combination of Mule application components and ActiveMQ queues are required to ensure automatic submission of orders to the back-end system while supporting but minimizing manual order processing?

An Until Successful scope to call the back-end system

One or more ActiveMQ long-retry queues

One or more ActiveMQ dead-letter queues for manual processing

One or more On Error scopes to assist calling the back-end system

An Until Successful scope containing VM components for long retries

A persistent dead-letter VM queue configured in CloudHub

One or more On Error scopes to assist calling the back-end system

One or more ActiveMQ long-retry queues

A persistent dead-letter object store configured in the CloudHub Object Store service

A Batch Job scope to call the back-end system

An Until Successful scope containing Object Store components for long retries

A dead-letter object store configured in the Mule application

Question # 2

A customer wants to use the mapped diagnostic context (MDC) and logging variables to enrich its logging and improve tracking by providing more context in the logs.

The customer also wants to improve the throughput and lower the latency of message processing.

As an Mulesoft integration architect can you advise, what should the customer implement to meet these requirements?

Use synchronous logging and use pattern layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables

Useasync logger at the level greater than INFO and use pattern layout with [%MDC] in the log4j2,xml configuration file and then configure the logging variables

Useasync logger at the level equal to DEBUG orTRACEand use pattern

layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables

Use synchronous logging at the INFO DEBUG or Trace level and use pattern layout with [%MDC] in the log4j2.xml configuration file and then configure the logging variables

Question # 3

An automation engineer needs to write scripts to automate the steps of the API lifecycle, including steps to create, publish, deploy and manage APIs and their implementations in Anypoint Platform.

What Anypoint Platform feature can be used to automate the execution of all these actions in scripts in the easiest way without needing to directly invoke the Anypoint Platform REST APIs?

Automated Policies in API Manager

Runtime Manager agent

The Mule Maven Plugin

Anypoint CLI

Question # 4

A Mule application is being designed for deployment to a single CloudHub worker. The Mule application will have a flow that connects to a SaaS system to perform some operations each time the flow is invoked.

The SaaS system connector has operations that can be configured to request a short-lived token (fifteen minutes) that can be reused for subsequent connections within the fifteen minute time window. After the token expires, a new token must be requested and stored.

What is the most performant and idiomatic (used for its intended purpose) Anypoint Platform component or service to use to support persisting and reusing tokens in the Mule application to help speed up reconnecting the Mule application to the SaaS application?

Nonpersistent object store

Persistent object store

Variable

Database

Question # 5

An organization is migrating all its Mule applications to Runtime Fabric (RTF). None of the Mule applications use Mule domain projects.

Currently, all the Mule applications have been manually deployed to a server group among several customer hosted Mule runtimes.

Port conflicts between these Mule application deployments are currently managed by the DevOps team who carefully manage Mule application properties files.

When the Mule applications are migrated from the current customer-hosted server group to Runtime Fabric (RTF), fo the Mule applications need to be rewritten and what DevOps port configuration responsibilities change or stay the same?

Yes, the Mule applications Must be rewritten

DevOps No Longer needs to manage port conflicts between the Mule applications

Yes, the Mule applications Must be rewritten

DevOps Must Still Manage port conflicts.

NO, The Mule applications do NOT need to be rewritten

DevOps MUST STILL manage port conflicts

NO, the Mule applications do NO need to be rewritten

DevOps NO LONGER needs to manage port conflicts between the Mule applications.

Question # 6

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

Answer:

Explanation:

Explanation

* 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

Graphical user interface Description automatically generated

Question # 7

An insurance company has an existing API which is currently used by customers. API is deployed to customer hosted Mule runtime cluster. The load balancer that is used to access any APIs on the mule cluster is only configured to point to applications hosted on the server at port 443.

Mule application team of a company attempted to deploy a second API using port 443 but the application will not start and checking logs shows an error indicating the address is already in use.

Which steps must the organization take to resolve this error and allow customers to access both the API's?

Change the base path of the HTTP listener configuration in the second API to a different one from the first API

Set HTTP listener configuration in both API's to allow for connections from multiple ports

Move the HTTP listener configurations from the API's and package them in a mule domain project using port 443

Set the HTTP listener of the second API to use different port than the one used in the first API

Question # 8

A company is building an application network and has deployed four Mule APIs: one experience API, one process API, and two system APIs. The logs from all the APIs are aggregated in an external log aggregation tool. The company wants to trace messages that are exchanged between multiple API implementations. What is the most idiomatic (based on its intended use) identifier that should be used to implement Mule event tracing across the multiple API implementations?

Mule event ID

Mule correlation ID

Client's IP address

DataWeave UUID

Question # 9

How does timeout attribute help inform design decisions while using JMS connector listening for incoming messages in an extended architecture (XA) transaction?

After the timeout is exceeded, stale JMS consumer threads are destroyed and new threads are created

The timeout specifies the time allowed to pass between receiving JMS messages on the same JMS connection and then after the timeout new JMS connection is established

The time allowed to pass between committing the transaction and the completion of the mule flow and then after the timeout flow processing triggers an error

The timeout defines the time that is allowed to pass without the transaction ending explicitly and after the timeout expires, the transaction rolls back

Question # 10

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

after successful processing