A company has implemented Snowflake replication between two Snowflake accounts, both of which are running on a Snowflake Enterprise edition. The replication is for the database APP_DB containing only one schema, APP_SCHEMA. The company's time Travel retention policy is currently set for 30 days for both accounts. An Administrator has been asked to extend the time Travel retention policy to 60 days on the secondary database only.
How can this requirement be met?

• A. Set the data retention policy on the primary database to 60 days.
• B. Set the data retention policy on the secondary database to 60 days.
• C. Set the data retention policy on the schemas in the secondary database to 60 days.
• D. Set the data retention policy on the primary database to 30 days and the schemas to 60 days.

Explanation: Only visible for TroytecDumps members. You can sign-up / login (it's free).

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

• A. use role ACCOUNTADMIN;
  select system$ generate_scim_access_token ('OKTA PROVISIONING');
  Update these steps every 6 months.
• B. use role ACCOUNTADMIN;
  select system$ generate_scim_access_token ('OKTA PROVISIONING');
  Update these steps every 12 months.
• C. create or replace security integration okta_provisioning
  type = scim
  scim_client = 'okta'
  run_as_role = 'OKTA PROVISIONER';
  Update this step every 6 months.
• D. 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.

Explanation: Only visible for TroytecDumps members. You can sign-up / login (it's free).

A retailer uses a TRANSACTIONS table (100M rows, 1.2 TB) that has been clustered by the STORE_ID column (varchar(50)). The vast majority of analyses on this table are grouped by STORE_ID to look at store performance.
There are 1000 stores operated by the retailer but most sales come from only 20 stores. The Administrator notes that most queries are currently experiencing poor pruning, with large amounts of bytes processed by even simple queries.
Why is this occurring?

• A. Sales across stores are not uniformly distributed.
• B. The STORE_ID should be numeric.
• C. The cardinality of the stores to transaction count ratio is too low to use the STORE_ID as a clustering key.
• D. The table is not big enough to take advantage of the clustering key.

Explanation: Only visible for TroytecDumps members. You can sign-up / login (it's free).

A Snowflake Administrator has a multi-cluster virtual warehouse and is using the Snowflake Business-Critical edition. The minimum number of clusters is set to 2 and the maximum number of clusters is set to 10. This configuration works well for the standard workload, rarely exceeding 5 running clusters. However, once a month the Administrator notes that there are a few complex long-running queries that are causing increased queue time and the warehouse reaches its maximum limit at 10 clusters.
Which solutions will address the issues happening once a month? (Choose two.)

• A. Have the group running the complex monthly queries use a separate appropriately-sized warehouse to support their workload.
• B. Increase the minimum number of clusters started in the multi-cluster configuration to 5.
• C. Use a task to increase the cluster size for the time period that the more complex queries are running and another task to reduce the size of the cluster once the complex queries complete.
• D. Examine the complex queries and determine if they can be made more efficient using clustering keys or materialized views.
• E. Increase the multi-cluster maximum to 20 or more clusters.

Explanation: Only visible for TroytecDumps members. You can sign-up / login (it's free).

An Administrator has been asked to support the company's application team need to build a loyalty program for its customers. The customer table contains Personal Identifiable Information (PII), and the application team's role is DEVELOPER.
CREATE TABLE customer_data (
customer_first_name string,
customer_last_name string,
customer_address string,
customer_email string,
... some other columns,
);
The application team would like to access the customer data, but the email field must be obfuscated.
How can the Administrator protect the sensitive information, while maintaining the usability of the data?

• A. Use the CURRENT_ROLE context function to integrate with a masking policy on the fields that contain sensitive data.
• B. Use the CURRENT_ROLE and CURRENT_USER context functions to integrate with a secure view and filter the sensitive data.
• C. Create a separate table for all the non-PII columns and grant the role DEVELOPER access to the new table.
• D. Create a view on the customer_data table to eliminate the email column by omitting it from the SELECT clause. Grant the role DEVELOPER access to the view.

Explanation: Only visible for TroytecDumps members. You can sign-up / login (it's free).