An Architect has chosen to separate their Snowflake Production and QA environments using two separate Snowflake accounts.
The QA account is intended to run and test changes on data and database objects before pushing those changes to the Production account. It is a requirement that all database objects and data in the QA account need to be an exact copy of the database objects, including privileges and data in the Production account on at least a nightly basis.
Which is the LEAST complex approach to use to populate the QA account with the Production account's data and database objects on a nightly basis?
This approach is the least complex because it uses Snowflake's built-in replication feature to copy the data and database objects from the Production account to the QA account. Replication is a fast and efficient way to synchronize data across accounts, regions, and cloud platforms. It also preserves the privileges and metadata of the replicated objects. By creating clones of the replica databases, the QA account can run tests on the cloned data without affecting the original dat
a. Clones are also zero-copy, meaning they do not consume any additional storage space unless the data is modified. This approach does not require any external stages, tasks, Snowpipe, or external functions, which can add complexity and overhead to the data transfer process.
Introduction to Replication and Failover
Replicating Databases Across Multiple Accounts
Cloning Considerations
Which of the below commands will use warehouse credits?
Warehouse credits are used to pay for the processing time used by each virtual warehouse in Snowflake. A virtual warehouse is a cluster of compute resources that enables executing queries, loading data, and performing other DML operations.Warehouse credits are charged based on the number of virtual warehouses you use, how long they run, and their size1.
Among the commands listed in the question, the following ones will use warehouse credits:
SELECT MAX(FLAKE_ID) FROM SNOWFLAKE: This command will use warehouse credits because it is a query that requires a virtual warehouse to execute.The query will scan the SNOWFLAKE table and return the maximum value of the FLAKE_ID column2. Therefore, option B is correct.
SELECT COUNT(*) FROM SNOWFLAKE: This command will also use warehouse credits because it is a query that requires a virtual warehouse to execute.The query will scan the SNOWFLAKE table and return the number of rows in the table3. Therefore, option C is correct.
SELECT COUNT(FLAKE_ID) FROM SNOWFLAKE GROUP BY FLAKE_ID: This command will also use warehouse credits because it is a query that requires a virtual warehouse to execute.The query will scan the SNOWFLAKE table and return the number of rows for each distinct value of the FLAKE_ID column4. Therefore, option D is correct.
The command that will not use warehouse credits is:
SHOW TABLES LIKE 'SNOWFL%': This command will not use warehouse credits because it is a metadata operation that does not require a virtual warehouse to execute.The command will return the names of the tables that match the pattern 'SNOWFL%' in the current database and schema5. Therefore, option A is incorrect.
The data share exists between a data provider account and a data consumer account. Five tables from the provider account are being shared with the consumer account. The consumer role has been granted the imported privileges privilege.
What will happen to the consumer account if a new table (table_6) is added to the provider schema?
When a new table (table_6) is added to a schema in the provider's account that is part of a data share, the consumer will not automatically see the new table. The consumer will only be able to access the new table once the appropriate privileges are granted by the provider. The correct process, as outlined in option D, involves using the provider's ACCOUNTADMIN role to grant USAGE privileges on the database and schema, followed by SELECT privileges on the new table, specifically to the share that includes the consumer's database. This ensures that the consumer account can access the new table under the established data sharing setup. Reference:
Snowflake Documentation on Managing Access Control
Snowflake Documentation on Data Sharing
Based on the Snowflake object hierarchy, what securable objects belong directly to a Snowflake account? (Select THREE).
A securable object is an entity to which access can be granted in Snowflake.Securable objects include databases, schemas, tables, views, stages, pipes, functions, procedures, sequences, tasks, streams, roles, warehouses, and shares1.
The Snowflake object hierarchy is a logical structure that organizes the securable objects in a nested manner. The top-most container is the account, which contains all the databases, roles, and warehouses for the customer organization. Each database contains schemas, which in turn contain tables, views, stages, pipes, functions, procedures, sequences, tasks, and streams. Each role can be granted privileges on other roles or securable objects.Each warehouse can be used to execute queries on securable objects2.
Based on the Snowflake object hierarchy, the securable objects that belong directly to a Snowflake account are databases, roles, and warehouses. These objects are created and managed at the account level, and do not depend on any other securable object. The other options are not correct because:
Schemas belong to databases, not to accounts.A schema must be created within an existing database3.
Tables belong to schemas, not to accounts.A table must be created within an existing schema4.
Stages belong to schemas or tables, not to accounts. A stage must be created within an existing schema or table.
1: Overview of Access Control | Snowflake Documentation
2: Securable Objects | Snowflake Documentation
3: CREATE SCHEMA | Snowflake Documentation
4: CREATE TABLE | Snowflake Documentation
[5]: CREATE STAGE | Snowflake Documentation
When activating Tri-Secret Secure in a hierarchical encryption model in a Snowflake account, at what level is the customer-managed key used?

Tri-Secret Secure is a feature that allows customers to use their own key, called the customer-managed key (CMK), in addition to the Snowflake-managed key, to create a composite master key that encrypts the data in Snowflake. The composite master key is also known as the account master key (AMK), as it is unique for each account and encrypts the table master keys (TMKs) that encrypt the file keys that encrypt the data files. The customer-managed key is used at the account level, not at the root level, the table level, or the micro-partition level.The root level is protected by a hardware security module (HSM), the table level is protected by the TMKs, and the micro-partition level is protected by the file keys12.Reference:
Understanding Encryption Key Management in Snowflake
Tri-Secret Secure FAQ for Snowflake on AWS
Thomas Torres
7 days agoElizabeth Williams
9 days agoRyan Walker
1 month agoLaura Harris
1 month agoEmily Reed
1 month agoJohn Miller
27 days agoMichael Gonzalez
22 days agoMichael Davis
21 days agoFidelia
2 months agoOmer
2 months agoOdette
3 months agoMurray
3 months agoErick
3 months agoDana
3 months agoBong
4 months agoPolly
4 months agoReita
4 months agoLyda
4 months agoRosann
5 months agoNorah
5 months agoTeresita
5 months agoSommer
5 months agoCeleste
6 months agoCarmelina
6 months agoEssie
6 months agoFelicidad
6 months agoGilma
7 months agoMarguerita
7 months agoSage
7 months agoDorthy
7 months agoKristeen
8 months agoSabina
8 months agoCarlee
8 months agoBrock
8 months agoElvera
9 months agoDomonique
9 months agoMertie
9 months agoBroderick
9 months agoLatrice
9 months agoFranklyn
11 months agoTommy
11 months agoLawana
11 months agoBeckie
12 months agoCarlee
12 months agoJamie
1 year agoSylvia
1 year agoJoseph
1 year agoMicheline
1 year agoJani
1 year agoMalinda
1 year agoErinn
1 year agoMari
1 year agoMozelle
1 year agoDeangelo
1 year agoSamira
1 year agoTy
1 year agoSheldon
1 year agoMinna
1 year agoTawna
1 year agoMerilyn
2 years agoKimbery
2 years agoVonda
2 years agoGlory
2 years agoDalene
2 years agoEliz
2 years agoSherly
2 years agoCarman
2 years agoHortencia
2 years agoJamie
2 years agoAlverta
2 years agoRory
2 years agoBev
2 years agoErasmo
2 years agoPrincess
2 years agoAnnamae
2 years agoFernanda
2 years agoGalen
2 years agoGlenn
2 years agoBernardine
2 years agoAshley
2 years agoLeoma
2 years agoJerry
2 years agoHerminia
2 years agoEarlean
2 years agoBrianne
2 years ago