Can public features and consumers reside in different applications?

Public features and consumers can indeed reside in different applications, which is why the answer is considered correct. In OutSystems, features that are made public can be consumed by other applications, allowing for modular and reusable components. This design promotes a clear separation of concerns and encourages developers to share functionalities across multiple applications, leading to more efficient development and easier maintenance.

This capability is fundamental to the OutSystems architecture, where applications can leverage shared logic or components that exist independently. This not only enhances collaboration between developers but also allows for a streamlined approach to application management. By facilitating such interactions across applications, OutSystems enables developers to integrate and utilize various features without being confined to the boundaries of a single application.

The other choices would limit the structure and flexibility offered by OutSystems’ framework and do not reflect the platform's support for modular application design.