A company has a team of data analysts who need read access to the SALES schema. The team also has a few analysts who need to create temporary tables for their analysis. What is the best role design?

Create a custom role for each analyst based on their specific needs.

Create a single role for all analysts with both read and create privileges.

Grant all analysts the ACCOUNTADMIN role and let them manage their own privileges.

Create two roles: ANALYST_READ with read access and ANALYST_TEMP with read and create temporary table privileges, and assign users to the appropriate role.

What is the primary goal of the least privilege principle in role-based access control?

To ensure all users have the same level of access for consistency.

To simplify administration by using a few broad roles.

To grant users only the privileges necessary to perform their job functions.

To provide maximum access to all users to increase productivity.

A new analyst joins the company. The analyst needs to query tables in the SALES schema but should not be able to create new tables or modify data. The SALES schema is owned by the SALES_ADMIN role. What is the most appropriate way to grant the analyst access?

Grant the analyst the SALES_ADMIN role.

Create a new role ANALYST_READ, grant it USAGE on the SALES schema and SELECT on the tables, and grant that role to the analyst.

Grant the analyst the ACCOUNTADMIN role temporarily.

Grant the analyst SELECT on the tables directly.

In Snowflake, when a role is granted to another role, what is the effect on privilege inheritance?

The granting role inherits all privileges of the granted role.

The granted role inherits all privileges of the granting role.

Both roles immediately share all privileges with each other.

Privileges are only inherited when the granted role is the parent in the hierarchy.

A role named DATA_OWNER owns a table. The security team wants to transfer ownership to a new role DATA_STEWARD. What is the correct command to transfer ownership?

GRANT ALL PRIVILEGES ON TABLE my_table TO ROLE DATA_STEWARD;

ALTER TABLE my_table SET OWNER = DATA_STEWARD;

GRANT OWNERSHIP ON TABLE my_table TO ROLE DATA_STEWARD;

Snowflake SnowPro Advanced:Security Engineer

Domain 2Objective 3

Manage Role-Based Access Control SNOWPRO-ADVANCED-SECURITY-ENGINEER Practice Questions (Page 1)

Part of the Identity and Access Management domain, which makes up ~24% of our current practice bank.

24questions here

5free pages

6concepts

Questions 1–5

1application · medium
A company has a team of data analysts who need read access to the SALES schema. The team also has a few analysts who need to create temporary tables for their analysis. What is the best role design?
Select an answer first
2foundation · easy
What is the primary goal of the least privilege principle in role-based access control?
Select an answer first
3application · medium
A new analyst joins the company. The analyst needs to query tables in the SALES schema but should not be able to create new tables or modify data. The SALES schema is owned by the SALES_ADMIN role. What is the most appropriate way to grant the analyst access?
Select an answer first
4foundation · easy
In Snowflake, when a role is granted to another role, what is the effect on privilege inheritance?
Select an answer first
5application · medium
A role named DATA_OWNER owns a table. The security team wants to transfer ownership to a new role DATA_STEWARD. What is the correct command to transfer ownership?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to SNOWPRO-ADVANCED-SECURITY-ENGINEER

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Snowflake. “SNOWPRO-ADVANCED-SECURITY-ENGINEER” is a trademark of its owner, used for identification only.