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

An FTP server with TLS encryption

An HTTPS server with WebDAV

A Google Cloud storage bucket

A Windows server file share on Azure

When increasing the size of an active warehouse the compute resource for all running and queued queries on the warehouse are affected

When reducing the size of a warehouse the compute resources are removed only when they are no longer being used to execute any current statements.

The warehouse will be suspended while the new compute resource is provisioned and will resume automatically once provisioning is complete.

Users who are trying to use the warehouse will receive an error message until the resizing is complete

True

False

A read-only copy of the cloned tables is stored.

The replication will not be successful.

The physical data is replicated

Additional costs for storage are charged to a secondary account

Metadata pointers to cloned tables are replicated

Data sharing within a specific region

Query result retrieval

Database replication

Loading data into Snowflake

GRANT ROLE MYROLE TO USER USER1;

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

GRANT ROLE MYROLE TO USER USER1;

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

GRANT ROLE MYROLE TO USER USER1;

CREATE MATERIALIZED VIEW ON SCHEMA MYDB.MYSCHEMA TO USER1;

GRANT ROLE MYROLE TO USER USER1;

CREATE MATERIALIZED VIEW ON SCHEMA MYDB.MYSCHEMA TO MYROLE;

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

They are a type of User-defined Function (UDF).

They contain their own SQL code.

They call code that is stored inside of Snowflake.

They can return multiple rows for each row received

The user has the appropriate privileges on the objects associated with the query

Micro-partitions have been reclustered since the query was last run

The new query is run using the same virtual warehouse as the previous query

The query includes a User Defined Function (UDF)

The query has been run within 24 hours of the previously-run query