What is a feature of a stored procedure in Snowflake?
What is a feature of a stored procedure in Snowflake?
A feature of a stored procedure in Snowflake is that they can be created to run with a caller's rights or an owner's rights. This allows for flexibility in determining the level of access and permissions the stored procedure has when being executed, based on either the privileges of the user who calls the procedure or the owner of the procedure itself.
https://docs.snowflake.com/en/sql-reference/stored-procedures-rights.html
I think that the "Correct Answers" are designed to fail hahaha. D is the correct.
answer is D
A. They can be created as secure and hide the underlying metadata from all users.
The answer is D. They can be created to run with a caller's rights or an owner's rights. Stored procedures in Snowflake can be created to run with either the caller's rights or the owner's rights. This allows you to control the level of access that users have to the data and resources that are used in the stored procedure.
A is wrong secured stored procedures only hide certain aspects like code handlers etc, but unauthorized users can still see parameters
Answer is D , I am not sure about A. For example, for a secure function or procedure, information omitted for unauthorized users includes its: Body (the handler code that comprises its logic) List of imports Handler name Packages list Unauthorized users will still be able to see information that includes its: Parameter types Return type Handler language Null handling Volatility https://docs.snowflake.com/en/developer-guide/secure-udf-procedure#label-secure-limiting-visibility-definition But D is definitely true A stored procedure runs with either the caller’s rights or the owner’s rights. It cannot run with both at the same time. This topic describes the differences between a caller’s rights stored procedure and an owner’s rights stored procedure. https://docs.snowflake.com/en/developer-guide/stored-procedure/stored-procedures-rights
A - https://docs.snowflake.com/en/developer-guide/stored-procedure/stored-procedures-overview
A and D https://docs.snowflake.com/developer-guide/stored-procedure/stored-procedures-overview and https://docs.snowflake.com/developer-guide/secure-udf-procedure
https://docs.snowflake.com/en/sql-reference/stored-procedures-overview#what-is-a-stored-procedure
D is correct...https://docs.snowflake.com/en/sql-reference/stored-procedures-rights
A - False - When you specify that the UDF or procedure is secure, these details are visible only to authorized users – in other words, to users who are granted a role that owns the function.
Invokers and caller rights
Stored procs can be created to be secure https://docs.snowflake.com/en/developer-guide/secure-udf-procedure.html#determining-if-a-udf-or-procedure-is-secure
but can't hide the underlying metadata from all users. Here "all" users is the catch. The role that created can view the definition of stored proc
According to documentation is D.
should be D
Should be D
Caller's Owner's is correct . Secured option is good for views, Materialized views.