Data CloudAdvancedzero-copysnowflakefederationcost
Evaluate Zero Copy vs copy-based ingestion for Snowflake
Real World Scenario
Enterprise data warehouse team prefers Zero Copy federation to avoid duplicating 50TB of customer data into Data Cloud storage.
Expected Answer
• Zero Copy reduces storage duplication and sync lag for warehouse-authoritative datasets
• Query performance depends on federation latency—may not suit high-frequency segment refresh
• Copy-based ingestion better for high-volume activation and offline processing patterns
• Hybrid: Zero Copy for exploratory CI development, materialized copies for production segments
• Security: evaluate row-level access policies propagating from Snowflake
• Cost model differs: federation query costs vs Data Cloud credit consumption
• Disaster recovery: understand dependency if Snowflake unavailable during activation
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Zero Copy reduces storage duplication and sync lag for warehouse-authoritative datasets Also consider: Query performance depends on federation latency—may not suit high-frequency segment refresh In practice: Copy-based ingestion better for high-volume activation and offline processing patterns Optimize for scale and operational observability.
Architect Perspective
Zero Copy is not free performance—architects benchmark segment refresh with federation before committing marketing SLAs.