ARA-C01 · Question #141
An Architect has chosen to separate their Snowflake Production and QA environments using two separate Snowflake accounts. The QA account is intended to run and test changes on data and database…
The correct answer is C. 1) Enable replication for each database in the Production account. Snowflake Database Replication is purpose-built for replicating entire databases-including all objects (tables, views, schemas), data, and object-level grants/privileges-across accounts on a scheduled basis. Enabling replication and creating a secondary database in the QA…
Question
An Architect has chosen to separate their Snowflake Production and QA environments using two separate Snowflake accounts. The QA account is intended to run and test changes on data and database objects before pushing those changes to the Production account. It is a requirement that all database objects and data in the QA account need to be an exact copy of the database objects, including privileges and data in the Production account on at least a nightly basis. Which is the LEAST complex approach to use to populate the QA account with the Production account's data and database objects on a nightly basis?
Options
- A
- Create a share in the Production account for each database
- B
- Create a stage in the Production account
- C
- Enable replication for each database in the Production account
- D
- In the Production account, create an external function that connects into the QA account and
How the community answered
(27 responses)- A4% (1)
- B11% (3)
- C81% (22)
- D4% (1)
Explanation
Snowflake Database Replication is purpose-built for replicating entire databases-including all objects (tables, views, schemas), data, and object-level grants/privileges-across accounts on a scheduled basis. Enabling replication and creating a secondary database in the QA account is a straightforward, managed process requiring minimal custom code or orchestration. Option A (data sharing) does not copy data or replicate object structures/privileges; consumers get a live read-only view. Option B (staging and COPY INTO) requires custom ETL scripts and cannot replicate privileges. Option D (external functions) is highly complex custom development and not a standard replication mechanism.
Topics
Community Discussion
No community discussion yet for this question.