Practice Free COF-C02 SnowPro Core Certification Exam Exam Questions Answers With Explanation

SQL functions like the GET command can be used to copy the unstructured data to a location on the client.

SQL functions can be used to create different types of URLs pointing to the unstructured data. These URLs can be used to download the data to a client.

SQL functions can be used to retrieve the data from the query results cache. When the query results are output to a client, the unstructured data will be output to the client as files.

SQL functions can call on different web extensions designed to display different types of files as a web page. The web extensions will allow the files to be downloaded to the client.

A user with an USERADMIN or higher role

A user with a SECURITYADMIN or higher role

A role that has been granted the ATTACH POLICY privilege

A role that has the NETWORK_POLlCY account parameter set

A role that has the ownership of the network policy

CREATE SESSION POLICY

CREATE NETWORK RULE

CREATE SECURITY INTEGRATION

CREATE PASSWORD POLICY

Warehouses that are multi-cluster can have nodes of different sizes.

Warehouses can be started and stopped at any time.

Warehouses can be resized at any time, even while running.

Warehouses are billed on a per-minute usage basis.

Warehouses can only be used for querying and cannot be used for data loading.

Queries without filters or aggregation

Queries with large scans and selective filters

Queries where the GROUP BY has high cardinality

Queries of tables that have search optimization service enabled

Range of values

Distinct values

Index values

Sorted values

Null values

Use clustering keys

Create materialized views

Use the search optimization service

Use the query acceleration service

Object owner

Schema owner

Database owner

SYSADMIN

A Query Profile can help users right-size virtual warehouses.

A Query Profile defines the hardware specifications of the virtual warehouse.

A Query Profile can help determine the number of virtual warehouses available.

A Query Profile automatically scales the virtual warehouse based on the query complexity.

Views

Materialized views

Tables

External tables

Future grants

ARRAY

CHARACTER

STRING

VARCHAR

VARIANT

TEXT

BINARY

STRING

VARIANT

USERADMIN

ORGADMIN

SYSADMIN

SECURITYADMIN

All data from all of the files on the stage will be appended to the table

Only data about new customers from the new files will be appended to the table

The operation will fail with the error uncertain files in stage.

All data from only the newly-added files will be appended to the table.

Create an account for an organization.

Edit the account data for an organization.

Delete the account data for an organization.

View usage information for all accounts in an organization.

Select all the data in tables for all accounts in an organization.

Data Replication

Secure Data Sharing

Data Exchange

Snowflake Marketplace

Manually re-cluster the table regularly.

Choose one high cardinality column as the clustering key.

Use the column that is most-frequently used in query select clauses as the clustering key.

Assess the average table depth to identify how clustering is impacting the query.

Bytes scanned

Bytes written to result

Partitions scanned

Partitions total

Percentage scanned from cache

Operator tree

Table pruning

Most expensive nodes

Nodes by execution time

Data:employee.name

DATA:employee.name

data:Employee.name

data:employee.name

GROUP BY

LIMIT

ORDER BY

PARTITION BY

UNION ALL

Data classification

Query acceleration service

Search optimization service

Tagging

Enable Time Travel.

Clone the dropped stage.

Execute the UNDROP command.

Recreate the dropped stage.

Graphical representation of the data model

Statistics for each component of the processing plan

Detailed Information about I he database schema

Real-time monitoring of the database operations

Send an alert notification to all account users who have notifications enabled.

Send an alert notification to all virtual warehouse users when thresholds over 100% have been met.

Send a notification to all account administrators who have notifications enabled, and suspend all assigned warehouses after all statements being executed by the warehouses have completed.

Send a notification to all account administrators who have notifications enabled, and suspend all assigned warehouses immediately, canceling any statements being executed by the warehouses.

SELECT

OWNERSHIP

MONITOR

MODIFY

USAGE

Casts the values of the flattened data

Extracts the path of the flattened data

Joins information outside the object with the flattened data

Retrieves a single instance of a repeating element in the flattened data

Reader account users cannot add new data to the account.

Reader account users can share data to other reader accounts.

A single reader account can consume data from multiple provider accounts.

Data consumers are responsible for reader account setup and data usage costs.

Reader accounts enable data consumers to access and query data shared by the provider.

The base tables do not change frequently.

The results of the view change often.

The query is not resource intensive.

The query results are not used frequently.

ALTER ROLE

REVOKE ROLE

USE ROLE

USE SECONDARY ROLES

60 minutes

24 hours

14 days

30 days

FLATTEN

CHECK_JSON

PARSE_JSON

TO_VARIANT

Secure view

Materialized view

Temporary table

Transient table

ACCOUNTADMIN

SECURITYADMIN

SYSADMIN

ORGADMIN

ARRAY_AGG

OBJECT_AGG

ARRAY_CONSTRUCT

OBJECT_CONSTRUCT

It uses a local data repository for all compute nodes in the platform.

It is a blend of shared-disk and shared-everything database architectures.

It is a hybrid of traditional shared-disk and shared-nothing database architectures.

It reorganizes loaded data into internal optimized, compressed, and row-based format.

Use the SHOW STAGES command.

Use the DESCRIBE STAGE command.

Use the GET_ABSOLUTE_PATH function.

Use the GET_STAGE_LOCATION function.

Last_QUERY_ID

CURRENT_STATEMENT

UUID_STRING

JOB_ID

GET_STATE_LOCATION

GET_PRESENT_URL

BUILD_SCOPED_FILE_URL

BUILD_STAGE_FILE_URL

Cloud services

Query processing

Elastic memory

Database storage

Caching

Cluster depth

Query pruning

Retrieval optimization

UTF-8

UTF-16

ISO-8859-1

WINDOWS-1253

Aggregate

Scalar

Table

Window

0 days

1 day

7 days

14 days

File URL

Scoped URL

Pre-signed URL

Scoped file URL

SYSTEMADMIN_TAG

SYSTEM$GET_PRIVATELINK

SYSTEMSALLONTLIST

SYSTEMAUTHORIZE

The access to a single table

The access to data stored in stage objects

The list of values provided with the VALUES clause

The records generated using the TABLE (GENERATOR (...)) construct

ACCOUNTADMIN

SECURITYADMIN

SYSADMIN

ORGADMIN

MODIFY

READ

SELECT

USAGE

A single executable statement can call only two stored procedures. In contrast, a single SQL statement can call multiple UDFs.

A single executable statement can call only one stored procedure. In contrast, a single SQL statement can call multiple UDFs.

A single executable statement can call multiple stored procedures. In contrast, multiple SQL statements can call the same UDFs.

Multiple executable statements can call more than one stored procedure. In contrast, a single SQL statement can call multiple UDFs.

Add or remove users from a worksheet.

Move a worksheet to a folder or a dashboard.

Combine multiple worksheets into a single worksheet.

Tag frequently accessed worksheets for ease of access.

SHOW TABLES command

SHOW EXTERNAL TABLES command

TABLES view

TABLE STORAGE METRICS view

1

5

10

100

60

91

120

121

A single-cluster shared data architecture using a central data repository and massively parallel processing (MPP)

A multi-duster shared nothing architecture using a soloed data repository and massively parallel processing (MPP)

A single-cluster shared nothing architecture using a sliced data repository and symmetric multiprocessing (SMP)

A multi-cluster shared nothing architecture using a siloed data repository and symmetric multiprocessing (SMP)

Partitions scanned

Partitions total

Bytes scanned

Bytes read from result

Bytes written

Disaster recovery

Time Travel

Fail-safe

Database failover and fallback

Data security

Worksheets can be grouped under folder, and a folder of folders.

Each worksheet is a unique Snowflake session.

Users are limited to running only one on a worksheet.

The Snowflake session ends when a user switches worksheets.

Users can import worksheets and share them with other users.

BINARY

GEOGRAPHY

GEOMETRY

OBJECT

VARIANT

They are a set of rules that define the network routes within Snowflake.

They are a set of rules that dictate how Snowflake accounts can be used between multiple users.

They are a set of rules that define how data can be transferred between different Snowflake accounts within an organization.

They are a set of rules that control access to Snowflake accounts by specifying the IP addresses or ranges of IP addresses that are allowed to connectto Snowflake.

User stage

Table stage

Named internal stage

Named external stage

Syntax error

Inefficient pruning

Ambiguous column names

Queries too large to fit in memory

Object does not exist or not authorized

1 minutes

5 minutes

10 minutes

15 minutes

TABLES

TABLE_STORAGE_METRICS

STORAGE_DAILY_HISTORY

STORAGE USAGE

Dynamic table

Hybrid table

Directory table

Iceberg table

Use the SECURITYADMIN role.

Use the SYSADMIN role.

Use the USERADMIN role.

Contact Snowflake Support.

Data storage

Dynamic data masking

Partition scanning

User authentication

Infrastructure management

Dictionary

List

Object

Scalar

Tabular

Binary file in Avro

Binary file in Parquet

Comma-separated JSON

Newline Delimited JSON

Plain text file containing XML elements

1 hour

2 hours

4 hours

8 hours

LOAD

copy

GET

PUT

show grants to user USER1;

show grants of user USER1;

describe user USER1;

show grants on user USER1;

Customer-managed encryption keys through Tri-Secret Secure

Automatic encryption of all data

Up to 90 days of data recovery through Time Travel

Object-level access control

Column-level security to apply data masking policies to tables and views

ROLES

POLICY_REFERENCES

QUERY_HISTORY

RESOURCE_MONIT ORS

ACCESS_HISTORY

1 day

7 days

45 days

90 days

Bytes scanned

Bytes sent over the network

Number of partitions scanned

Percentage scanned from cache

External bytes scanned

Users

Tables

Databases

Internal Stages

INSERT

MERGE

SELECT

UPDATE

DELETE

SELECT SPLIT_TO_TABLE FROM DUAL;

SELECT SPLIT_TO_TABLE('a.b.c', '.');

SELECT * FROM TABLE(SPLIT_TO_TABLE('a.b.c', '.'));

SELECT * FROM SPLIT_TO_TABLE('a-b.c', '.');

Schemas

Databases

Masking policies

External functions

Virtual warehouses

When there is a need for a predefined schema which cannot be changed after it is created.

When there is a need to add or modify elements within the data structure without interrupting the session.

When the data set is huge and the order of the data elements in the data set does not change.

When the data contains nested data structures like JSON or XML.

When the data consists of images and videos.

Repair the failed resources.

Restart failed resources.

Queue the failed resources

Provision the failed resources

Standard

Enterprise

Business Critical

Virtual Private Snowflake (VPS)

BUILD_STAGE_FILE_URL

BUILD_SCOPED_FILE_URL

GET_PRESIGNED_URL

GET STAGE LOCATION

To view any queries that encountered an error

To verify that a SELECT query will run without error

To prevent a put statement from running if an error occurs

To see all errors from a previously run COPY INTO <table> statement

MATCH_BY_COLUMN_NAME = CASE_INSENSITIVE

ENFORCE_LENGTH = TRUE

PURGE = TRUE

LOAD_UNCERTAIN_FILES = TRUE

By clustering the tables

By creating a persistent data structure

By using caching

By optimizing the use of micro-partitions

No micro-partitions were pruned during execution.

The query used the local disk cache and pruning was not required.

The size of the data queried was too small to trigger micro-partition pruning.

Since the bytes scanned is less than the bytes written to results some pruning has occurred.

It will return an error.

It will return a warning.

The suspended warehouse is resumed and new compute resources are provisioned immediately.

The additional compute resources are provisioned when the warehouse is resumed.

When the query contains multiple filters and no data is returned.

When a virtual warehouse runs out of memory while executing the query.

When the number of queries exceeds the max_concurrency_level parameter setting.

When running queries that exceed the statement_timecut_in_seccnds parameter setting.

A tag can be dropped after a masking policy is assigned

A tag can have only one masking policy for each data type.

A tag can have multiple masking policies for each data type.

A tag can have multiple masking policies with varying data types

Processing

Resource usage

Query Plan execution steps

Bytes scanned

Partitions scanned

Tasks

Pipes

Secure User-Defined Functions (UDFs)

Stored Procedures

Standard

Enterprise

Business Critical

Virtual Private Snowflake (VPS)

The COPY INTO commands will load the data only once in the table.

The COPY INTO commands will duplicate the data in the table.

The COPY INTO commands will all fail with an error due to reading the same file.

The COPY INTO commands will overwrite the data in the table.

The privileges that have been granted to the ACCOUNTADMIN role

The privileges on objects held by the custom role

The privileges accessed by the PUBLIC role

The privileges accessed by the USERADMIN role

Auto-suspend

Cache size

Default role

Resource monitor

Storage size

PUT

INSERT

COPY INTO

GET

When the object owner has been granted a database role

When the object owner has been granted an account role

When the object is part of a managed access schema

When the object is part of a regular schema

COPY INTO

GET

LIST

REMOVE

The manual-refresh operations and the automatic-refresh operations will both take place.

The automatic-refresh operations will be aborted.

The automatic-refresh operations will be performed more often.

The automatic-refresh operations will continue on the established schedule.

LOAD_HISTORY

STAGE_STORAGE_USAGE_HISTORY

COPY_HISTORY

DATA TRANSFER HISTORY

GET_ABSOLUTE_PATH

GET_PRESIGNED_URL

GET_STAGE_LOCATION

BUILD_STAGE_FILE_URL

ACCESS_HISTORY

LOAD_HISTORY

QUERY_HISTORY

REST EVENT HISTORY

If the table and sequence are in the same schema, the cloned table will reference the source sequence.

If the table and sequence are in the same schema, the cloned table will reference the cloned sequence.

If the table and sequence are in different schemas, the cloned table will reference the source sequence.

If the table and sequence are in different schemas, the cloned table will no longer have a default value for the column.

If the table and sequence are in the same schema, the cloned table will use the most-recently generated value from the source sequence.

XML

JSON

Parquet

CSV

All privileges that have been granted to the ACCOUNTADMIN

All privileges on objects allowed by the custom role

Access to the PUBLIC role

Access to all the objects owned by the USERADMIN role

Auto-scale mode

Maximized mode

Standard scaling policy

Economy scaling policy

The retention period will be equal to the value of the parameter MIN_DATA_RETENTION_TIME_IN_DAYS set at the account level.

The retention period will be equal to the value of the parameter DATA_RETENTION_TIME_IN_DAYS set at the object level.

The retention period will be equal to the greatest of the two values of parameters DATA_RETENTION_TIME_IN_DAYS set at the object level, and MIN_DATA_RETENTION_TIME_IN_DAYS set at the account level.

The retention period will be equal to the lesser of the two values of parameters DATA_RETENTION_TIME_IN_DAYS set at the object level and MIN_DATA_RETENTION_TIME_IN_DAYS set at the account level.

2

3

5

7

MANAGE SHARE

IMPORT SHARE

USERADMIN

SECURITYADMIN

ACCOUNTADMIN

Micro-partitions

Clustering keys

Equality searches

Search access paths

DATA_TRANSFER_HISTORY

PIPE_USAGE_HISTORY

VALIDATE_PIPE_LOAD

COPY_HISTORY

Use the copy option files=single.

Use the COPY Option SINGLE=TRUE .

Use the get option SINGLE-TRUE.

Use the GET option FILES-SINGLE.

CREATE PIPE at the schema level

SELECT and INSERT on the table in the pipe definition

CREATE SCHEMA at the database level

USAGE on the virtual warehouse

OWNERSHIP on the table in the pipe definition

All child objects will retain data for the new retention period.

All child objects that do not have an explicit retention period will automatically inherit the new retention period.

All child objects with an explicit retention period will be overridden with the new retention period.

All explicit child object retention periods will remain unchanged.

Materialized views do not allow joins.

Clones of materialized views can be created directly by the user.

Multiple tables can be joined in the underlying query of a materialized view.

Aggregate functions can be used as window functions in materialized views.

ACCESS_HISTORY

COPY_HISTORY

QUERY_HISTORY

ROW ACCESS POLICIES

By setting up network policies with IPv4 IP addresses

By putting the Snowflake URL on the allowed list for get method responses

By manually setting up vulnerability patch management policies

By manually setting up an Intrusion Prevention System (IPS) on each account

DELETE

REMOVE

TRUNCATE

DROP

TO_OBJECT

TO_JSON

TO_VARIANT

OBJECT CONSTRUCT

Network policy

End-to-end encryption

Multi-Factor Authentication (MFA)

Role-Based Access Control (RBAC)

QUALIFY

LATERAL

PIVOT

CONNECT BY

Tag

Task

Stream

Stored procedure

Insert a colon (:) between the VARIANT column name and any first-level element.

Insert a colon (:) between the VARIANT column name and any second-level element. C. Insert a double colon (: :) between the VARIANT column name and any first-level element.

Insert a double colon (: :) between the VARIANT column name and any second-level element.

Use COPY INTO followed by a GET command to download the file.

Use COPY INTO followed by a put command to download the file.

Use COPY INTO with SINGLE = TRUE followed by a GET command to download the file.

Use COPY INTO with SINGLE = TRUE followed by a PUT command to download the file.

CREATE STAGE

COPY INTO <table>

COPY INTO

CREATE PIPE

Add and remove members.

Delete data categories.

Approve and deny listing approval requests.

Transfer listing ownership.

Transfer ownership of a provider profile.

To store actual data from external stages

To automatically expire file URLs for security

To manage user privileges and access control

To store file-level metadata about data files in a stage

FLATTEN

GET_PATH

CHECK_JSON

PARSE JSON

Access control

Fail-safe

Network policies

Time Travel

Column reordering

Column omission

JOIN function

FLATTEN function

GROUP BY function

Review the granted privileges to the database object.

Review the row access policy for the database object.

Query the ACCESS_HlSTORY view in the ACCOUNT_USAGE schema.

Query the REPLICATION USAGE HISTORY view in the ORGANIZATION USAGE schema.

When creating a table

When loading data into a table

When unloading data from a table

When executing a show command

When executing a list command

Secure view

Materialized view

Temporary table

Transient table

It removes null values from all columns in the data.

It converts null values to empty strings during loading.

It skips rows with null values during the loading process.

It removes object or array elements containing null values.

MONITOR

OPERATE

OWNERSHIP

ALL

USAGE_VIEWER

GOVERNANCE_VIEWER

OBJECT_VIEWER

SECURITY_VIEWER

Temporary tables

Permanent tables

Transient tables

External tables

User-Defined Table Functions (UDTFs)

RETURN_-1_R0WS

RETURN_n_ROWS

RETURN_ERRORS

RETURN ALL ERRORS

Clustering keys update the micro-partitions in place with a full sort, and impact the DML operations.

Clustering keys sort the designated columns over time, without blocking DML operations

Clustering keys create a distributed, parallel data structure of pointers to a table's rows and columns

Clustering keys establish a hashed key on each node of a virtual warehouse to optimize joins at run-time

Data can be filtered by an optional where clause

Incoming data can be joined with other tables

Columns can be reordered

Columns can be omitted

Row level access can be defined

Create a task that runs a copy into operation from an external stage every 5 minutes

Create a task that puts the files in an internal stage and automate the data loading wizard

Create a task that runs a GET operation to intermittently check for new files

Set up cloud provider notifications on the Tile location and use Snowpipe with auto-ingest

A compressed file size greater than 100 MB, and up to 250 MB

A compressed file size greater than 100 GB, and up to 250 GB

A compressed file size greater than 10 MB, and up to 100 MB

A compressed file size greater than 1 GB, and up to 2 GB

Pipes

Streams

Tasks

Procedures

When dropping an external stage, the files are not removed and only the stage is dropped

When dropping an external stage, both the stage and the files within the stage are removed

When dropping an internal stage, the files are deleted with the stage and the files are recoverable

When dropping an internal stage, the files are deleted with the stage and the files are not recoverable

When dropping an internal stage, only selected files are deleted with the stage and are not recoverable

True

False

account__usage . query history view

account__usage.query__history__archive View

information__schema . cruery_history view

information__schema - query history_by_ses s i on view

Snowflake parameters

Micro-partitions

Query history

Persisted query results

Standard and secure view results

CSV

JSON

Parquet

XML

Cluster keys

Time Travel

Fail-safe

Cloning

ACCOUNTADMIN

ORGADMIN

SECURITYADMIN

SYSADMIN

Alation

DataRobot

dbt

Tableau

True

False

Possibly, if the warehouse is resized to a smaller size and the cache no longer fits.

Yes. because the compute resource is replaced in its entirety with a new compute resource.

No. because the size of the cache is independent from the warehouse size

Yes. became the new compute resource will no longer have access to the cache encryption key

True

False

Standard Edition

Enterprise Edition

Business Critical Edition

Virtual Private Snowflake Edition

A User Defined Function (UDF)

A stored procedure

A single copy_into statement

A single insert__into statement

ROLEADMIN

ACCOUNTADMIN

SYSADMIN

SECURITYADMIN

USERADMIN

An FTP server with TLS encryption

An HTTPS server with WebDAV

A Google Cloud storage bucket

A Windows server file share on Azure

Data sharing within a specific region

Query result retrieval

Database replication

Loading data into Snowflake

Column-level security

SOC 2 type II certification

Multi-factor Authentication (MFA)

Object-level access control

Time Travel - 1 day. Fail-safe - 1 day

Time Travel - 0 days. Fail-safe - 1 day

Time Travel - 1 day. Fail-safe - 0 days

Transient tables are retained in neither Fail-safe nor Time Travel

list @mytable;

list @%raytable;

list @ %m.ystage;

list @mystage;

Through the Snowflake web interface (Ul)

Through the DATA_SHARE=TRUE parameter

Through SQL commands

Through the enable__share=true parameter

Using the CREATE SHARE AS SELECT * TABLE command

The primary cluster in the virtual warehouse

The entire virtual warehouse

The database in which the virtual warehouse resides

The Queries currently being run on the virtual warehouse

SCIM

Federated authentication

TLS 1.2

Key-pair authentication

OAuth

OCSP authentication

Zero-copy cloning creates a mirror copy of a database that updates with the original

Software updates are automatically applied on a quarterly basis

Snowflake eliminates resource contention with its virtual warehouse implementation

Multi-cluster warehouses allow users to run a query that spans across multiple clusters

Snowflake automatically sorts DATE columns during ingest for fast retrieval by date

Query against the result set cache

Query against a virtual warehouse cache

Query against the most-recently created micro-partition

Query against the metadata excite

Querying data-related objects that were created within the past 365 days

Restoring data-related objects that have been deleted within the past 90 days

Conducting point-in-time analysis for Bl reporting

Analyzing data usage/manipulation over all periods of time

Compute Credits = 50 Credits Cloud Services = 10

Compute Credits = 80 Credits Cloud Services = 5

Compute Credits = 10 Credits Cloud Services = 9

Compute Credits = 120 Credits Cloud Services = 10

Compute Credits = 200 Credits Cloud Services = 26

Via the Snowflake Web Interface (Ul)

Via thedata_share=trueparameter

Via SQL commands

Via Virtual Warehouses

Columns can be aggregated

Columns can be joined with an existing table

Columns can be reordered

Columns can be omitted

Data can be loaded without the need to spin up a virtual warehouse

Yes, because a table owner has full control and can unset masking policies.

Yes, because masking policies only apply to cloned tables.

No, because masking policies must always reference specific access roles.

No, because ownership of a table does not include the ability to change masking policies

ALLOW RESIZE ON WAREHOUSE MKTG__WH TO USER MKTG__LEAD;

GRANT MODIFY ON WAREHOUSE MKTG WH TO ROLE MARKETING;

GRANT MODIFY ON WAREHOUSE MKTG__WH TO USER MKTG__LEAD;

GRANT OPERATE ON WAREHOUSE MKTG WH TO ROLE MARKETING;

Root task may be executed concurrently (i.e. multiple instances), it is recommended to leave some margins in the execution window to avoid missing instances of execution

Querying(select)the size of the stream content would help determine the warehouse size. For example, if querying large stream content, use a larger warehouse size

If using the stored procedure to execute multiple SQL statements, it's best to test run the stored procedure separately to size the compute resource first

Since task infrastructure is based on running the task body on schedule, it's recommended to configure the virtual warehouse for automatic concurrency handling using Multi-cluster warehouse (MCW) to match the task schedule

Load files that are approximately 25 MB or smaller.

Remove all dates and timestamps.

Load files that are approximately 100-250 MB (or larger)

Avoid using embedded characters such as commas for numeric data types

Remove semi-structured data types

As configured in the create pipe settings

Until the pipe is dropped

64 days

14 days

Enable the data sharing feature in the account and validate the view.

Use the CURRENT_ROLE and CURRENT_USER functions to validate secure views.

Use the CURRENT_ function to authorize users from a specific account to access rows in a base table.

Set the SIMULATED DATA SHARING CONSUMER session parameter to the name of the consumer account for which access is being simulated.

STRIP_NULL_VALUES

SKIP_BYTE_ORDER_MARK

REPLACE_INVALID_CHARACTERS

VALIDATION_MODE

Materialized views

Sequences

Procedures

Tables

Secure User Defined Functions (UDFs)

Infrastructure management

Metadata management

Query execution

Query parsing and optimization

Management of the storage layer

The columns that are queried in the select clause.

The columns with very high cardinality.

The columns with many different values.

The columns most actively used in the select filters.

Pipe

File format

Resource monitor

Storage integration

Virtual warehouse

A User-Defined Table Function (UDTF)

A Scalar User Function (UDF)

A stored procedure

A task

Append-only

External

Insert-only

Standard

GRANT ROLE MYROLE TO USER USER1;GRANT CREATE MATERIALIZED VIEW ON SCHEMA MYDB.MYSCHEMA TO ROLE MYROLE;

GRANT ROLE MYROLE TO USER USER1;GRANT CREATE MATERIALIZED VIEW ON SCHEMA MYDB.MYSCHEMA TO USER USER1;

GRANT ROLE MYROLE TO USER USER1;GRANT CREATE MATERIALIZED VIEW ON SCHEMA MYDB. K"-'SCHEMA TO USER! ;

GRANT ROLE MYROLE TO USER USER1;GRANT CREATE MATERIALIZED VIEW ON SCHEMA MYDB.MYSCHEMA TO MYROLE;

In the metadata of the target table for 14 days

In the metadata of the pipe for 14 days

In the metadata of the target table for 64 days

In the metadata of the pipe for 64 days

It assigns each unloaded data file a unique name.

It uses the put command to download the data by default.

It uses COPY INTO for bulk unloading where the default option is SINGLE - TRUE.

It uses COPY INTO to copy the data from a table into one or more files in an external stage only.

Listing

Direct share

Reader account

Data Exchange

1 hour

2 hours

4 hours

8 hours

File URL

Staged URL

Scoped URL

Pre-signed URL

When users will be using compute at different times throughout a 24/7 period

When managing a steady workload

When the compute must be available with no delay or lag time

When the user does not want to have to manually turn on the warehouse each time it is needed

When the warehouse is shared across different teams

Grant the OWNERSHIP privilege on the schema.

Grant the OWNERSHIP privilege on the database.

Grant the MANAGE GRANTS global privilege.

Grant ALL privileges on the schema.

8MB

16MB

32MB

128MB

ARRAY

OBJECT

VARCHAR

VARIANT

7 days

14 days

28 days

365 days

The reader account will automatically use the Standard edition of Snowflake.

The reader account compute will be billed to the provider account.

The reader account can clone data the provider has shared, but cannot re-share it.

The reader account can create a copy of the shared data using CREATE TABLE AS...

DISABLED

MINS TO BYPASS MFA

MINS TO BYPASS NETWORK POLICY

MINS TO UNLOCK

Account and user authentication is only available with the Snowflake Business Critical edition.

Support for HIPAA and GDPR compliance is available for UI Snowflake editions.

Periodic rekeying of encrypted data is available with the Snowflake Enterprise edition and higher

Private communication to internal stages is allowed in the Snowflake Enterprise edition and higher.

10

50

64

256

Table definition

Stage definition

Session level

COPY INTO TABLE statement

No virtual warehouse will be used, data will be read from the result cache.

No virtual warehouse will be used, data will be read from the local disk cache.

The default virtual warehouse will be used to read all data.

The virtual warehouse that is defined at the session level will be used to read all data.

30 Days

60 Days

90 Days

365 Days.

When the data cache clears.

When the persisted query result period ends.

The encoded URL access is permanent.

The length of time is specified in the expiration_time argument.

Reorder the rows in a relational table and then unload the rows into a file

Convert the rows in a relational table lo a single VARIANT column and then unload the rows into a file.

Reorder the data columns according to a target table definition and then unload the rows into the table.

Convert the rows in a source file to a single variant column and then load the rows from the file to a variant table.

Auto-scale mode

Maximized mode

Economy scaling policy

Standard scaling policy

The number of queries executed

The number of active users assigned to the warehouse

The size of the virtual warehouse

The length of time the warehouse is running

The duration of the queries that are executed

USERADMIN

PUBLIC

ORGADMIN

SYSADMIN

A VARIANT column

A column with very low cardinality

A column with very high cardinality

A column that is most actively used in selective filters

A column that is most actively used in join predicates

Query execution

Data loading

Time Travel data

Security

Authentication and access control

Rename listings.

Delete provider profiles.

Modify listings properties.

Modify incoming listing access requests.

Submit listings for approval/publishing.

There is minimal cost associated with running the query.

The query consumes many compute resources every time it runs.

The base table gets updated frequently.

The query is highly optimized and does not consume many compute resources.

The results of the query do not change often and are used frequently.

IMPORT SHARE

OWNERSHIP

REFERENCES

USAGE

NUMBER

OBJECT

STRING

VARCHAR

VARIANT

When unloading semi-structured data, it is recommended that the STRIP_OUTER_ARRAY option be used.

Use the ENCODING file format option to change the encoding from the default UTF-8.

The OBJECT_CONSTRUCT function can be used to convert relational data to semi-structured data.

By using the SINGLE = TRUE parameter, a single file up to 5 GB in size can be exported to the storage layer.

Use the PARSE_JSON function to ensure structured data will be unloaded into the VARIANT data type.

B-tree

Indexing

Map reduce

Pruning

The clone always stays in sync with the original table.

The clone has better query performance.

The clone is created almost instantly.

The clone will have time travel history from the original table.

The clone saves space by not duplicating storage.

Create dashboards.

Write and run SQL queries.

Explore databases and objects.

Explore executed query performance.

Use Snowpipe.

Use the INSERT command.

Use an external table.

Use the COPY command.

inscrtFilcs

insertReport

GET /api/tiles/

loadHistoryScan

Stored procedures can execute database operations while UDFs cannot.

Returning a value is required in a stored procedure while returning values in a UDF is optional.

Values returned by a stored procedure can be used directly in a SQL statement while the values returned by a UDF cannot.

Multiple stored procedures can be called as part of a single executable statement while a single SQL statement can only call one UDF at a time.

1

2

3

4

CREATE_SHARE on the account

SHARE on databases and schemas

SELECT on tables used by the secure view

REFERENCE_USAGE on databases

Swift

JavaScript

Python

SQL

The data from the permanent table.

The data from the temporary table.

An error stating that the view could not be compiled.

An error stating that the referenced object could not be uniquely identified.

A reader account can consume data from the provider account that created it and combine it with its own data.

A consumer needs to become a licensed Snowflake customer as data sharing is only supported between Snowflake accounts.

The users in a reader account can query data that has been shared with the reader account and can perform DML tasks.

The SHOW MANAGED ACCOUNTS command will view all the reader accounts that have been created for an account.

Enterprise

Business Critical

Standard

Virtual Private Snowflake

INTERSECT

MFRCK

MINUS

UNION

CHECK_JSON

TO_JSON

FLATTEN

PARSE_JSON

Indefinitely

Until the result_cache expires

Until the retention_time is met

Until the expiration time is exceeded

UPDATE TABLE FROM STREAM

SELECT FROM STREAM

INSERT INTO TABLE SELECT FROM STREAM

ALTER TABLE AS SELECT FROM STREAM

BEGIN COMMIT

When it is unknown how much compute power is needed

If the select statement contains a large number of temporary tables or Common Table Expressions (CTEs)

If the runtime of the executed query is very slow

When a large number of concurrent queries are run on the same warehouse

Within the policy DDL

Within the create table or create view DDL

By future APPLY for all objects in a schema

Within a control table

Using the command ALTER