A Snowflake Architect is designing a multi-tenant application strategy for an organization in the Snowflake Data Cloud and is considering using an Account Per Tenant strategy.
Which requirements will be addressed with this approach? (Choose two.)
The Account Per Tenant strategy involves creating separate Snowflake accounts for each tenant within the multi-tenant application. This approach offers a number of advantages.
Option B: With separate accounts, each tenant's environment is isolated, making security and RBAC policies simpler to configure and maintain. This is because each account can have its own set of roles and privileges without the risk of cross-tenant access or the complexity of maintaining a highly granular permission model within a shared environment.
Option D: This approach also allows for each tenant to have a unique data shape, meaning that the database schema can be tailored to the specific needs of each tenant without affecting others. This can be essential when tenants have different data models, usage patterns, or application customizations.
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?
A new user user_01 is created within Snowflake. The following two commands are executed:
Command 1-> show grants to user user_01;
Command 2 ~> show grants on user user 01;
What inferences can be made about these commands?
Therefore, the correct inference is that command 1 defines all the grants which are given to user_01, and command 2 defines which role owns user_01.
What Snowflake system functions are used to view and or monitor the clustering metadata for a table? (Select TWO).
The Snowflake system functions used to view and monitor the clustering metadata for a table are:
SYSTEM$CLUSTERING_INFORMATION
SYSTEM$CLUSTERING_DEPTH
Comprehensive But Short Explanation:
The SYSTEM$CLUSTERING_INFORMATION function in Snowflake returns a variety of clustering information for a specified table. This information includes the average clustering depth, total number of micro-partitions, total constant partition count, average overlaps, average depth, and a partition depth histogram. This function allows you to specify either one or multiple columns for which the clustering information is returned, and it returns this data in JSON format.
The SYSTEM$CLUSTERING_DEPTH function computes the average depth of a table based on specified columns or the clustering key defined for the table. A lower average depth indicates that the table is better clustered with respect to the specified columns. This function also allows specifying columns to calculate the depth, and the values need to be enclosed in single quotes.
SYSTEM$CLUSTERING_INFORMATION: Snowflake Documentation
SYSTEM$CLUSTERING_DEPTH: Snowflake Documentation
Jamie
10 hours agoSylvia
12 days agoJoseph
1 months agoMicheline
2 months agoJani
2 months agoMalinda
2 months agoErinn
2 months agoMari
3 months agoMozelle
3 months agoDeangelo
3 months agoSamira
4 months agoTy
4 months agoSheldon
4 months agoMinna
4 months agoTawna
4 months agoMerilyn
5 months agoKimbery
5 months agoVonda
5 months agoGlory
5 months agoDalene
5 months agoEliz
6 months agoSherly
6 months agoCarman
6 months agoHortencia
6 months agoJamie
7 months agoAlverta
7 months agoRory
7 months agoBev
7 months agoErasmo
7 months agoPrincess
8 months agoAnnamae
8 months agoFernanda
8 months agoGalen
9 months agoGlenn
10 months agoBernardine
10 months agoAshley
10 months agoLeoma
11 months agoJerry
11 months agoHerminia
11 months agoEarlean
12 months agoBrianne
1 years ago