SnowPro Advanced: Architect — Question 148

A company has a single Snowflake account for both its production and non-production environments. An Architect needs to design a solution defining the different database layers with a process that also includes a periodic data refresh from production to non-production with data governance in place to protect columns that contain sensitive data.

How should the layers be configured, and what process should be followed?

Answer options

• A. Database layers: RAW->Presentation->Integration Schedule tasks that share the identified tables using data sharing from production to non-production. Define Dynamic Data Masking on columns with sensitive data in the production environment, based on the defined roles.
• B. Database layers: RAW->Presentation->Integration Schedule tasks that clone the identified tables from production to non-production. Define Dynamic Data Masking on the columns that have sensitive data in the production environment, based on the defined roles.
• C. Database layers: RAW->Integration->Presentation Schedule tasks that clone the identified tables from production to non-production. Define Dynamic Data Masking on columns that have sensitive data in the production environment, based on the defined roles.
• D. Database layers: RAW->Integration->Presentation Schedule tasks that clone the identified tables from production to non-production. Define row access policies on the columns that have sensitive data in the production environment, based on the defined roles.

Correct answer: C

Explanation

The correct answer is C because it correctly identifies the database layer sequence as RAW->Integration->Presentation and uses the cloning method for data refresh, which is suitable for non-production environments. Option A is incorrect due to the wrong layer sequence and data sharing method, while B has the correct sequence but incorrectly uses the Presentation layer. Option D uses row access policies, which are less suitable than Dynamic Data Masking for the described requirement.