What does Snowflake recommend as a best practice for using secure views?

The correct answer is D. Do not expose the sequence-generated column(s). Snowflake recommends that secure views should NOT expose sequence-generated columns. Sequence-generated values (auto-incremented IDs) can inadvertently leak information about the underlying table - such as row count, insertion order, or data volume - to consumers of the view…

Data Protection and Data Sharing

Question

Options

AUse sequence-gen era ted values
BProgrammatically reveal the identifiers.
CUse secure views solely for query convenience.
DDo not expose the sequence-generated column(s)

How the community answered

(36 responses)

B
3% (1)
C
6% (2)
D
92% (33)

Explanation

Snowflake recommends that secure views should NOT expose sequence-generated columns. Sequence-generated values (auto-incremented IDs) can inadvertently leak information about the underlying table - such as row count, insertion order, or data volume - to consumers of the view. Since the primary purpose of a secure view is to restrict access to sensitive data and hide the underlying query logic, exposing sequence-generated columns defeats that purpose. Best practice is to omit or mask those columns in the view definition.

Topics

#Secure Views#Security Best Practices#Data Protection#Identifier Protection

Community Discussion

No community discussion yet for this question.

Full COF-C02 Practice