The correct answer is A. Clone the table .
The most cost-efficient way to back up a Snowflake table is to use zero-copy cloning . A clone creates a copy of the table’s metadata without immediately duplicating the underlying micro-partitions.
Why A is correct:
When a table is cloned, Snowflake creates a new independent table object that initially shares the same micro-partitions as the source table. Because the underlying data is not copied at clone creation time, cloning is fast and storage-efficient.
This is why cloning is commonly used for backups, development, testing, and point-in-time snapshots.
Important concept:
At the instant a clone is created, the original table and cloned table share the same micro-partitions. The clone becomes independent after creation, and changes to either object do not modify the other object. Additional storage is used only when data changes occur.
Why the other options are incorrect:
B. Downloading table data to a stage creates additional data files and increases storage and operational overhead.
C. Sharing data with another account in another region is not the simplest or lowest-cost table backup method. Cross-region replication or sharing can involve additional costs.
D. A CTAS statement physically creates a new table from query results and can duplicate data storage, making it less storage-efficient than cloning.
Official Snowflake documentation reference:
Snowflake documentation explains that zero-copy cloning creates a copy of a database, schema, or table without duplicating the underlying storage at the time the clone is created.
[Reference: Snowflake Documentation — Zero-copy cloning; Snowflake Documentation — CREATE TABLE ... CLONE; SnowPro Core Study Guide — Snowflake Architecture and Data Protection., ==]
