Question 650
Consider this Snowflake situation: A cloud migration team needs to copy a large database for test workloads without physically duplicating all storage at creation. Which platform behavior BEST explains the appropriate solution?
Explanation
Correct Answer
The decisive Snowflake behavior is: Zero-copy cloning uses shared underlying micro-partition references initially, with later changes driving divergence. It supports the response: Use a supported zero-copy database clone and verify relevant role and object behaviors. Confirm it with this observable result: A new clone appears with correct initial rows and its incremental storage changes are visible after test updates. Distinguish this mechanism from superficially related Snowflake features.
Incorrect Answers
Fail-safe is not ordinary user-queryable historical data access and has a different recovery process. That explanation applies to a different technical failure. Here the controlling principle is: Zero-copy cloning uses shared underlying micro-partition references initially, with later changes driving divergence.
The offered statement is true for this other mechanism: Reader accounts enable supported share consumption for organizations that do not operate their own Snowflake accounts. It does not explain the facts described here, which follow from: Zero-copy cloning uses shared underlying micro-partition references initially, with later changes driving divergence.
This principle describes a separate cause: Secure Data Sharing permits governed read access to provider-managed shared objects without copying the underlying table data. The reported condition is governed by: Zero-copy cloning uses shared underlying micro-partition references initially, with later changes driving divergence. The two mechanisms should not be conflated.