COF-C02 · Question #574
How does the Access_History view enhance overall data governance pertaining to read and write operations? (Select TWO).
The correct answer is B. Provides a unified picture of what data was accessed and when it was accessed E. Determines whether a given row in a table can be accessed by the user by filtering the data based. The ACCESS_HISTORY view in Snowflake is a powerful tool for enhancing data governance, especially concerning monitoring and auditing data access patterns for both read and write operations. The key ways in which ACCESS_HISTORY enhances overall data governance are: B . Provides…
Question
How does the Access_History view enhance overall data governance pertaining to read and write operations? (Select TWO).
Options
- AShows how the accessed data was moved from the source lo the target objects
- BProvides a unified picture of what data was accessed and when it was accessed
- CProtects sensitive data from unauthorized access while allowing authorized users to access it at
- DIdentifies columns with personal information and tags them so masking policies can be applied to
- EDetermines whether a given row in a table can be accessed by the user by filtering the data based
How the community answered
(39 responses)- A3% (1)
- B90% (35)
- C5% (2)
- D3% (1)
Explanation
The ACCESS_HISTORY view in Snowflake is a powerful tool for enhancing data governance, especially concerning monitoring and auditing data access patterns for both read and write operations. The key ways in which ACCESS_HISTORY enhances overall data governance are: B . Provides a unified picture of what data was accessed and when it was accessed: This view logs details about query executions, including the objects (tables, views) accessed and the timestamps of these accesses. It's instrumental in auditing and compliance scenarios, where understanding the access patterns to sensitive data is critical. E . Determines whether a given row in a table can be accessed by the user by filtering the data based on a given policy: While this option is a bit of a misinterpretation of what ACCESS_HISTORY directly offers, it indirectly supports data governance by providing the information necessary to analyze access patterns. This analysis can then inform policy decisions, such as implementing Row-Level Security (RLS) to restrict access to specific rows based on user roles or attributes. ACCESS_HISTORY does not automatically apply data masking or tag columns with personal information. However, the insights derived from analyzing ACCESS_HISTORY can be used to identify sensitive data and inform the application of masking policies or other security measures.
Topics
Community Discussion
No community discussion yet for this question.