What MuleSoft API-led connectivity layer is intended to expose part of a backend database without business logic?

The correct choice is the System layer, which is designed to expose backend systems or databases in a way that allows other applications to access raw data without any business logic applied. This layer typically acts as a facade for existing databases and systems, effectively ensuring that data can be queried or read from multiple sources while maintaining the integrity of the backend systems.

The System layer often provides a simplified view of the underlying data by operating at a lower level. It is focused on integration and connectivity, enabling data access for further processing and manipulation. By exposing data in its raw form, it allows for flexibility in how that data is used without enforcing how applications interact with it at a higher level of abstraction.

In contrast, other layers such as the Experience layer are focused on tailoring the API to specific client needs and may incorporate business logic to provide a user-friendly interface or format relevant to the end user. The Process layer typically handles business logic, creating workflows or orchestrating data processing, while the Data layer unifies and transforms data from various sources to suit specific analytical or business purposes. Each of these layers serves a unique function within the overall API-led connectivity strategy, but the System layer's primary intention is to facilitate direct access to database information.