Assuming all Snowflake accounts are using an Enterprise edition or higher, in which development and testing scenarios would be copying of data be required, and zero-copy cloning not be suitable?…

Question

Options

• ADevelopers create their own datasets to work against transformed versions of the live data.
• BProduction and development run in different databases in the same account, and Developers need
• CData is in a production Snowflake account that needs to be provided to Developers in a separate
• DDevelopers create their own copies of a standard test database previously created for them in the
• EThe release process requires pre-production testing of changes with data of production scale and

• A
  91% (20)
• B
  5% (1)
• E
  5% (1)

Explanation

Zero-copy cloning in Snowflake creates a metadata-level snapshot of an object (table, schema, database) within the same Snowflake account - it does not physically duplicate data and cannot cross account boundaries or produce transformed copies. Option A requires it: developers need 'transformed versions' of live data, not a raw clone - you must extract, transform, and load (copy) the data into a new structure. Option C requires it: the data resides in a production account and must be provided to developers in a separate account - zero-copy cloning cannot span accounts, so an actual data copy (e.g., via data sharing export, COPY INTO, or replication) is needed. Options B and D describe scenarios within the same account where zero-copy cloning works perfectly. Option E could be handled by cloning the production database for pre-production scale testing.

No community discussion yet for this question.