Snowflake Exam ARA-R01 Topic 3 Question 31 Discussion

Actual exam question for Snowflake's ARA-R01 exam

Question #: 31
Topic #: 3

An Architect needs to grant a group of ORDER_ADMIN users the ability to clean old data in an ORDERS table (deleting all records older than 5 years), without granting any privileges on the table. The group's manager (ORDER_MANAGER) has full DELETE privileges on the table.

How can the ORDER_ADMIN role be enabled to perform this data cleanup, without needing the DELETE privilege held by the ORDER_MANAGER role?

ACreate a stored procedure that runs with caller's rights, including the appropriate '> 5 years' business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

BCreate a stored procedure that can be run using both caller's and owner's rights (allowing the user to specify which rights are used during execution), and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

CCreate a stored procedure that runs with owner's rights, including the appropriate '> 5 years' business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

DThis scenario would actually not be possible in Snowflake -- any user performing a DELETE on a table requires the DELETE privilege to be granted to the role they are using.

Show Suggested Answer

Suggested Answer: C

This is the correct answer because it allows the ORDER_ADMIN role to perform the data cleanup without needing the DELETE privilege on the ORDERS table. A stored procedure is a feature that allows scheduling and executing SQL statements or stored procedures in Snowflake. A stored procedure can run with either the caller's rights or the owner's rights. A caller's rights stored procedure runs with the privileges of the role that called the stored procedure, while an owner's rights stored procedure runs with the privileges of the role that created the stored procedure. By creating a stored procedure that runs with owner's rights, the ORDER_MANAGER role can delegate the specific task of deleting old data to the ORDER_ADMIN role, without granting the ORDER_ADMIN role more general privileges on the ORDERS table. The stored procedure must include the appropriate business logic to delete only the records older than 5 years, and the ORDER_MANAGER role must grant the USAGE privilege on the stored procedure to the ORDER_ADMIN role.The ORDER_ADMIN role can then execute the stored procedure to perform the data cleanup12.

Snowflake Documentation: Stored Procedures

Snowflake Documentation: Understanding Caller's Rights and Owner's Rights Stored Procedures

by Renay at Apr 04, 2025, 02:38 AM

Limited Time Offer

25%

Off

Get Premium ARA-R01 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Mertie

2 days ago

I think option C sounds familiar because it mentions running with owner's rights, which might be necessary to perform the DELETE operation.

upvoted 0 times

...

Daren

8 days ago

I remember we discussed stored procedures in class, but I'm not sure if they should run with caller's rights or owner's rights for this scenario.

upvoted 0 times

...

Krystina

13 days ago

Hmm, Option D is interesting. If it's truly not possible to achieve this in Snowflake, I'll need to make a note of that and explain my reasoning in the exam. I'll double-check the documentation to be sure.

upvoted 0 times

...

Lai

19 days ago

I think Option B might be the way to go. Allowing the user to specify the rights they want to use during execution could be a good solution. I'll need to make sure I understand how that would work in practice.

upvoted 0 times

...

Emerson

24 days ago

I'm a bit confused by the wording of the question. Does the ORDER_MANAGER role really need to own the stored procedure, or can the Architect create it and grant the necessary permissions? I'll need to review the details more closely.

upvoted 0 times

...

Tequila

30 days ago

Okay, let's see. I think the key here is to find a way to give the ORDER_ADMIN users the ability to clean up the old data without directly granting them the DELETE privilege. Option A sounds promising, but I'll need to double-check the details.

upvoted 0 times

...

Pamella

1 month ago

Hmm, this is a tricky one. I'll need to think carefully about the different options and how they might work in the exam setting.

upvoted 0 times

...

Nancey

6 months ago

Wait, is the ORDER_MANAGER role allowed to own the procedure in the first place? Seems like a potential security risk. I'd go with option B to be on the safe side.

upvoted 0 times

...

Emiko

6 months ago

Haha, D is a classic 'this is not possible' answer. At least the question is giving us a real-world scenario to work with.

upvoted 0 times

Donte

4 months ago

Haha, D is a classic 'this is not possible' answer. At least the question is giving us a real-world scenario to work with.

upvoted 0 times

...

Nada

5 months ago

B) Create a stored procedure that can be run using both caller's and owner's rights (allowing the user to specify which rights are used during execution), and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

upvoted 0 times

...

Ressie

5 months ago

A) Create a stored procedure that runs with caller's rights, including the appropriate '> 5 years' business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

upvoted 0 times

...

Shelba

6 months ago

Ah, I see. Option A looks like it would work too, but having the ORDER_MANAGER own the procedure is a bit sketchy. I don't know, I'm torn between B and C.

upvoted 0 times

Junita

5 months ago

Yeah, I see your point. Option B does provide more flexibility. Let's go with that.

upvoted 0 times

...

Kimberlie

5 months ago

I agree, but having ORDER_MANAGER own the procedure does seem a bit risky. Option B gives more control over rights during execution.

upvoted 0 times

...

Sherell

6 months ago

I think Option A is the best choice. It allows ORDER_ADMIN to clean old data without needing DELETE privilege.

upvoted 0 times

...

Louisa

7 months ago

I think option C is the way to go. Keeping the business logic in the stored procedure and running it with the owner's rights is a cleaner approach.

upvoted 0 times

Arletta

5 months ago

True, but having the business logic centralized in the stored procedure, as in option C, can also help maintain consistency.

upvoted 0 times

...

Reyes

5 months ago

That's a good point. Having that flexibility could be useful in certain situations.

upvoted 0 times

...

German

5 months ago

But wouldn't it be better to have the flexibility of choosing between caller's and owner's rights, like in option B?

upvoted 0 times

...

Lillian

5 months ago

I agree, option C seems like the most secure way to handle this.

upvoted 0 times

...

Effie

5 months ago

True, it's important to consider both security and organization when granting permissions.

upvoted 0 times

...

Carisa

6 months ago

That's a good point, but I think having the business logic in the stored procedure itself, like in option C, is more organized.

upvoted 0 times

...

Naomi

6 months ago

But wouldn't it be better to have the flexibility of choosing rights during execution, like in option B?

upvoted 0 times

...

Selene

6 months ago

I agree, option C seems like the most secure way to handle this.

upvoted 0 times

...

Rose

7 months ago

I'm not sure about option A. Maybe we should consider option B as well, since it allows the user to specify rights during execution.

upvoted 0 times

...

Apolonia

7 months ago

I agree with Nikita. Option A seems like the most secure and efficient solution for this scenario.

upvoted 0 times

...

Oretha

7 months ago

Hmm, option B seems like the best choice here. Giving the ORDER_ADMIN users the ability to choose which rights to use during execution is a pretty neat solution.

upvoted 0 times