Which of the following describes a "System API" in API-led architecture?

In API-led architecture, a "System API" is designed to interact directly with underlying systems and data sources. This type of API serves as a bridge between the external world and the core systems of record, such as databases or legacy systems. By doing so, System APIs enable access to essential data and facilitate operations that are tied to those core systems, ensuring that other APIs, like Process or Experience APIs, can leverage this data without directly interacting with the systems of record themselves.

This architecture promotes separation of concerns; while the System API handles the complexities and peculiarities of the underlying data storage and systems, other APIs can focus on exposing business logic or presenting user interfaces, thus streamlining application development and ensuring better maintainability. Using a System API enhances security as it abstracts direct access to databases and key business resources, reducing the risk of data breaches or corruption.

The choices related to external applications and core business logic refer to APIs that serve different roles. APIs connecting to external applications typically engage with third-party systems or services, while APIs that expose core business logic allow for reusability across different channels and require a higher level of abstraction from the underlying data. In contrast, APIs that provide a user interface are concerned with how users interact with applications and are not