The correct answer is C. A role with the OWNERSHIP privilege on the database . A database role is scoped to a specific database. To create a database role, a role must have sufficient privileges on the database where the database role will be created. Why C is correct: The role that owns the database has control over that database and can create database roles within it. Example: CREATE DATABASE ROLE my_database.my_db_role; To run this successfully, the executing role must have the required privilege on the database, such as OWNERSHIP. Why the other options are incorrect: A). SECURITYADMIN manages users, roles, and grants at the account level, but database role creation depends on privileges on the specific database. B). A custom role being granted to SECURITYADMIN does not automatically mean it can create database roles in a database. D). SYSADMIN commonly owns many account objects by default in recommended role models, but the required condition is privilege on the database, not simply holding the SYSADMIN role. Official Snowflake documentation reference: Snowflake documentation explains that database roles are created inside databases and require appropriate privileges on the database. Reference: Snowflake Documentation - Database roles; CREATE DATABASE ROLE; Access control privileges; SnowPro Core Study Guide - Security and Access Control. ==
Question 182
Which command should be used to load data from a local computer into Snowflake?
Correct Answer: B
Question 183
What metrics will the show tables command in Snowsight provide?
Correct Answer: B
Question 184
What is the purpose of the use of the VALIDATE command?
Correct Answer: D
The VALIDATE command in Snowflake is used to check for errors that occurred during the execution of a COPY INTO <table> statement. This command helps users identify and resolve data loading issues. Run the COPY INTO Statement: Execute the COPY INTO <table> command to load data from a stage into a table. COPY INTO my_table FROM @my_stage FILE_FORMAT = (FORMAT_NAME = 'my_format'); Validate the Load: Use the VALIDATE function to see if there were any errors during the data load. SELECT * FROM TABLE(VALIDATE(my_table, JOB_ID => 'my_copy_job_id')); Review Errors: The VALIDATE function will return details about any errors that occurred, such as parsing errors or data type mismatches. References: Snowflake Documentation: Validating Data Loads Snowflake Documentation: COPY INTO <table>
Question 185
What information is stored in the ACCESS_HlSTORY view?
Correct Answer: D
Details around the privileges that have been granted for all objects in an account. TheACCESS_HISTORYview in Snowflake provides a comprehensive log of access control changes, including grants and revocations of privileges on all securable objects within the account. This information is crucial for auditing and monitoring the security posture of your Snowflake environment. Here ' s how to understand and use theACCESS_HISTORYview: Purpose of ACCESS_HISTORY View:It is designed to track changes in access controls, such as when a user or role is granted or revoked privileges on various Snowflake objects. This includes tables, schemas, databases, and more. Querying ACCESS_HISTORY:To access this view, you can use the following SQL query pattern: SELECT*FROMSNOWFLAKE.ACCOUNT_USAGE.ACCESS_HISTORYWHEREEVENT_TYPE = ' GRANT ' OREVENT_TYPE = ' REVOKE ' ; Interpreting the Results:The results from theACCESS_HISTORYview include the object type, the specific privilege granted or revoked, the grantee (who received or lost the privilege), and the timestamp of the event. This data is invaluable for audits and compliance checks. Reference:For detailed information on theACCESS_HISTORYview and how to interpret its data, please visit the official Snowflake documentation: https://docs.snowflake.com/en/sql-reference/account-usage /access_history.html
