COF-R02 SnowPro Core Recertification Exam Questions and Answers

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

list @file__stage

show @file__stage

view @file__stage

verify @file__stage

LOAD

copy

GET

PUT

Standard Edition

Enterprise Edition

Business Critical Edition

Virtual Private Snowflake Edition

If an account is enrolled with a Data Exchange, it will lose its access to the Snowflake Marketplace.

A Data Exchange allows groups of accounts to share data privately among the accounts.

A Data Exchange allows accounts to share data with third, non-Snowflake parties.

Data Exchange functionality is available by default in accounts using the Enterprise edition or higher.

The sharing of data in a Data Exchange is bidirectional. An account can be a provider for some datasets and a consumer for others.

4

8

16

32

SHOW GRANTS OF ROLE MY_ROLE

SHOW GRANTS TO ROLE MY_ROLE

SHOW GRANTS FOR ROLE MY_ROLE

SHOW GRANTS ON ROLE MY_ROLE

Queries against large tables where frequent DML occurs

Queries against tables larger than 1 TB

Selective point lookup queries

Queries against a subset of columns in a table

The ability to scale up warehouses

The use of warehouse auto scaling

The ability to resize warehouses

Use of multi-clustered warehouses

The use of warehouse indexing

Compute resources

Query execution

Authentication

Data storage

Metadata

@

&

$

#

The database ACCOUNTADMIN must define the clustering methodology for each Snowflake table.

Clustering is the way data is grouped together and stored within Snowflake micro-partitions.

The clustering key must be included in the COPY command when loading data into Snowflake.

Clustering can be disabled within a Snowflake account.

Amazon Web Services

Docker

IBM Cloud

Microsoft Azure Cloud

Google Cloud Platform

Oracle Cloud

All columns in a micro-partition

Any columns accessed during the query

The columns in the result set of the query

All rows accessed during the query

VARIANT

ARRAY

VARCHAR

XML

BLOB

VARIANT

VARRAY

STRUCT

ARRAY

QUEUE

True

False

Alation

DataRobot

dbt

Tableau

Okta Verify

Duo Mobile

Microsoft Authenticator

Google Authenticator

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;

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

SnowCLI

SnowUI

SnowSQL

SnowCD

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.

Cloud services layer

Compute layer

Storage layer

Cloud agnostic layer

8-16 MB

16-24 MB

10-99 MB

100-250 MB

Materialized views

Sequences

Procedures

Tables

Secure User Defined Functions (UDFs)

Privileges on the database

Existing child objects within the database

Future child objects within the database

Privileges on the schemas within the database

Only schemas and tables within the database

Row access policies

Data masking policies

Data encryption

Role based access control

Optimizes the virtual warehouse size and multi-cluster setting to economy mode

Allows a user to import the files in a sequential order

Increases the latency staging and accuracy when loading the data

Allows optimization of parallel operations

Compute layer

Storage layer

Cloud infrastructure layer

Cloud services layer

Snowflake parameters

Micro-partitions

Query history

Persisted query results

Standard and secure view results

Tables

Schemas

Databases

Stages

True

False

A Schema may contain one or more Databases

A Database may contain one or more Schemas

A Schema is a logical grouping of Database Objects

Each Schema is contained within a Warehouse

The global privilege create task is required to create a new task.

Tasks are created at the Application level and can only be created by the Account Admin role.

Many Snowflake DDLs are metadata operations only, and create task DDL can be executed without virtual warehouse requirement or task specific grants.

The role must have access to the target schema and the create task privilege on the schema itself.

4

16

32

128

True

False

It was built specifically for the cloud

It was built as an on-premises solution and then ported to the cloud

It was designed as a hybrid database to allow customers to store data either on premises or in the cloud

It was built for Hadoop architecture

It's based on an Oracle Architecture

Compute

Tri-Secret Secure

Storage

Cloud Services

The Pipe load history is reset to empty

The REFRESH parameter is set to TRUE

Previously loaded files will be ignored

All of the above

SYSADMIN

SECURITYADMIN

PUBLIC

ACCOUNTADMIN

Named Stage

User Stage

Table Stage

Schema Stage

Per-second/per Warehouse size

Per-second/per-core granularity

Number of Pipes in account

Total storage bucket size

True

False

The Snowflake Web Interface (UI)

SQL commands

Data integration tools

All of the above

The tables are now orphaned

The user that deleted the role

SYSADMIN

The assumed role that dropped the role