SnowPro Associate: Platform Question 98
Single answer● DatabasesA retail company stores production data in the database PROD_DB. Analysts need a safe way to test new transformation logic against a recent copy of production data without affecting live objects, while minimizing both storage costs and time to provision the environment. Which Snowflake approach best meets these requirements?
- A
Create a clone of PROD_DB for the analysts' test environment
- B
Create a data share of PROD_DB for the analysts and let them modify shared tables
- C
Export PROD_DB to stage files and reload it into a new database for testing
- D
Replicate PROD_DB into another database in the same account for development use
Show answer and explanation
Correct answer: A
Explanation
The best answer is to create a clone of PROD_DB. Snowflake zero-copy cloning supports databases, schemas, and tables, and is a common best practice for creating development, testing, and QA environments from production data. It is near-instant because Snowflake copies metadata pointers rather than physically duplicating all data at creation time. Storage usage increases only as changes are made, due to copy-on-write behavior. By contrast, Secure Data Sharing provides read-only access, unloading/reloading data is unnecessarily expensive and slow, and replication is aimed at business continuity and cross-region/cloud use cases rather than routine test environment provisioning. This aligns with Snowflake documentation on zero-copy cloning, database objects, and replication use cases.
- A. Correct.
Correct. Database cloning is designed for this scenario. A clone creates a point-in-time copy of the database metadata and uses Snowflake's copy-on-write storage model, so it is very fast to create and initially does not duplicate all underlying data storage. Analysts can work independently in the cloned database without affecting production objects. Additional storage is only consumed for changed or newly added micro-partitions after the clone is created.
- B. Incorrect.
Incorrect. Secure Data Sharing allows read-only access to shared database objects; consumers cannot directly modify the shared tables. This makes sharing useful for distribution and collaboration, but not for creating an isolated writable test environment where analysts need to change objects or transformation logic.
- C. Incorrect.
Incorrect. Exporting and reloading data would work functionally, but it is slower, more operationally complex, and typically more expensive than cloning. It also introduces unnecessary data movement and administrative overhead, which goes against the requirement to minimize provisioning time and storage cost.
- D. Incorrect.
Incorrect. Database replication is intended for cross-region or cross-cloud business continuity, disaster recovery, and data locality scenarios, not as the primary mechanism for quickly creating a low-cost writable development copy in the same account. It is heavier than cloning and does not best fit the stated requirement.