Cloud Kicks stores historical customer transaction data inside Snowflake.

Zero Copy Data Federation is the correct architectural approach because it allows Tableau Next and Data 360 to work with Snowflake-hosted data without creating a separate duplicated dataset. The Snowflake tables remain in the source platform while the federation layer exposes them for governed analytical use. This directly addresses both storage-cost concerns and the compliance risk associated with maintaining synchronized copies.

Option B would move the data into Salesforce custom objects through an integration flow, which creates another persisted copy and increases synchronization and governance overhead. Option C also creates replicated data through scheduled batch processing and therefore violates the stated requirement to avoid duplication. Zero-copy access keeps the source system authoritative while making the dataset available for semantic modeling and Tableau Next analysis.

The important architecture pattern is federation rather than extraction: connect Snowflake, expose the required federated data objects, apply the necessary governance, and then build the Tableau Next semantic layer over those objects. This minimizes data movement while preserving analytical accessibility.

References/Topics: Data Setup - > Data 360 - > Snowflake - > Zero Copy Data Federation - > Tableau Next.

===========================================================================