A E C - no, use this instead: https://docs.snowflake.com/en/sql-reference/account-usage/network_policies B - I would probably use QUERY_HISTORY for that instead https://docs.snowflake.com/en/sql-reference/account-usage/query_history D - I would use this instead: ROW_ACCESS_POLICIES https://docs.snowflake.com/en/sql-reference/account-usage/row_access_policies

Specifies the DDL operation on a database, schema, table, view, and column. These operations also include statements that specify a row access policy on a table or view, a masking policy on a column, and tag updates (e.g. set a tag, change a tag value) on the object or column. USER_NAME column JSMITH

Access history in Snowflake provides the following benefits pertaining to read and write operations: Data discovery Discover unused data to determine whether

Who what when how

[ { "objectDomain": "Stage", "objectId": 1, "objectName": "JRAMCELESTE", "stageKind": "User" } ]

A is the right answer. Check the benefit section: https://docs.snowflake.com/en/user-guide/access-history#benefits

correct

Access History in Snowflake refers to when the user query reads column data and when the SQL statement performs a data write operation, such as INSERT, UPDATE, and DELETE along with variations of the COPY command, from the source data object to the target data object

ADE A: https://docs.snowflake.com/en/user-guide/access-history#label-access-history-benefits:~:text=Discover%20unused%20data%20to%20determine%20whether%20to%20archive%20or%20delete%20the%20data. D: https://docs.snowflake.com/en/user-guide/access-history#example-track-row-access-policy-references E: https://docs.snowflake.com/en/user-guide/access-history#examples-read-queries

Only A. They did not ask for two.Dont Confuse

AE looks correct

Benefits¶ Access history in Snowflake provides the following benefits pertaining to read and write operations: Data discovery Discover unused data to determine whether to archive or delete the data.

Verified

E: "Access History in Snowflake refers to when the user query reads column data and when the SQL statement performs a data write operation" C: "These records facilitate regulatory compliance auditing and provide insights on popular and frequently accessed tables and columns"

D: https://docs.snowflake.com/en/sql-reference/account-usage/access_history#:~:text=Specifies%20information%20about%20the%20enforced%20masking%20policy%20set%20on%20the%20column%20and%20the%20enforced%20row%20access%20policy%20set%20on%20the%20table%2C%20including%20policies%20set%20on%20intermediate%20objects%20or%20columns. E: https://docs.snowflake.com/en/sql-reference/account-usage/access_history#:~:text=The%20user%20who%20issued%20the%20query.

No mention of roles into the columns of the view into the user document

The benefits of using the ACCESS_HISTORY view in the Snowflake database include: Identification of who has read data Tracking of which roles have been used Highlighting of row access policy usage By using the ACCESS_HISTORY view, organizations can get a better understanding of who has access to what data within their Snowflake environment, and ensure that data is being accessed and used in an appropriate manner.