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

Loading demo links...

Showing 1–3 of 14 questions

Question 1

As part of a growth strategy, a supplier signs a trading agreement with a large customer. The customer sends purchase orders to the supplier according to the ANSI X12 EDI standard, and the supplier creates the orders in its ERP system using the information in the EDI document.

The agreement also requires that the supplier provide a new RESTful API to process request from the customer for current product inventory level from the supplier’ s ERP system.

Which two fundamental integration use cases does the supplier need to deliver to provide an end-to-end solution for this business scenario? (Choose two.)

Select all that apply, then click Submit answer.

  • Synchronized data transfer

  • Sharing data with external partners

  • User interface integration

  • Streaming data ingestion

  • Data mashups

Question 2

As an enterprise architect, what are the two reasons for which you would use a canonical data model in the new integration project using Mulesoft Anypoint platform ( choose two answers )

Select all that apply, then click Submit answer.

  • To have consistent data structure aligned in processes

  • To isolate areas within a bounded context

  • To incorporate industry standard data formats

  • There are multiple canonical definitions of each data type

  • Because the model isolates the back and systems and support mule applications from change

Question 3

An organization is building a test suite for their applications using m-unit. The integration architect has recommended using test recorder in studio to record the processing flows and then configure unit tests based on the capture events

What are the two considerations that must be kept in mind while using test recorder

(Choose two answers)

Select all that apply, then click Submit answer.

  • Tests for flows cannot be created with Mule errors raised inside
    the flow or already existing in the incoming event

  • Recorder supports smoking a message before or inside a ForEach processor

  • The recorder support loops where the structure of the data been tested
    changes inside the iteration

  • A recorded flow execution ends successfully but the result does
    not reach its destination because the application is killed

  • Mocking values resulting from parallel processes are possible and will not affect the execution of the processes that follow in the test