What is a valid object hierarchy when building a Snowflake environment?
Correct Answer: B
This is the valid object hierarchy when building a Snowflake environment, according to the Snowflake documentation and the web search results. Snowflake is a cloud data platform that supports various types of objects, such as databases, schemas, tables, views, stages, warehouses, and more. These objects are organized in a hierarchical structure, as follows: * Organization: An organization is the top-level entity that represents a group of Snowflake accounts that are related by business needs or ownership. An organization can have one or more accounts, and can enable features such as cross-account data sharing, billing and usage reporting, and single sign-on across accounts12. * Account: An account is the primary entity that represents a Snowflake customer. An account can have one or more databases, schemas, stages, warehouses, and other objects. An account can also have one or more users, roles, and security integrations. An account is associated with a specific cloud platform, region, and Snowflake edition34. * Database: A database is a logical grouping of schemas. A database can have one or more schemas, and can store structured, semi-structured, or unstructured data. A database can also have properties such as retention time, encryption, and ownership56. * Schema: A schema is a logical grouping of tables, views, stages, and other objects. A schema can have one or more objects, and can define the namespace and access control for the objects. A schema can also have properties such as ownership and default warehouse . * Stage: A stage is a named location that references the files in external or internal storage. A stage can be used to load data into Snowflake tables using the COPY INTO command, or to unload data from Snowflake tables using the COPY INTO LOCATION command. A stage can be created at the account, database, or schema level, and can have properties such as file format, encryption, and credentials . The other options listed are not valid object hierarchies, because they either omit or misplace some objects in the structure. For example, option A omits the organization level and places the warehouse under the schema level, which is incorrect. Option C omits the organization, account, and stage levels, and places the table under the schema level, which is incorrect. Option D omits the database level and places the stage and table under the account level, which is incorrect. Snowflake Documentation: Organizations Snowflake Blog: Introducing Organizations in Snowflake Snowflake Documentation: Accounts Snowflake Blog: Understanding Snowflake Account Structures Snowflake Documentation: Databases Snowflake Blog: How to Create a Database in Snowflake [Snowflake Documentation: Schemas] [Snowflake Blog: How to Create a Schema in Snowflake] [Snowflake Documentation: Stages] [Snowflake Blog: How to Use Stages in Snowflake]
Question 122
Based on the architecture in the image, how can the data from DB1 be copied into TBL2? (Select TWO).
Correct Answer: B,E
The architecture in the image shows a Snowflake data platform with two databases, DB1 and DB2, and two schemas, SH1 and SH2. DB1 contains a table TBL1 and a stage STAGE1. DB2 contains a table TBL2. The image also shows a snippet of code written in SQL language that copies data from STAGE1 to TBL2 using a file format FF PIPE 1. To copy data from DB1 to TBL2, there are two possible options among the choices given: Option B: Use a named external stage that references STAGE1. This option requires creating an external stage object in DB2.SH2 that points to the same location as STAGE1 in DB1.SH1. The external stage can be created using the CREATE STAGE command with the URL parameter specifying the location of STAGE11. For example: SQLAI-generated code. Review and use carefully. More info on FAQ. use database DB2; use schema SH2; create stage EXT_STAGE1 url = @DB1.SH1.STAGE1; Then, the data can be copied from the external stage to TBL2 using the COPY INTO command with the FROM parameter specifying the external stage name and the FILE FORMAT parameter specifying the file format name2. For example: SQLAI-generated code. Review and use carefully. More info on FAQ. copy into TBL2 from @EXT_STAGE1 file format = (format name = DB1.SH1.FF PIPE 1); Option E: Use a cross-database query to select data from TBL1 and insert into TBL2. This option requires using the INSERT INTO command with the SELECT clause to query data from TBL1 in DB1.SH1 and insert it into TBL2 in DB2.SH2. The query must use the fully-qualified names of the tables, including the database and schema names3. For example: SQLAI-generated code. Review and use carefully. More info on FAQ. use database DB2; use schema SH2; insert into TBL2 select * from DB1.SH1.TBL1; The other options are not valid because: Option A: It uses an invalid syntax for the COPY INTO command. The FROM parameter cannot specify a table name, only a stage name or a file location2. Option C: It uses an invalid syntax for the COPY INTO command. The FILE FORMAT parameter cannot specify a stage name, only a file format name or options2. Option D: It uses an invalid syntax for the CREATE STAGE command. The URL parameter cannot specify a table name, only a file location1. Reference: 1: CREATE STAGE | Snowflake Documentation 2: COPY INTO table | Snowflake Documentation 3: Cross-database Queries | Snowflake Documentation
Question 123
What integration object should be used to place restrictions on where data may be exported?
Correct Answer: C
In Snowflake, a storage integration is used to define and configure external cloud storage that Snowflake will interact with. This includes specifying security policies for access control. One of the main features of storage integrations is the ability to set restrictions on where data may be exported. This is done by binding the storage integration to specific cloud storage locations, thereby ensuring that Snowflake can only access those locations. It helps to maintain control over the data and complies with data governance and security policies by preventing unauthorized data exports to unspecified locations.
Question 124
Following objects can be cloned in snowflake
Correct Answer: A,B,D
* Snowflake supports cloning of various objects, such as databases, schemas, tables, stages, file formats, sequences, streams, tasks, and roles. Cloning creates a copy of an existing object in the system without copying the data or metadata. Cloning is also known as zero-copy cloning1. * Among the objects listed in the question, the following ones can be cloned in Snowflake: * Permanent table: A permanent table is a type of table that has a Fail-safe period and a Time Travel retention period of up to 90 days. A permanent table can be cloned using the CREATE TABLE ... CLONE command2. Therefore, option A is correct. * Transient table: A transient table is a type of table that does not have a Fail-safe period and can have a Time Travel retention period of either 0 or 1 day. A transient table can also be cloned using the CREATE TABLE ... CLONE command2. Therefore, option B is correct. * External table: An external table is a type of table that references data files stored in an external location, such as Amazon S3, Google Cloud Storage, or Microsoft Azure Blob Storage. An external table can be cloned using the CREATE EXTERNAL TABLE ... CLONE command3. Therefore, option D is correct. * The following objects listed in the question cannot be cloned in Snowflake: * Temporary table: A temporary table is a type of table that is automatically dropped when the session ends or the current user logs out. Temporary tables do not support cloning4. Therefore, option C is incorrect. * Internal stage: An internal stage is a type of stage that is managed by Snowflake and stores files in Snowflake's internal cloud storage. Internal stages do not support cloning5. Therefore, option E is * incorrect. References: : Cloning Considerations : CREATE TABLE ... CLONE : CREATE EXTERNAL TABLE ... CLONE : Temporary Tables : Internal Stages
Question 125
Based on the Snowflake object hierarchy, what securable objects belong directly to a Snowflake account? (Select THREE).
Correct Answer: A,E,F
* 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. References: * 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
