What are the three layers in API-led connectivity?

• A. System APIs, Process APIs, Experience APIs
• B. Data APIs, Integration APIs, Presentation APIs
• C. System APIs, Data APIs, Experience APIs
• D. Core APIs, Business APIs, User APIs

Answer: (A)

The model being tested is API-led connectivity, which organizes APIs into three layers: System APIs, Process APIs, and Experience APIs. System APIs expose backend systems in a standardized way, hiding the details and handling system-specific concerns. Process APIs sit between them, orchestrating and shaping data from one or more System APIs, applying business logic and data transformations to present a clean, consistent interface. Experience APIs are tailored for a specific channel or consumer (such as a mobile app or partner portal) and consume Process APIs to deliver the right data and operations in the right format for that experience.

This separation enables reuse and governance: backend changes stay contained if the System API surface remains stable, Process APIs can orchestrate across multiple systems, and Experience APIs can be updated for a channel without impacting the underlying layers. The other groupings don’t reflect this canonical three-layer structure, so they don’t capture how API-led connectivity organizes concerns across backend, orchestration, and consumer-facing surfaces.