SnowPro Advanced: Architect — Question 191
A company is migrating to Snowflake. Production and non-production data cannot be in the same account.
Which account design and lifecycle management plan will meet this requirement?
Answer options
- A. 1. Create one Snowflake account. 2. Use Dynamic Data Masking and row access policies in a Production environment for performance and cost optimization. 3. Create three databases, Development, Test, and Production. 4. Use one role and one warehouse for all three databases for efficient warehouse caching.
- B. 1. Create two Snowflake accounts, Production and Non-Production. 2. Use the Non-Production account for development and testing. 3. When development is complete clone the databases for testing and execute workloads on top of the cloned data within the Non-Production account. 4. When testing is complete push the code to the Production account using version control.
- C. 1. Create three Snowflake accounts, Production, Test, and Development. 2. When development is complete, clone the data from the Development account to the Test account. 3. When testing is complete push the code and data to the Production account, using version control.
- D. 1. Create three Snowflake accounts, Production, Test, and Development. 2. When development is complete, unload the data from the Development account and load all the data into the Test account using the COPY INTO command. 3. When testing is complete unload the data from the Test account and load it into the Production account using the COPY INTO command.
Correct answer: B
Explanation
The correct answer is B because it appropriately separates production and non-production environments by utilizing two distinct Snowflake accounts, ensuring compliance with the requirement. Options A, C, and D do not maintain this separation, either by consolidating both environments into a single account or failing to adequately isolate the data and processes, which can lead to risks in data integrity and security.