MCIA-Level-1 Dumps MCIA-Level-1 Braindumps

MCIA-Level-1 Real Questions MCIA-Level-1 Practice Test MCIA-Level-1 Actual Questions


Mulesoft


MCIA-Level-1


MuleSoft Certified Integration Architect - Level 1


https://killexams.com/pass4sure/exam-detail/MCIA-Level-1

Question: 52


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?

  • 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 APIThe Experience API implementation must be coded to also propagate the correlation ID to the Process API in a suitable HTTP request header


  • The web store backend generates a new correlation ID value at the start of checkout and sets it on the X-CORRELATION-ID 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


  • 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-standardheaders

    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 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


    Answer: B


    Question: 53


    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?

    1. 1. Read the JMS message (NOT in an XA transaction)

      1. Perform EACH DB insert in a SEPARATE DB transaction

      2. Acknowledge the JMS message

    2. 1. Read and acknowledge the JMS message (NOT in an XA transaction)

      2. In a NEW XA transaction, perform BOTH DB inserts

    3. 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

    4. 1. Read the JMS message (NOT in an XA transaction)

    1. Perform BOTH DB inserts in ONE DB transaction

    2. Acknowledge the JMS message


    Answer: C


    Question: 54


    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?

  • Persistent Object Store

  • Persistent Cache Scope

  • Persistent Anypoint MQ Queue

  • Persistent VM Queue


    • Answer: A


    Question: 55


    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?

    1. API-led connectivity

    2. Batch-triggered ETL

    3. Event-driven architecture

    4. Microservice architecture


    Answer: D


    Question: 56


    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?

    1. 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 oftechnical depth

    2. 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

    3. 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

    4. 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


    Question: 57


    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?

    1. 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

    2. Organizations need to use Anypoint Exchange as the main SCM system to centralize versioning and avoid code duplication

    3. 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

    4. 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


    Question: 58


    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?

    1. MuleSoft-hosted Anypoint Platform control planeCloudHub Shared Worker Cloud in multiple AWS regions

    2. MuleSoft-hosted Anypoint Platform control plane

      Customer-hosted runtime plane in multiple AWS regions

    3. MuleSoft-hosted Anypoint Platform control planeCustomer-hosted runtime plane in each datacenter

    4. Anypoint Platform – Private Cloud Edition

    Customer-hosted runtime plane in each datacenter


    Answer: B