Snowflake SnowPro Core Practice Test 3
Question 20
For an original SnowPro Core educational scenario, consider: A company expects renaming two virtual warehouses to isolate workloads while both teams still submit to the same warehouse object. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Inspect edition, feature availability and limits for the named requirement in an isolated test account.
- Check: Compare QUERY_HISTORY warehouse identifiers, queued time and load before and after changing session warehouse assignments.
- Change: Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access.
- Duplicate every source table for each team merely to obtain compute isolation.
- Change: Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules.
Explanation
Correct Answer
B:Distinct Snowflake warehouses have independent compute resources, so separating workloads reduces resource contention without copying database storage. Acceptance: Batch workloads no longer consume the interactive warehouse's slots while both read consistent shared tables.
E:Distinct Snowflake warehouses have independent compute resources, so separating workloads reduces resource contention without copying database storage. Evidence: Compare QUERY_HISTORY warehouse identifiers, queued time and load before and after changing session warehouse assignments.
Incorrect Answers
A:Check: Inspect edition, feature availability and limits for the named requirement in an isolated test account. Distinct Snowflake warehouses have independent compute resources, so separating workloads reduces resource contention without copying database storage.
C:Change: Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access. Distinct Snowflake warehouses have independent compute resources, so separating workloads reduces resource contention without copying database storage.
D:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Distinct Snowflake warehouses have independent compute resources, so separating workloads reduces resource contention without copying database storage.
Question 21
A Snowflake engineer is examining this platform situation: A single large aggregation spills to remote storage on an XS warehouse even when only one query is running. A proposed shortcut is: Add numerous multi-cluster replicas to fix one query's memory spill without evaluating vertical sizing. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Design a supported Snowflake Iceberg table with its external cloud data and metadata location and appropriate catalog configuration.
- Add numerous multi-cluster replicas to fix one query's memory spill without evaluating vertical sizing.
- Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
- Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute.
Explanation
Correct Answer
C:The required acceptance condition is: Target queries finish within agreed latency while extra compute cost remains justified. Applied case: A single large aggregation spills to remote storage on an XS warehouse even when only one query is running.
Incorrect Answers
A:Design a supported Snowflake Iceberg table with its external cloud data and metadata location and appropriate catalog configuration. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
B:Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
D:Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
Question 22
A Snowflake implementation review finds: A single large aggregation spills to remote storage on an XS warehouse even when only one query is running. The team proposes: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
- Specialized warehouse types provide different memory-to-compute characteristics and cost profiles; they are not universally preferable for SQL reporting.
- Stages store files and directory tables expose metadata; a file's existence alone does not transform its contents into structured table rows.
- Snowflake's legacy notebook experience is being superseded by Notebooks in Workspaces; availability and workflows depend on account rollout and current documentation.
Explanation
Correct Answer
A:Demonstrable success requires: Target queries finish within agreed latency while extra compute cost remains justified. This principle explains the proposed technical approach, which is: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
Incorrect Answers
B:This option addresses a different Snowflake technical topic (Snowpark-optimized warehouse selection) rather than the documented Warehouse resizing for resource-intensive queries decision.
C:Stages store files and directory tables expose metadata; a file's existence alone does not transform its contents into structured table rows. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
D:This option addresses a different Snowflake technical topic (Notebooks in Workspaces versus legacy notebooks) rather than the documented Warehouse resizing for resource-intensive queries decision.
Question 23
The data platform team has not yet approved changes. Current evidence indicates: A single large aggregation spills to remote storage on an XS warehouse even when only one query is running. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs.
- Check table persistence after warehouse suspension and trace a query through authorization, optimization and independent compute.
- Compare access pattern, index availability, concurrency, constraint enforcement and compute cost.
- Review catalog choice, external volume, object storage paths and metadata refresh requirements.
Explanation
Correct Answer
A:If confirmed, the proportionate intervention is: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Applied case: A single large aggregation spills to remote storage on an XS warehouse even when only one query is running.
Incorrect Answers
B:Check table persistence after warehouse suspension and trace a query through authorization, optimization and independent compute. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
C:Compare access pattern, index availability, concurrency, constraint enforcement and compute cost. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
D:Review catalog choice, external volume, object storage paths and metadata refresh requirements. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
Question 24
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A single large aggregation spills to remote storage on an XS warehouse even when only one query is running. 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.
- Valid nested values are extracted and malformed optional fields are flagged or safely handled.
- Scripts target the intended database.schema.object without cross-environment ambiguity.
- Approved use cases generate useful drafts without bypassing classification or uncritically treating model output as factual truth.
Explanation
Correct Answer
A:The approved implementation step was: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Applied case: A single large aggregation spills to remote storage on an XS warehouse even when only one query is running.
Incorrect Answers
B:Valid nested values are extracted and malformed optional fields are flagged or safely handled. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
C:Scripts target the intended database.schema.object without cross-environment ambiguity. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
D:Approved use cases generate useful drafts without bypassing classification or uncritically treating model output as factual truth. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
Question 25
An implementation sign-off request identifies the following problem: A single large aggregation spills to remote storage on an XS warehouse even when only one query is running. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism. Verify: Verify table type, historical retention expiration and documented support/recovery process before planning restoration.
- Change: Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute. Verify: Inspect execution history before and after actions such as collect or write and compare data transfer size.
- Change: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary. Verify: Inspect partition statistics and query profile scans before and after relevant data layout changes.
- Change: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Verify: Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs.
Explanation
Correct Answer
D:The change is successful only when: Target queries finish within agreed latency while extra compute cost remains justified.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Fail-safe purpose and operational limits) rather than the documented Warehouse resizing for resource-intensive queries decision.
B:Change: Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute.
C:This option addresses a different Snowflake technical topic (Micro-partitioned columnar table storage) rather than the documented Warehouse resizing for resource-intensive queries decision.
Question 26
A Snowflake engineer is examining this platform situation: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters. A proposed shortcut is: Add numerous multi-cluster replicas to fix one query's memory spill without evaluating vertical sizing. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
- Create appropriate streams to expose change data and give independently checkpointed consumers their own streams when needed.
- Use supported CLONE operations for a point-in-time logical snapshot and treat later changes to source and clone as separate.
- Add numerous multi-cluster replicas to fix one query's memory spill without evaluating vertical sizing.
Explanation
Correct Answer
A:The required acceptance condition is: Target queries finish within agreed latency while extra compute cost remains justified. Applied case: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters.
Incorrect Answers
B:Create appropriate streams to expose change data and give independently checkpointed consumers their own streams when needed. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
C:Use supported CLONE operations for a point-in-time logical snapshot and treat later changes to source and clone as separate. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
D:Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency. Use this instead: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
Question 27
A Snowflake implementation review finds: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters. The team proposes: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- An idle warehouse can be suspended to stop compute consumption and resumed when authorized work requires it.
- Snowflake editions have different availability and limits for selected features; architectural claims must match the purchased edition and current documentation.
- Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
- Stages store files and directory tables expose metadata; a file's existence alone does not transform its contents into structured table rows.
Explanation
Correct Answer
C:Demonstrable success requires: Target queries finish within agreed latency while extra compute cost remains justified. Applied case: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Warehouse auto-suspend and auto-resume) rather than the documented Warehouse resizing for resource-intensive queries decision.
B:Snowflake editions have different availability and limits for selected features; architectural claims must match the purchased edition and current documentation. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
D:Stages store files and directory tables expose metadata; a file's existence alone does not transform its contents into structured table rows. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
Question 28
The data platform team has not yet approved changes. Current evidence indicates: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs.
- Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
- Inspect stage file listings, directory table refresh and supported document-processing entry points.
- Compare access pattern, index availability, concurrency, constraint enforcement and compute cost.
Explanation
Correct Answer
A:If confirmed, the proportionate intervention is: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Applied case: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters.
Incorrect Answers
B:Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
C:Inspect stage file listings, directory table refresh and supported document-processing entry points. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
D:Compare access pattern, index availability, concurrency, constraint enforcement and compute cost. A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters.
Question 29
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters. 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.
- The source remains unchanged and a practical test clone is created without an immediate full physical duplication.
- Flexible payloads remain queryable and critical measures retain correct types rather than becoming ambiguous text.
- The peak workload completes with reduced queuing while the cluster count contracts after demand subsides.
Explanation
Correct Answer
A:The approved implementation step was: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Applied case: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters.
Incorrect Answers
B:The source remains unchanged and a practical test clone is created without an immediate full physical duplication. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
C:Flexible payloads remain queryable and critical measures retain correct types rather than becoming ambiguous text. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
D:The peak workload completes with reduced queuing while the cluster count contracts after demand subsides. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
Question 30
For an original SnowPro Core educational scenario, consider: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
- Check: Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs.
- Add numerous multi-cluster replicas to fix one query's memory spill without evaluating vertical sizing.
- Check: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session.
- Change: Design a supported Snowflake Iceberg table with its external cloud data and metadata location and appropriate catalog configuration.
Explanation
Correct Answer
A:Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency. Applied case: A reporting job suffers memory pressure during a complex join yet an engineer proposes adding only concurrency clusters.
B:Required intervention: Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
Incorrect Answers
C:Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency. Add numerous multi-cluster replicas to fix one query's memory spill without evaluating vertical sizing.
D:Check: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
E:Change: Design a supported Snowflake Iceberg table with its external cloud data and metadata location and appropriate catalog configuration. Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
