|Exam Name||:||MuleSoft Certified Integration Architect - Level 1|
|Questions and Answers||:||58 Q & A|
|Updated On||:||Click to Check Update|
|PDF Download Mirror||:||MCIA-Level-1 Brain Dump|
|Get Full Version||:||Pass4sure MCIA-Level-1 Full Version|
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?
No special code or configuration is included in the Experience API and Process API implementations to generate and manage the correlation ID
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
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
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 SalesOrderLineItem 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?
Perform EACH DB insert in a SEPARATE DB transaction
Acknowledge the JMS message
2. In a NEW XA transaction, perform BOTH DB inserts
2. In the SAME XA transaction, perform BOTH DB inserts but do NOT acknowledge the JMS message
Perform BOTH DB inserts in ONE DB transaction
Acknowledge the JMS message
Refer to the exhibit. A Mule application is being designed to be deployed to several CloudHub workers. The Mule applicationâ€™s integration logic is to replicate changed Accounts from Salesforce to a backend system every 5 minutes.
A watermark will be used to only retrieve those Salesforce 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?
An organization is designing an integration solution to replicate financial transaction data from a legacy system into a data warehouse (DWH).
The DWH must contain a daily snapshot of financial transactions, to be delivered as a CSV file. Daily transaction volume exceeds tens of millions of records, with significant spikes in volume during popular shopping periods.
What is the most appropriate integration style for an integration solution that meets the organizationâ€™s current requirements?
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?
Anypoint Exchange is required to maintain the source code of some of the assets committed to it, such as Connectors, Templates, and API specifications.
What is the best way to use an organizationâ€™s source-code management (SCM) system in this context?
A global organization operates datacenters in many countries. There are private network links between these datacenters because all business data (but NOT metadata) must be exchanged over these private network connections.
The organization does not currently use AWS in any way.
The strategic decision has just been made to rigorously minimize IT operations effort and investment going forward.
What combination of deployment options of the Anypoint Platform control plane and runtime plane(s) best serves this organization at the start of this strategic journey?
Customer-hosted runtime plane in multiple AWS regions
Customer-hosted runtime plane in each datacenter