Free Snowflake ADA-C02 Exam Dumps Questions & Answers

If the query matches the definition, will Snowflake always dynamically rewrite the query to use a materialized view?

• A.Yes, because materialized views are always faster.
• B.No, because the materialized view may not be up-to-date.
• C.No, because the optimizer might decide against it.
• D.No, because joins are not supported by materialized views.

DatabaseA has a single schema called Schema1. This schema contains many tables and views. The ANALYST role has privileges to select from all objects in DatabaseA.Schema1. The SYSADMIN role clones DatabaseA to DatabaseA_clone.
What privileges does the ANALYST role have on tables and views in DatabaseA_clone? (Choose two.)

• A.USAGE on the schema DatabaseA_clone
• B.USAGE on the database DatabaseA_clone.Schema1
• C.SELECT on all tables, and only non-secure views in DatabaseA_clone.Schema1
• D.SELECT on all tables and views in DatabaseA_clone.Schema1
• E.SELECT on all tables, and only secure views in DatabaseA_clone.Schema1

What are the MINIMUM grants required on the database, schema, and table for a stream to be properly created and managed?

• A.Database: Usage
  Schema: Usage, Create Stream
  Table: Select
• B.Database: Usage
  Schema: Usage
  Table: Select
• C.Database: Usage, Create Stream
  Schema: Usage
  Table: Select
• D.Database: Usage
  Schema: Usage
  Table: Select, Create Stream

What steps are required to set up OKTAAPI token integration in Snowflake?

• A.create or replace security integration okta_provisioning
  type = scim
  scim_client = 'okta'
  run_as_role = 'OKTA PROVISIONER';
  Update this step every 6 months.
• B.use role ACCOUNTADMIN;
  select system$ generate_scim_access_token ('OKTA PROVISIONING');
  Update these steps every 12 months.
• C.grant role okta_provisioner to role ACCOUNTADMIN;
  create or replace security integration okta_provisioning
  type = scim
  scim_client = 'okta'
  run_as_role = 'OKTA PROVISIONER';
  Update these steps every 12 months.
• D.use role ACCOUNTADMIN;
  select system$ generate_scim_access_token ('OKTA PROVISIONING');
  Update these steps every 6 months.

A team of developers created a new schema for a new project. The developers are assigned the role DEV_TEAM which was set up using the following statements:
USE ROLE SECURITYADMIN;
CREATE ROLE DEV_TEAM;
GRANT USAGE, CREATE SCHEMA ON DATABASE DEV_DB01 TO ROLE DEV_TEAM;
GRANT USAGE ON WAREHOUSE DEV_WH TO ROLE DEV_TEAM;
Each team member's access is set up using the following statements:
USE ROLE SECURITYADMIN;
CREATE ROLE JDOE_PROFILE;
CREATE USER JDOE LOGIN_NAME = 'JDOE' DEFAULT ROLE='JDOE_PROFILE';
GRANT ROLE JDOE_PROFILE TO USER JDOE;
GRANT ROLE DEV_TEAM TO ROLE JDOE_PROFILE;
New tables created by any of the developers are not accessible by the team as a whole.
How can an Administrator address this problem?

• A.Assign usage privilege on the virtual warehouse DEV_WH to the role JDOE_PROFILE.
• B.Assign ownership privilege to DEV_TEAM on the newly-created schema.
• C.Set up future grants on the newly-created schemas.
• D.Set up the new schema as a managed-access schema.