A. 3 NF

B. Data Vault

C. Star schema

D. Snowflake schema

A. The consumer sees the table only after SELECT is granted on the new table to the share on the provider side.

B. The consumer automatically sees the new table.

C. The consumer sees the table after USAGE is granted on the database and schema and SELECT is granted on the table to the consumer database.

D. The consumer sees the table after granting IMPORTED PRIVILEGES again on the consumer side.

A. value:activityNumber AS activity_number,
IFF(

B. value:winner = lf.json:leader.number,
lf.json:leader.name.default,
lf.json:follower.name.default
)::VARCHAR AS winner_name
FROM leader_follower lf,
LATERAL FLATTEN(input => json:activities, outer => TRUE) p;

C. value:activityNumber AS activity_number,
IFF(

D. value:winner = lf.json:leader.number,
lf.json:leader,
lf.json:follower
)::VARCHAR AS winner_name
FROM leader_follower lf,
LATERAL FLATTEN(input => json:activities) p;

E. SELECT lf.json:activities.activityNumber AS activity_number,
IFF(
lf.json:activities.activityNumber = lf.json:leader.number,
lf.json:leader.name.default,
lf.json:follower.name.default
)::VARCHAR
FROM leader_follower lf;

F. value:activityNumber AS activity_number,
IFF(

G. SELECT

H. value:winner = lf.json:leader.number,
lf.json:leader.name.default,
lf.json:follower.name.default
)::VARCHAR AS winner_name
FROM leader_follower lf,
LATERAL FLATTEN(input => json:activities) p;

I. SELECT

J. SELECT

A. The result set cache is not shared between warehouses.

B. The retention period can be reset for a maximum of 31 days.

C. Snowflake persists the data results for 24 hours.

D. Each time persisted results for a query are used, a 24-hour retention period is reset.

E. The data stored in the result cache will contribute to storage costs.

F. Time Travel queries can be executed against the result set cache.

A. Assume role with OWNERSHIP on VPN_ACCESS_LOGS and ADD SEARCH OPTIMIZATION in the SECURITY_LOGS schema.

B. Assume role with OWNERSHIP on future tables and ADD SEARCH OPTIMIZATION on the SECURITY_LOGS schema.

C. Assume role with ALL PRIVILEGES including ADD SEARCH OPTIMIZATION in the SECURITY LOGS schema.

D. Assume role with ALL PRIVILEGES on VPN_ACCESS_LOGS and ADD SEARCHOPTIMIZATION in the SECURITY_LOGS schema.

A. Use a row level policy on the user_events table using a entitlement table with valid dates.

B. Use a secure view on the user_events table using a case statement on the username column.

C. Use a masking policy on the username column with event_timestamp as a conditional column.

D. Use a masking policy on the username column using a entitlement table with valid dates.

A. Unmasked data will be loaded in the new column.

B. Masked data will be loaded into the new column.

C. Unmasked data will be loaded into the new column but only users with the appropriate privileges will be able to see the unmasked data.

D. Unmasked data will be loaded into the new column and no users will be able to see the unmasked data.

A. Grant R2 to users and use USE_SECONDARY_ROLES for SELECT.

B. Grant R2 to users and require USE SECONDARY ROLES.

C. Grant R2 to R1 to use privilege inheritance.

D. Set DEFAULT_SECONDARY_ROLE to R2.

A. Create a stored procedure that can be run using both caller's and owner's rights (allowing the user to specify which rights are used during execution), and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

B. Create a stored procedure that runs with owner's rights, including the appropriate "> 5 years" business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

C. This scenario would actually not be possible in Snowflake - any user performing a DELETE on a table requires the DELETE privilege to be granted to the role they are using.

D. Create a stored procedure that runs with caller's rights, including the appropriate "> 5 years" business logic, and grant USAGE on this procedure to ORDER_ADMIN. The ORDER_MANAGER role owns the procedure.

A. Spark

B. Snowflake Connector for Kafka

C. Snowflake streams

D. Snowpipe

A. External tables

B. Permanent table

C. Temporary table

D. Transient table

E. Internal stages

A. Query the event table MARKETING_DB.TELEMETRY.EVENTS.

B. Query the event table SNOWFLAKE.TELEMETRY.EVENTS.

C. Add a new event table and associate it with the Snowflake account.

D. Add a new event table and associate it with the Marketing database.

A. TRANSIENT

B. PERMANENT

C. TEMPORARY

A. Create a clustering key that contains all columns used in the access paths.

B. Create super projections that will automatically create clustering.

C. Create multiple clustering keys for a table.

D. Create multiple materialized views with different cluster keys.

A. Deploy a Private Data Exchange in combination with data shares for the European accounts.

B. Deploy a Private Data Exchange and use replication to allow European data shares in the Exchange.

C. Deploy to the Snowflake Marketplace making sure that invoker_share() is used in all secure views.

D. Migrate the European accounts in the global region and manage shares in a connected graph architecture. Deploy a Data Exchange.