Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Snowflake Exam ADA-C01 Topic 2 Question 37 Discussion

Actual exam question for Snowflake's ADA-C01 exam
Question #: 37
Topic #: 2
[All ADA-C01 Questions]

The following SQL command was executed:

Use role SECURITYADMIN;

Grant ownership

On future tables

In schema PROD. WORKING

To role PROD_WORKING_OWNER;

Grant role PROD_WORKING_OWNER to role SYSADMIN;

Use role ACCOUNTADMIN;

Create table PROD.WORKING.XYZ (value number) ;

Which role(s) can alter or drop table XYZ?

Show Suggested Answer Hide Answer
Suggested Answer: C

According to the GRANT OWNERSHIP documentation, the ownership privilege grants full control over the table and can only be held by one role at a time. However, the current owner can also grant the ownership privilege to another role, which transfers the ownership to the new role. In this case, the SECURITYADMIN role granted the ownership privilege on future tables in the PROD.WORKING schema to the PROD_WORKING_OWNER role. This means that any table created in that schema after the grant statement will be owned by the PROD_WORKING_OWNER role. Therefore, the PROD_WORKING_OWNER role can alter or drop table XYZ, which was created by the ACCOUNTADMIN role in the PROD.WORKING schema. Additionally, the ACCOUNTADMIN role can also alter or drop table XYZ, because it is the top-level role that has all privileges on all objects in the account. Furthermore, the SYSADMIN role can also alter or drop table XYZ, because it was granted the PROD_WORKING_OWNER role by the SECURITYADMIN role. The SYSADMIN role can activate the PROD_WORKING_OWNER role and inherit its privileges, including the ownership privilege on table XYZ. The SECURITYADMIN role cannot alter or drop table XYZ, because it does not have the ownership privilege on the table, nor does it have the PROD_WORKING_OWNER role.


Contribute your Thoughts:

Gerald
2 months ago
Haha, looks like we've got some security shenanigans going on here! I'm leaning towards option B, just to cover all the bases. You can never have too many admins, right?
upvoted 0 times
Lindsey
2 months ago
I think option B makes the most sense too. Better safe than sorry!
upvoted 0 times
...
Stacey
2 months ago
I agree, having multiple admins can help with security.
upvoted 0 times
...
...
Avery
3 months ago
I'm not sure, but I think D is the correct answer.
upvoted 0 times
...
Lawrence
3 months ago
I agree with Raylene, PROD_WORKING_OWNER, ACCOUNTADMIN, and SYSADMIN can alter or drop table XYZ.
upvoted 0 times
...
Ashlee
3 months ago
I think the answer is C. The PROD_WORKING_OWNER role was granted ownership on future tables in the PROD.WORKING schema, so it should be able to alter or drop the XYZ table.
upvoted 0 times
Royal
2 months ago
Yes, because the PROD_WORKING_OWNER role was granted ownership on future tables, they should be able to alter or drop the XYZ table.
upvoted 0 times
...
Barrett
3 months ago
But what about the SYSADMIN role? Can they also alter or drop the table?
upvoted 0 times
...
Hubert
3 months ago
I agree, C seems like the correct answer.
upvoted 0 times
...
...
Raylene
3 months ago
I think the answer is C.
upvoted 0 times
...

Save Cancel