Which object, when it has Historization enabled, controls the Historian to which its hosted objects will historize?

The correct choice is the Engine, which plays a crucial role in the configuration and management of data collection within the AVEVA Historian environment. When historization is enabled on an Engine, it establishes the framework for data ingestion and storage, determining how objects hosted on that Engine, such as tags or data points, will be historized.

The Engine effectively acts as a central point of control, dictating the parameters and rules for how data is gathered from the various sources and subsequently stored in the Historian database. This includes managing data retention policies, compression methods, and ensuring that the historization process adheres to the specified configurations.

In contrast, while the other options like Data Source, Tag Manager, and Database Connector are integral to the overall functioning of the Historian, they do not directly control the historization process at the same level as the Engine itself. Data Sources refer to where the data is coming from, Tag Manager manages the life cycle of the tags, and Database Connectors facilitate connections between the Historian and external databases but do not set the foundation for historization.