An Administrator needs to configure a virtual warehouse in Snowflake for a new use case with these details:
1. There will be 50-100 concurrent users running reports
2. Minimize costs based on the number of active users at a given time
3. The virtual warehouse should suspend and resume automatically based on user activity
Which configuration will meet these requirements?

• A. create or replace warehouse reporting_wh
  warehouse_size = medium
  max_cluster_count = 10
  scaling_policy = standard
  auto_suspend = 600
  auto_resume = true;
• B. create or replace warehouse reporting_wh
  warehouse_size = xxxlarge
  max_cluster_count = 10
  scaling_policy = standard
  auto_suspend = 600
  auto_resume = false;
• C. create or replace warehouse reporting_wh
  warehouse_size = xxxlarge
  auto_suspend = 60
  auto_resume = true;
• D. create or replace warehouse reporting_wh
  warehouse_size = medium
  auto_suspend = 600
  auto_resume = true;

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

An Administrator loads data into a staging table every day. Once loaded, users from several different departments perform transformations on the data and load it into different production tables.
How should the staging table be created and used to MINIMIZE storage costs and MAXIMIZE performance?

• A. Create it as a permanent table with a retention time of 0 days.
• B. Create it as a temporary table with a retention time of 0 days.
• C. Create it as an external table, which will not incur Time Travel costs.
• D. Create it as a transient table with a retention time of 0 days.

Explanation: Only visible for PremiumVCEDump 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 cardinality of the stores to transaction count ratio is too low to use the STORE_ID as a clustering key.
• C. The STORE_ID should be numeric.
• D. The table is not big enough to take advantage of the clustering key.

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

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 30 days and the schemas to 60 days.
• B. Set the data retention policy on the secondary database to 60 days.
• C. Set the data retention policy on the primary database to 60 days.
• D. Set the data retention policy on the schemas in the secondary database to 60 days.

Explanation: Only visible for PremiumVCEDump 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. Increase the minimum number of clusters started in the multi-cluster configuration to 5.
• B. Increase the multi-cluster maximum to 20 or more clusters.
• 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. Have the group running the complex monthly queries use a separate appropriately-sized warehouse to support their workload.

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