The ORGADMIN role in Snowflake is an organizational-level role that provides administrative capabilities across the entire organization, rather than being limited to a single Snowflake account. Users with this role can:
* A. Create an account for an organization: The ORGADMIN role has the privilege to create new Snowflake accounts within the organization, allowing for the expansion and management of the organization's resources.
* D. View usage information for all accounts in an organization: This role also has access to comprehensive usage and activity data across all accounts within the organization. This is crucial for monitoring, cost management, and optimization at the organizational level.
References:
* Snowflake Documentation: Understanding Role-Based Access Control

Operations that do not require compute resources are typically those that can leverage previously cached results. However, if no queries have been executed previously, all the given operations would require compute to execute. It's important to note that certain operations like DDL statements and queries that hit the result cache do not consume compute credits2.

When a Snowflake user wants to share a newly created object in a database with consumers, the correct action to take is to use theGRANTprivilege ... TO SHARE command to grant the necessary privileges for the object to be shared. This approach allows the object owner or a user with the appropriate privileges to share database objects such as tables, secure views, and streams with other Snowflake accounts by granting access to a named share.
TheGRANTstatement specifies which privileges are granted on the object to the share. The object remains in its original location; sharing does not duplicate or move the object. Instead, it allows the specified share to access the object according to the granted privileges.
For example, to share a table, the command would be:
GRANTSELECTONTABLEnew_tableTOSHARE consumer_share;
This command grants the SELECT privilege on a table namednew_tableto a share namedconsumer_share, enabling the consumers of the share to query the table.
Automatic sharing, dropping and re-adding the object, or recreating the object with a different name are not required or recommended practices for sharing objects in Snowflake. The use of theGRANTstatement to a share is the direct and intended method for this purpose.
Reference: Snowflake Documentation on Sharing Data (https://docs.snowflake.com/en/user-guide/data- sharing-intro.html)

Dynamic data masking is a feature in Snowflake that allows administrators to define masking policies to protect sensitive data. It enables partial visibility of the data to certain roles, such as functional managers, while hiding it from others, like end users

When deciding to use a secure view, several considerations come into play, especially concerning security and performance:
A).No details of the query execution plan will be available in the query profiler: Secure views are designed to prevent the exposure of the underlying data and the view definition to unauthorized users. Because of this, the detailed execution plans for queries against secure views are not available in the query profiler. This is intended to protect sensitive data from being inferred through the execution plan.
C).Secure views do not take advantage of the same internal optimizations as standard views: Secure views, by their nature, limit some of the optimizations that can be applied compared to standard views. This is because they enforce row-level security and mask data, which can introduce additional processing overhead and limit the optimizer's ability to apply certain efficiencies that are available to standard views.
B).Once created, there is no way to determine if a view is secure or notis incorrect because metadata about whether a view is secure can be retrieved from the INFORMATION_SCHEMA views or by using theSHOW VIEWScommand.
D).It is not possible to create secure materialized viewsis incorrect because the limitation is not on the security of the view but on the fact that Snowflake currently does not support materialized views with the same dynamic data masking and row-level security features as secure views.
E).The view definition of a secure view is still visible to users by way of the information schemais incorrect because secure views specifically hide the view definition from users who do not have the privilege to view it, ensuring that sensitive information in the definition is not exposed.
Reference: Snowflake Documentation on Secure Views (https://docs.snowflake.com/en/user-guide/views- secure.html)