When should a stored procedure be created with caller's rights?

The correct answer is C. When the stored procedure needs to run with the privileges of the role that called the stored. Stored procedures in Snowflake can be created with either 'owner's rights' or 'caller's rights'. A stored procedure created with caller's rights executes with the privileges of the role that calls the procedure, not the privileges of the role that owns the procedure. This is…

Account Access and Security

Question

Options

AWhen the caller needs to be prevented from viewing the source code of the stored procedure
BWhen the caller needs to run a statement that could not execute outside of the stored procedure
CWhen the stored procedure needs to run with the privileges of the role that called the stored
DWhen the stored procedure needs to operate on objects that the caller does not have privileges on

How the community answered

(23 responses)

A
4% (1)
B
4% (1)
C
91% (21)

Explanation

Stored procedures in Snowflake can be created with either 'owner's rights' or 'caller's rights'. A stored procedure created with caller's rights executes with the privileges of the role that calls the procedure, not the privileges of the role that owns the procedure. This is particularly useful in scenarios where the procedure needs to perform operations that depend on the caller's access permissions, ensuring that the procedure can only access objects that the caller is authorized to

Topics

#Stored Procedures#Caller's Rights#Execution Privileges#Security Context

Community Discussion

No community discussion yet for this question.

Full COF-C02 Practice