Snowflake SnowPro Core Practice Test 6
Question 50
For an original SnowPro Core educational scenario, consider: A development team manually resumes its warehouse every morning after disabling automatic resume to reduce spending. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Check retention settings, query timestamp and a before/after row sample before restoring.
- Check: Review warehouse configuration, idle duration and metered credit history around overnight gaps.
- Change: Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules.
- Change: Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing.
- Keep a development warehouse running around the clock because stored tables become unavailable during suspension.
Explanation
Correct Answer
B:An idle warehouse can be suspended to stop compute consumption and resumed when authorized work requires it. Required intervention: Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing.
D:An idle warehouse can be suspended to stop compute consumption and resumed when authorized work requires it. Evidence: Review warehouse configuration, idle duration and metered credit history around overnight gaps.
Incorrect Answers
A:Check: Check retention settings, query timestamp and a before/after row sample before restoring. An idle warehouse can be suspended to stop compute consumption and resumed when authorized work requires it.
C:Change: Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules. An idle warehouse can be suspended to stop compute consumption and resumed when authorized work requires it.
E:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. An idle warehouse can be suspended to stop compute consumption and resumed when authorized work requires it.
Question 51
A Snowflake engineer is examining this platform situation: A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits. A proposed shortcut is: Set minimum and maximum clusters to the highest value without observing demand or cost. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Set minimum and maximum clusters to the highest value without observing demand or cost.
- Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
- Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements.
- Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
Explanation
Correct Answer
C:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
B:Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
D:Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary. A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits.
Question 52
A Snowflake implementation review finds: A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits. The team proposes: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Temporary tables exist only for their creating session and are removed when the session ends.
- Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
- Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
- Additional clusters can reduce queuing under concurrency, but do not inherently accelerate one slow query.
Explanation
Correct Answer
C:Demonstrable success requires: Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity. This principle explains the proposed technical approach, which is: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements.
Incorrect Answers
A:Temporary tables exist only for their creating session and are removed when the session ends. A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits.
B:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
D:Additional clusters can reduce queuing under concurrency, but do not inherently accelerate one slow query. A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits.
Question 53
The data platform team has not yet approved changes. Current evidence indicates: A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare account identifiers, regions, sharing or replication configuration and permitted data paths.
- Inspect execution history before and after actions such as collect or write and compare data transfer size.
- Correlate cluster activity, queue lengths and hourly metering with workload peaks and lulls.
- Validate path selection, output row counts, INDEX and VALUE on arrays including empty and missing cases.
Explanation
Correct Answer
C:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. Confirm afterward that: Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity.
Incorrect Answers
A:Compare account identifiers, regions, sharing or replication configuration and permitted data paths. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
B:This option addresses a different Snowflake technical topic (Snowpark DataFrame execution) rather than the documented Warehouse scaling mode and minimum clusters decision.
D:Validate path selection, output row counts, INDEX and VALUE on arrays including empty and missing cases. A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits.
Question 54
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits. The service owner needs positive and negative results and evidence that legitimate data workflows still function. Which acceptance result demonstrates correct platform behavior without disrupting authorized workflows? Select ONE best answer.
- Target queries finish within agreed latency while extra compute cost remains justified.
- A governed Iceberg table can be queried with supported capabilities while its files remain in the configured external location.
- Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity.
- Cost analysis and architecture diagrams identify cloud services and warehouse activity as distinct components.
Explanation
Correct Answer
C:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Target queries finish within agreed latency while extra compute cost remains justified. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
B:A governed Iceberg table can be queried with supported capabilities while its files remain in the configured external location. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
D:Cost analysis and architecture diagrams identify cloud services and warehouse activity as distinct components. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
Question 55
An implementation sign-off request identifies the following problem: A variable daytime dashboard load keeps extra clusters running longer than needed and consumes excess credits. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Design a supported Snowflake Iceberg table with its external cloud data and metadata location and appropriate catalog configuration. Verify: Review catalog choice, external volume, object storage paths and metadata refresh requirements.
- Change: Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans. Verify: Compare access pattern, index availability, concurrency, constraint enforcement and compute cost.
- Change: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements. Verify: Correlate cluster activity, queue lengths and hourly metering with workload peaks and lulls.
- Change: Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing. Verify: Review warehouse configuration, idle duration and metered credit history around overnight gaps.
Explanation
Correct Answer
C:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. The change is successful only when: Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity.
Incorrect Answers
A:Change: Design a supported Snowflake Iceberg table with its external cloud data and metadata location and appropriate catalog configuration. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
B:Change: Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans.
D:Change: Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
Question 56
A Snowflake engineer is examining this platform situation: An operations team sets the minimum cluster count to peak capacity even during hours without demand. A proposed shortcut is: Set minimum and maximum clusters to the highest value without observing demand or cost. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Set minimum and maximum clusters to the highest value without observing demand or cost.
- Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing.
- Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
- Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements.
Explanation
Correct Answer
D:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. Applied case: An operations team sets the minimum cluster count to peak capacity even during hours without demand.
Incorrect Answers
A:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. Use this instead: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements.
B:Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
C:Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
Question 57
A Snowflake implementation review finds: An operations team sets the minimum cluster count to peak capacity even during hours without demand. The team proposes: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
- UI and programmatic clients connect to the same governed account but differ in interaction, automation and authentication patterns.
- Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
- Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition.
Explanation
Correct Answer
A:Demonstrable success requires: Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity. Applied case: An operations team sets the minimum cluster count to peak capacity even during hours without demand.
Incorrect Answers
B:This option addresses a different Snowflake technical topic (Snowsight and programmatic tools) rather than the documented Warehouse scaling mode and minimum clusters decision.
C:Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
D:Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
Question 58
The data platform team has not yet approved changes. Current evidence indicates: An operations team sets the minimum cluster count to peak capacity even during hours without demand. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Correlate cluster activity, queue lengths and hourly metering with workload peaks and lulls.
- Test permissions, sample outputs, cost consumption, sensitive-data handling and false assertions against known cases.
- Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs.
- Review warehouse configuration, idle duration and metered credit history around overnight gaps.
Explanation
Correct Answer
A:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. This check tests the actual data, compute or access boundary before an operationally risky change.
Incorrect Answers
B:Test permissions, sample outputs, cost consumption, sensitive-data handling and false assertions against known cases. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
C:Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
D:Review warehouse configuration, idle duration and metered credit history around overnight gaps. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
Question 59
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An operations team sets the minimum cluster count to peak capacity even during hours without demand. The service owner needs positive and negative results and evidence that legitimate data workflows still function. Which acceptance result demonstrates correct platform behavior without disrupting authorized workflows? Select ONE best answer.
- The recovery runbook specifies the correct mechanism and realistic timing for historical incidents.
- Scripts target the intended database.schema.object without cross-environment ambiguity.
- Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity.
- Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection.
Explanation
Correct Answer
C:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. The approved implementation step was: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements.
Incorrect Answers
A:The recovery runbook specifies the correct mechanism and realistic timing for historical incidents. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
B:Scripts target the intended database.schema.object without cross-environment ambiguity. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
D:Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
Question 60
For an original SnowPro Core educational scenario, consider: An operations team sets the minimum cluster count to peak capacity even during hours without demand. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements.
- Check: Review warehouse configuration, idle duration and metered credit history around overnight gaps.
- Set minimum and maximum clusters to the highest value without observing demand or cost.
- Change: Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets.
- Check: Correlate cluster activity, queue lengths and hourly metering with workload peaks and lulls.
Explanation
Correct Answer
A:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. Acceptance: Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity.
E:Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost. Required intervention: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements.
Incorrect Answers
B:Check: Review warehouse configuration, idle duration and metered credit history around overnight gaps. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
C:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
D:Change: Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets. Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
