In the API-led connectivity approach, APIs are categorized into Experience, Process, and System layers:
* Enterprise Data Model Scope:
* The Enterprise Data Model (EDM) generally supports System APIs and some Process APIs by defining standard data structures used across the organization. Experience APIs, however, are tailored to specific applications or interfaces and are less likely to be served directly by the EDM, as they may require customized data representations to meet the unique needs of each user interface.
* Why Option C is Correct:
* The Mobile Account Management EAPI serves mobile-specific needs and often requires data formatted differently from the standardized data models. Thus, it would be outside the direct scope of the EDM and might employ custom mappings to fit mobile application requirements.
* Explanation of Incorrect Options:
* Option A (Customer SAPI), Option B (Customer Lookup PAPI), and Option D (Service SAPI) would typically align with the EDM as they are closer to the core data and services the EDM supports.
ReferencesFor additional guidance, review MuleSoft's best practices on API-led connectivity and data modeling.