Discuss Snowflake ARA-R01 Exam Topic 3 Question 31

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.

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

Get Premium ARA-R01 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

44 comments · newest first

Annette 10 months ago

C makes sense, but I’m not convinced it’ll work as expected.

Shala 10 months ago

I think D is correct, can't delete without privileges!

Elroy 10 months ago

Option C seems like the best choice here.

Belen 10 months ago

Wait, are you sure this can be done without DELETE rights?

Daren 11 months ago

A is interesting, but I prefer B for flexibility.

Crista 11 months ago

I'm leaning towards option A, but I worry that running with caller's rights might not give ORDER_ADMIN the necessary permissions to delete records.

Fletcher 11 months ago

I feel like we practiced a similar question where we had to grant access without direct privileges, but I can't recall the exact details.

Mertie 11 months ago

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

Daren 11 months 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.

Krystina 12 months 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.

Lai 12 months 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.

Emerson 12 months 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.

Tequila 1 year 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.

Pamella 1 year 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.

Nancey 1 year 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.

Emiko 1 year 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.

Donte 1 year ago

↳ replying to Emiko

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

Nada 1 year ago

↳ replying to Emiko

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.

Ressie 1 year ago

↳ replying to Emiko

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.

Shelba 1 year 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.

Junita 1 year ago

↳ replying to Shelba

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

Kimberlie 1 year ago

↳ replying to Shelba

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

Sherell 1 year ago

↳ replying to Shelba

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

Louisa 1 year 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.

Arletta 1 year ago

↳ replying to Louisa

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

Reyes 1 year ago

↳ replying to Louisa

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

German 1 year ago

↳ replying to Louisa

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

Lillian 1 year ago

↳ replying to Louisa

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

Effie 1 year ago

↳ replying to Louisa

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

Carisa 1 year ago

↳ replying to Louisa

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

Naomi 1 year ago

↳ replying to Louisa

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

Selene 1 year ago

↳ replying to Louisa

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

Rose 1 year 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.

Apolonia 2 years ago

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

Oretha 2 years 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.

Santos 1 year ago

↳ replying to Oretha

I see your point. It's important to consider the level of control given to ORDER_ADMIN.

Alease 1 year ago

↳ replying to Oretha

True, but with option B, ORDER_ADMIN can have more control over the execution rights.

My 1 year ago

↳ replying to Oretha

But wouldn't option A also work since it grants USAGE on the procedure to ORDER_ADMIN?

Tuyet 1 year ago

↳ replying to Oretha

I agree, option B sounds flexible and secure.

Maryann 1 year ago

↳ replying to Oretha

I see your point. Having the ability to choose rights during execution can be beneficial in this case.

Amina 1 year ago

↳ replying to Oretha

True, option A could work as well, but option B gives more control to the ORDER_ADMIN users.

Kayleigh 1 year ago

↳ replying to Oretha

But wouldn't option A also work since it grants USAGE on the procedure to ORDER_ADMIN?

Michel 1 year ago

↳ replying to Oretha

I agree, option B sounds like a flexible solution for this scenario.

Nikita 2 years ago

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

Snowflake ARA-R01 Exam - Topic 3 Question 31 Discussion