An Architect on a new project has been asked to design an architecture that meets Snowflake security, compliance, and governance requirements as follows: 1) Use Tri-Secret Secure in Snowflake 2)…

Question

Options

• ADefine row access policies.
• BUse the Business-Critical edition of Snowflake.
• CCreate a secure view.
• DUse the Enterprise edition of Snowflake.
• EUse Dynamic Data Masking.
• FCreate a materialized view.

• A
  2% (1)
• B
  77% (34)
• D
  7% (3)
• F
  14% (6)

Explanation

Each requirement maps to a specific Snowflake feature and edition. Tri-Secret Secure, which allows customers to use their own encryption keys in combination with Snowflake-managed and cloud provider keys, is exclusively available in the Business-Critical edition - making Option B mandatory and Option D (Enterprise) insufficient. Sharing data via a view with another Snowflake customer requires a Secure View (Option C), because regular views expose the underlying query plan and data structure to the recipient account; secure views prevent that. Hiding portions of sensitive column data (partial masking, e.g., showing only last 4 digits of a credit card) is handled by Dynamic Data Masking (Option E), which applies masking policies at query time based on the user's role. Row access policies (Option A) control which rows a user sees, not which parts of a column value, so they do not satisfy requirement 3. Materialized views (Option F) improve query performance but are not a security or governance mechanism.

No community discussion yet for this question.