MCPA - Level 1: MuleSoft Certified Platform Architect - Level 1 Apis Practice Questions

A company has created a successful enterprise data model (EDM). The company is committed to building an application network by adopting modern APIs as a core enabler of the company's IT operating model. At what API tiers (experience, process, system) should the company require reusing the EDM when designing modern API data models?

• AA. At the experience and process tiers
• BB. At the experience and system tiers
• CC. At the process and system tiers
• DD. At the experience, process, and system tiers

Refer to the exhibit. Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications. These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?

• AA. Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities
• BB. Build distinct data models for each API to follow established micro-services and Agile API-centric practices
• CC. Build all API data models using XML schema to drive consistency and reuse across the organization
• DD. Build one centralized Canonical Data Model (Enterprise Data Model) that unifies all the data types from all three business processes, ensuring the data model is consistent and non-redundant
• EE. Option A
• FF. Option B
• GG. Option C
• HH. Option D

Correct answer: A

Explanation

Correct Answer Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities. ***************************************** >> The options w.r.t building API data models using XML schema/ Agile API-centric practices are irrelevant to the scenario given in the question. So these two are INVALID. >> Building EDM (Enterprise Data Model) is not feasible or right fit for this scenario as the teams and LOBs work in silo and they all have different initiatives, budget etc.. Building EDM needs intensive coordination among all the team which evidently seems not possible in this scenario. So, the right fit for this scenario is to build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities.

Was this answer correct?