What is typically NOT a function of the APIs created within the framework called API-led connectivity?

APIs created within the API-led connectivity framework are designed to abstract and decouple systems, not to act as a fully resilient substitute for them. While patterns like caching and circuit breakers can be implemented within an API to handle transient backend failures, an API cannot fundamentally insulate a client from an extended outage of the underlying system it depends on for data. The API's primary function is to provide a well-defined contract and access point, but it remains dependent on the availability of the source system for its core data processing capabilities.

B. This is a primary function of Experience APIs. They abstract backend complexity, allowing front-end developers to innovate and build new user experiences without needing to understand the source systems.

C. This is the core purpose of System APIs. They unlock data from backend systems and expose it in a modern, reusable format, thereby reducing direct, tight-coupled dependencies on those systems.

D. This accurately describes the role of Process APIs. They orchestrate business processes by composing data and functionality from various System APIs to create new, higher-level services.

1. MuleSoft Documentation, "What is API-led Connectivity?": This document outlines the three-tiered approach. It states that System APIs "unlock data from systems," Process APIs "compose data into processes," and Experience APIs "reconfigure data for consumption." This directly supports the validity of options B, C, and D as core functions. The document does not claim that this architecture provides full insulation from extended backend failures.

2. MuleSoft Documentation, "Designing for Reliability": This section discusses reliability patterns. While it covers handling failures gracefully (e.g., with a circuit breaker), the patterns are designed to prevent cascading failures and manage transient issues. They do not enable an API to function independently during a prolonged outage of its backend data source, which confirms that option A is not a function of the framework. The API is a consumer of the backend system, and its reliability is inherently linked to the backend's reliability.

3. MuleSoft Whitepaper, "The API-led Connectivity Imperative": This paper emphasizes how API-led connectivity "unlocks the value of existing systems" and "enables the composition of new capabilities." It focuses on agility, reuse, and decoupling. The concept of providing a resilient layer that insulates from extended failure is not presented as a primary function; rather, the focus is on abstracting complexity and managing dependencies. (Reference: Page 4, "The Three Layers of API-led Connectivity").