COF-C02 無料問題集「Snowflake SnowPro Core Certification」

（A）Use a stored procedure executing multiple SQL statements and invoke the stored procedure from the task. CREATE TASK mytask .... AS call stored_proc_multiple_statements_inside();

（B）Create a task for each SQL statement (e.g. resulting in task1, task2, etc.) and string the series of SQL statements by having a control task calling task1, task2, etc. sequentially.

（C）Include the SQL statements in the body of the task CREATE TASK mytask .. AS INSERT INTO target1 SELECT .. FROM stream_s1 WHERE .. INSERT INTO target2 SELECT .. FROM stream_s1 WHERE ..

（D）A stored procedure can have only one DML statement per stored procedure invocation and therefore the user should sequence stored procedure calls in the taskdefinition CREATE TASK mytask .... AS call stored_proc1(); call stored_proc2();

（A）A Materialized View cannot be defined with a JOIN

（B）A Materialized View cannot be joined with other tables

（C）A Materialized View can only reference up to two tables

（D）A Materialized View cannot support any aggregate functions

（A）COPY_HISTORY

（B）DATA_TRANSFER_HISTORY

（C）VALIDATE_PIPE_LOAD

（D）PIPE_USAGE_HISTORY

（A）Into single files with 100-250 MB of compressed data per file

（B）Into files of maximum size of 1 GB of compressed data per file

（C）Into single files with 1-100 MB of compressed data per file

（D）Into files of maximum size of 4 GB of compressed data per file

（A）False

（B）True

（A）Implement a column-level security policy in the customer table that restricts access based on the user's geographic location.

（B）Implement a new account structure and create sub-accounts for each country. Then replicate the required data.

（C）Implement a row-level security policy in the customer table that looks at a mapping table identifying which users should have access to what data.

（D）Implement a secure User-Defined Function (UDF) and use a secure data share for each country.

（A）Query the REPLICATION USAGE HISTORY view in the ORGANIZATION USAGE schema.

（B）Review the granted privileges to the database object.

（C）Query the ACCESS_HlSTORY view in the ACCOUNT_USAGE schema.

（D）Review the row access policy for the database object.

（A）Virtual Private Snowflake Edition

（B）Enterprise Edition

（C）Standard Edition

（D）Business Critical Edition

（A）The account-level policy

（B）The most-restrictive policy

（C）The user-level policy

（D）The policy that was applied first

（A）Stream

（B）Task

（C）Snowpipe

（D）Stage

（A）SELECT EVENT_TIMESTAMP, USER_NAME
FROM table(information_schema.login_history_by_user())

（B）SELECT LAST_SUCCESS_LOGIN, LOGIN_NAME
FROM ACCOUNT_USAGE.USERS;

（C）SELECT EVENT_TIMESTAMP, USER_NAME
FROM ACCOUNT_USAGE.LOGIN_HISTORY;

（D）SELECT EVENT_TIMESTAMP, USER_NAME
FROM ACCOUNT_USAGE.ACCESS_HISTORY;

（A）A role that has the ownership of the network policy

（B）A role that has the NETWORK_POLlCY account parameter set

（C）A user with a SECURITYADMIN or higher role

（D）A user with an USERADMIN or higher role

（E）A role that has been granted the ATTACH POLICY privilege

（A）Setting up a multi-cluster virtual warehouse

（B）Automating the virtual warehouse suspension and resumption settings

（C）Increasing the maximum cluster count parameter for a multi-cluster virtual warehouse

（D）Resizing the virtual warehouse to a larger size

（A）Bytes scanned

（B）Bytes written

（C）Bytes read from result

（D）Partitions scanned

（E）Partitions total