Assuming every Snowflake account uses Enterprise edition or higher, in which development and testing scenarios is data copying required, making zero-copy cloning unsuitable?
Choose two A Developers create their own datasets to work against transformed versions of the live data. B Production and development run in different databases in the same account, and Developers need to see production-like data but with specific columns masked. C Data is in a production Snowflake account that needs to be provided to Developers in a separate development/testing Snowflake account in the same cloud region. D Developers create their own copies of a standard test database previously created for them in the development account, for their initial development and unit testing. E The release process requires pre-production testing of changes with data of production scale and complexity. For security reasons, pre-production also runs in the production account. Show Answer Answer Explanation Zero-copy clones initially share the source table’s micro-partitions and represent an unchanged point-in-time copy; creating a dataset with transformed live data requires materializing the transformed results. Cloning is also not a cross-account writable-copy mechanism. Secure Data Sharing between accounts transfers no data but provides imported objects as read-only, so developers who need a writable dataset in a separate account need data to be copied or otherwise materialized there.
Learn more
Community Discussion