DEA-C02 · Question #129
A Data Engineer created table t1 and applied a projection policy, my_proj_policy to several columns: What effect will the policy have on columns account_number and account_type? (Choose three.)
The correct answer is C. These columns cannot pass an argument to an external function or external stored procedure. D. The data in these columns will not be included in query results. F. The columns cannot be used in a WHERE clause. A projection policy in Snowflake completely restricts a column from being exposed in query output - it goes beyond masking by preventing the column from appearing in results at all. D is correct because the entire purpose of a projection policy is to block columns from being…
Question
A Data Engineer created table t1 and applied a projection policy, my_proj_policy to several columns:
What effect will the policy have on columns account_number and account_type? (Choose three.)
Exhibit
Options
- AThe columns cannot be used to insert data into another table.
- BThe columns will be masked and will only be visible to a defined user role.
- CThese columns cannot pass an argument to an external function or external stored procedure.
- DThe data in these columns will not be included in query results.
- ETags can now be placed on these columns.
- FThe columns cannot be used in a WHERE clause.
How the community answered
(31 responses)- A6% (2)
- B3% (1)
- C81% (25)
- E10% (3)
Explanation
A projection policy in Snowflake completely restricts a column from being exposed in query output - it goes beyond masking by preventing the column from appearing in results at all. D is correct because the entire purpose of a projection policy is to block columns from being projected (returned) in query results. F is correct because allowing a column in a WHERE clause would let users infer its values through filtering, circumventing the protection. C is correct because passing the column as an argument to an external function or stored procedure would similarly leak the data outside Snowflake's control.
The distractors fail for these reasons: B describes a masking policy, not a projection policy - masking shows obfuscated values to certain roles, while projection suppresses the column entirely. A is wrong because projection policies control reading, not writing - INSERT operations are unaffected. E is wrong because tags are independent metadata objects that can be applied to any column regardless of policy status; a projection policy neither grants nor blocks tagging.
Memory tip: Think of "projection" as what appears on a projector screen - a projection policy turns the screen off entirely for that column. If it's off, you can't see it (D), filter by it (F), or sneak it out through an external call (C). Masking dims the screen; projection cuts the power.
Topics
Community Discussion
No community discussion yet for this question.
