Snowflake SnowPro Core Practice Test 13
Question 120
For an original SnowPro Core educational scenario, consider: A deployment script references a table name without qualification and unexpectedly resolves a similarly named table in another schema. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations.
- Rely on an unspecified session context while running destructive DDL across environments.
- Check: Inspect edition, feature availability and limits for the named requirement in an isolated test account.
- Check: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session.
- Change: Use correct VARIANT path expressions with explicit type conversion and null-safe handling for heterogeneous attributes.
Explanation
Correct Answer
A:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. Acceptance: Scripts target the intended database.schema.object without cross-environment ambiguity.
D:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. Required intervention: Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations.
Incorrect Answers
B:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
C:Check: Inspect edition, feature availability and limits for the named requirement in an isolated test account. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
E:Change: Use correct VARIANT path expressions with explicit type conversion and null-safe handling for heterogeneous attributes. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
Question 121
A Snowflake engineer is examining this platform situation: A disposable staging table keeps historical recovery storage longer than required and raises storage costs. A proposed shortcut is: Convert all regulated production tables to transient to eliminate recovery storage. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use correct VARIANT path expressions with explicit type conversion and null-safe handling for heterogeneous attributes.
- Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window.
- Use permanent tables for durable recovery requirements and transient tables for suitable short-lived data with reduced recovery guarantees.
- Convert all regulated production tables to transient to eliminate recovery storage.
Explanation
Correct Answer
C:Validate the premise using: Compare table type, data-retention parameter, recovery needs and storage usage before conversion. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:Use correct VARIANT path expressions with explicit type conversion and null-safe handling for heterogeneous attributes. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
B:Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
D:Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
Question 122
A Snowflake implementation review finds: A disposable staging table keeps historical recovery storage longer than required and raises storage costs. The team proposes: Use permanent tables for durable recovery requirements and transient tables for suitable short-lived data with reduced recovery guarantees. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Specialized warehouse types provide different memory-to-compute characteristics and cost profiles; they are not universally preferable for SQL reporting.
- Zero-copy clones initially share existing micro-partitions, while subsequent modifications create independent data where changes occur.
- Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
- Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
Explanation
Correct Answer
C:Relevant validation before approval: Compare table type, data-retention parameter, recovery needs and storage usage before conversion. Demonstrable success requires: Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Snowpark-optimized warehouse selection) rather than the documented Permanent versus transient table retention decision.
B:Zero-copy clones initially share existing micro-partitions, while subsequent modifications create independent data where changes occur. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
D:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
Question 123
The data platform team has not yet approved changes. Current evidence indicates: A disposable staging table keeps historical recovery storage longer than required and raises storage costs. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Review catalog choice, external volume, object storage paths and metadata refresh requirements.
- Correlate cluster activity, queue lengths and hourly metering with workload peaks and lulls.
- Compare table type, data-retention parameter, recovery needs and storage usage before conversion.
- Create a controlled clone, compare initial storage and query results, then modify only the clone.
Explanation
Correct Answer
C:Confirm afterward that: Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection. Applied case: A disposable staging table keeps historical recovery storage longer than required and raises storage costs.
Incorrect Answers
A:Review catalog choice, external volume, object storage paths and metadata refresh requirements. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
B:Correlate cluster activity, queue lengths and hourly metering with workload peaks and lulls. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
D:Create a controlled clone, compare initial storage and query results, then modify only the clone. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
Question 124
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A disposable staging table keeps historical recovery storage longer than required and raises storage costs. 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.
- Approved use cases generate useful drafts without bypassing classification or uncritically treating model output as factual truth.
- Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection.
- Each consumer processes only its authorized new changes without missing events due to another consumer's offset.
- Data remains queryable after one warehouse stops and a different authorized warehouse can process it.
Explanation
Correct Answer
B:Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Approved use cases generate useful drafts without bypassing classification or uncritically treating model output as factual truth. A disposable staging table keeps historical recovery storage longer than required and raises storage costs.
C:Each consumer processes only its authorized new changes without missing events due to another consumer's offset. A disposable staging table keeps historical recovery storage longer than required and raises storage costs.
D:Data remains queryable after one warehouse stops and a different authorized warehouse can process it. A disposable staging table keeps historical recovery storage longer than required and raises storage costs.
Question 125
An implementation sign-off request identifies the following problem: A disposable staging table keeps historical recovery storage longer than required and raises storage costs. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Use permanent tables for durable recovery requirements and transient tables for suitable short-lived data with reduced recovery guarantees. Verify: Compare table type, data-retention parameter, recovery needs and storage usage before conversion.
- Change: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. Verify: Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
- Change: Use correct VARIANT path expressions with explicit type conversion and null-safe handling for heterogeneous attributes. Verify: Inspect raw PARSE_JSON output, key names, TYPEOF and TRY_TO_NUMBER results on representative records.
- Change: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows. Verify: Examine task graph history, predecessor states, warehouse permissions and failure handling.
Explanation
Correct Answer
A:The change is successful only when: Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection.
Incorrect Answers
B:Change: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
C:Change: Use correct VARIANT path expressions with explicit type conversion and null-safe handling for heterogeneous attributes. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
D:Change: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
Question 126
A Snowflake engineer is examining this platform situation: An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options. A proposed shortcut is: Convert all regulated production tables to transient to eliminate recovery storage. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use supported CLONE operations for a point-in-time logical snapshot and treat later changes to source and clone as separate.
- Use permanent tables for durable recovery requirements and transient tables for suitable short-lived data with reduced recovery guarantees.
- Convert all regulated production tables to transient to eliminate recovery storage.
- Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute.
Explanation
Correct Answer
B:Validate the premise using: Compare table type, data-retention parameter, recovery needs and storage usage before conversion. The required acceptance condition is: Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection.
Incorrect Answers
A:Use supported CLONE operations for a point-in-time logical snapshot and treat later changes to source and clone as separate. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
C:Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings. Use this instead: Use permanent tables for durable recovery requirements and transient tables for suitable short-lived data with reduced recovery guarantees.
D:Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
Question 127
A Snowflake implementation review finds: An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options. The team proposes: Use permanent tables for durable recovery requirements and transient tables for suitable short-lived data with reduced recovery guarantees. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Stages store files and directory tables expose metadata; a file's existence alone does not transform its contents into structured table rows.
- Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
- Snowflake editions have different availability and limits for selected features; architectural claims must match the purchased edition and current documentation.
- Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
Explanation
Correct Answer
B:Relevant validation before approval: Compare table type, data-retention parameter, recovery needs and storage usage before conversion. This principle explains the proposed technical approach, which is: Use permanent tables for durable recovery requirements and transient tables for suitable short-lived data with reduced recovery guarantees.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Unstructured data and directory metadata) rather than the documented Permanent versus transient table retention decision.
C:This option addresses a different Snowflake technical topic (Snowflake editions and feature entitlements) rather than the documented Permanent versus transient table retention decision.
D:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options.
Question 128
The data platform team has not yet approved changes. Current evidence indicates: An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare table type, data-retention parameter, recovery needs and storage usage before conversion.
- Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
- Compare access pattern, index availability, concurrency, constraint enforcement and compute cost.
- Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session.
Explanation
Correct Answer
A:Confirm afterward that: Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection. Applied case: An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options.
Incorrect Answers
B:Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
C:Compare access pattern, index availability, concurrency, constraint enforcement and compute cost. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
D:Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
Question 129
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options. 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.
- Each intended array element appears as a queryable row while empty or malformed payloads are handled deliberately.
- Downstream work starts only after its required predecessor succeeds and failures are visible to operators.
- The peak workload completes with reduced queuing while the cluster count contracts after demand subsides.
- Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection.
Explanation
Correct Answer
D:Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings. Applied case: An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (FLATTEN on array elements) rather than the documented Permanent versus transient table retention decision.
B:Downstream work starts only after its required predecessor succeeds and failures are visible to operators. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
C:The peak workload completes with reduced queuing while the cluster count contracts after demand subsides. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
Question 130
For an original SnowPro Core educational scenario, consider: An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Compare table type, data-retention parameter, recovery needs and storage usage before conversion.
- Check: Inspect queued overload time, cluster count, concurrency and credit usage during a realistic peak.
- Change: Use permanent tables for durable recovery requirements and transient tables for suitable short-lived data with reduced recovery guarantees.
- Change: Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window.
- Convert all regulated production tables to transient to eliminate recovery storage.
Explanation
Correct Answer
A:Acceptance: Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection. Applied case: An audit dataset is moved to a transient table merely to save storage despite needing the strongest available recovery options.
C:Acceptance: Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection. Evidence: Compare table type, data-retention parameter, recovery needs and storage usage before conversion.
Incorrect Answers
B:Check: Inspect queued overload time, cluster count, concurrency and credit usage during a realistic peak. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
D:Change: Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window. Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
E:Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings. Distinguish the two approaches by checking: Compare table type, data-retention parameter, recovery needs and storage usage before conversion.
