Mulesoft MCIA - Level 1 - MuleSoft Certified Integration Architect - Level 1 Exam

Page:    1 / 21   
Total 101 questions

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?

  • A. MuleSoft-hosted Anypoint Platform control plane CloudHub Shared Worker Cloud in multiple AWS regions
  • B. MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in multiple AWS regions
  • C. MuleSoft-hosted Anypoint Platform control plane Customer-hosted runtime plane in each datacenter
  • D. Anypoint Platform - Private Cloud Edition Customer-hosted runtime plane in each datacenter


Answer : B

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. Organizations need to point Anypoint Exchange to their SCM system so Anypoint Exchange can pull source code when requested by developers and provide it to Anypoint Studio
  • B. Organizations need to use Anypoint Exchange as the main SCM system to centralize versioning and avoid code duplication
  • C. Organizations can continue to use an SCM system of their choice for branching and merging, as long as they follow the branching and merging strategy enforced by Anypoint Exchange
  • D. Organizations should continue to use an SCM system of their choice, in addition to keeping source code for these asset types in Anypoint Exchange, thereby enabling parallel development, branching, and merging


Answer : B

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. API-led connectivity
  • B. Batch-triggered ETL
  • C. Event-driven architecture
  • D. Microservice architecture


Answer : D

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?

  • A. 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
  • B. 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
  • C. 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
  • D. Use Anypoint Exchange to register the various Mule applications and APIs and share the RAML definitions with the stakeholders, so they can be discovered


Answer : D

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?

  • A. 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
  • B. 1. Read and acknowledge the JMS message (NOT in an XA transaction) 2. In a NEW XA transaction, perform BOTH DB inserts
  • C. 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
  • D. 1. Read the JMS message (NOT in an XA transaction) 2. Perform BOTH DB inserts in ONE DB transaction 3. Acknowledge the JMS message


Answer : C

Page:    1 / 21   
Total 101 questions