This is an extension of the primary viewpoint which describes a link between the layers. This trace viewpoint is relevant in the situation where the model is used to generate program code based on classes and tables. In that situation you would like to have lookups and a trace between the logical and physical data modeling.

Data object is an ArchiMate concept that on the one hand can be linked to a number of ArchiMate concepts so that aspects such as quality, requirements. But also where is the dataset used and by whom, which application has a relation with this dataset etc. If necessary, you could link to the infrastructure from the data object. At this moment, this is not yet chosen in this example. As soon as there is a need in the community for this, this will be worked out further

The physical table is an implementation within a relational database and is linked via a trace to the logical data model. Physical tables are converted to table structures in (relational databases). That is why columns and associations are worked out for these tables. Multiple types of constraints or rules can be added to the tables, columns and associations. Think of primary and foreign keys, check constraints and the like.