In a Foundry data model, what elements define cross-dataset relationships?

• A. Dashboards and visualizations.
• B. Storage location and file format.
• C. Keys and relationships/joins.
• D. User roles and permissions.

Answer: (C)

Cross-dataset relationships in a Foundry data model are defined by keys and the way datasets are joined. Keys act as identifiers that connect records across datasets—for example, a product_id in an orders dataset linking to the same product_id in a products dataset. Those keys establish the logical link between datasets. The actual relationship or join specification specifies how the data should be combined, including the type of join and any constraints, so that data from multiple sources can be fused correctly in queries and pipelines. This combination enables coherent data fusion, lineage, and governance across datasets. Dashboards and visualizations simply present data and do not establish how datasets relate. Storage location and file format concern where and how data is stored, not how it connects across datasets. User roles and permissions govern access, not inter-dataset relationships.