Snowflake SnowPro Core Practice Test 12
Question 110
For an original SnowPro Core educational scenario, consider: A failover plan expects a Snowflake account in a second region to use the primary region's data automatically. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Compare account identifiers, regions, sharing or replication configuration and permitted data paths.
- Change: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
- Check: Inspect raw PARSE_JSON output, key names, TYPEOF and TRY_TO_NUMBER results on representative records.
- Treat all Snowflake accounts globally as one common set of tables and warehouses by default.
- Change: Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access.
Explanation
Correct Answer
A:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Acceptance: Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior.
E:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Applied case: A failover plan expects a Snowflake account in a second region to use the primary region's data automatically.
Incorrect Answers
B:Change: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
C:Check: Inspect raw PARSE_JSON output, key names, TYPEOF and TRY_TO_NUMBER results on representative records. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
D:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Distinguish the two approaches by checking: Compare account identifiers, regions, sharing or replication configuration and permitted data paths.
Question 111
A Snowflake engineer is examining this platform situation: An analyst creates SALES in the wrong schema because the current database context points to a development environment. A proposed shortcut is: Rely on an unspecified session context while running destructive DDL across environments. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use appropriate staged file storage, directory metadata and supported unstructured file references or processing functions as needed.
- Rely on an unspecified session context while running destructive DDL across environments.
- Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
- Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations.
Explanation
Correct Answer
D:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. Applied case: An analyst creates SALES in the wrong schema because the current database context points to a development environment.
Incorrect Answers
A:Use appropriate staged file storage, directory metadata and supported unstructured file references or processing functions as needed. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
B:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
C:Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
Question 112
A Snowflake implementation review finds: An analyst creates SALES in the wrong schema because the current database context points to a development environment. The team proposes: Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
- Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
- Snowpark DataFrame transformations are generally lazily composed into executable plans and can avoid pulling full datasets into a local client.
- Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
Explanation
Correct Answer
D:Relevant validation before approval: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session. Applied case: An analyst creates SALES in the wrong schema because the current database context points to a development environment.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Permanent versus transient table retention) rather than the documented Database, schema and object hierarchy decision.
B:This option addresses a different Snowflake technical topic (Hybrid tables and transactional constraints) rather than the documented Database, schema and object hierarchy decision.
C:This option addresses a different Snowflake technical topic (Snowpark DataFrame execution) rather than the documented Database, schema and object hierarchy decision.
Question 113
The data platform team has not yet approved changes. Current evidence indicates: An analyst creates SALES in the wrong schema because the current database context points to a development environment. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Validate path selection, output row counts, INDEX and VALUE on arrays including empty and missing cases.
- Examine task graph history, predecessor states, warehouse permissions and failure handling.
- Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session.
- Create a controlled clone, compare initial storage and query results, then modify only the clone.
Explanation
Correct Answer
C:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. Confirm afterward that: Scripts target the intended database.schema.object without cross-environment ambiguity.
Incorrect Answers
A:Validate path selection, output row counts, INDEX and VALUE on arrays including empty and missing cases. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
B:Examine task graph history, predecessor states, warehouse permissions and failure handling. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
D:Create a controlled clone, compare initial storage and query results, then modify only the clone. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
Question 114
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An analyst creates SALES in the wrong schema because the current database context points to a development environment. 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.
- Cost analysis and architecture diagrams identify cloud services and warehouse activity as distinct components.
- Both interactive and automated users access only the authorized objects through the correct interfaces.
- Scripts target the intended database.schema.object without cross-environment ambiguity.
- Data remains queryable after one warehouse stops and a different authorized warehouse can process it.
Explanation
Correct Answer
C:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Cost analysis and architecture diagrams identify cloud services and warehouse activity as distinct components. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
B:Both interactive and automated users access only the authorized objects through the correct interfaces. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
D:Data remains queryable after one warehouse stops and a different authorized warehouse can process it. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
Question 115
An implementation sign-off request identifies the following problem: An analyst creates SALES in the wrong schema because the current database context points to a development environment. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations. Verify: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session.
- 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.
- Change: Select Information Schema or ACCOUNT_USAGE views based on required object scope, privileges, history and documented latency. Verify: Compare requested time window, privileges, ingestion lag and query history against a sample event.
- 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
A:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. The change is successful only when: Scripts target the intended database.schema.object without cross-environment ambiguity.
Incorrect Answers
B:Change: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
C:Change: Select Information Schema or ACCOUNT_USAGE views based on required object scope, privileges, history and documented latency. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
D:Change: Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
Question 116
A Snowflake engineer is examining this platform situation: A deployment script references a table name without qualification and unexpectedly resolves a similarly named table in another schema. A proposed shortcut is: Rely on an unspecified session context while running destructive DDL across environments. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Rely on an unspecified session context while running destructive DDL across environments.
- Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements.
- Use correct VARIANT path expressions with explicit type conversion and null-safe handling for heterogeneous attributes.
- Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations.
Explanation
Correct Answer
D:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. Applied case: A deployment script references a table name without qualification and unexpectedly resolves a similarly named table in another schema.
Incorrect Answers
A:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. Use this instead: Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations.
B:Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
C: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 117
A Snowflake implementation review finds: A deployment script references a table name without qualification and unexpectedly resolves a similarly named table in another schema. The team proposes: Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations. 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.
- Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
- Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
- Zero-copy clones initially share existing micro-partitions, while subsequent modifications create independent data where changes occur.
Explanation
Correct Answer
B:Relevant validation before approval: Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session. Applied case: A deployment script references a table name without qualification and unexpectedly resolves a similarly named table in another schema.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Snowpark-optimized warehouse selection) rather than the documented Database, schema and object hierarchy decision.
C:Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
D:Zero-copy clones initially share existing micro-partitions, while subsequent modifications create independent data where changes occur. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
Question 118
The data platform team has not yet approved changes. Current evidence indicates: A deployment script references a table name without qualification and unexpectedly resolves a similarly named table in another schema. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Reproduce creation, querying and session close using two independent connections.
- Inspect partition statistics and query profile scans before and after relevant data layout changes.
- Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session.
- Compare QUERY_HISTORY warehouse identifiers, queued time and load before and after changing session warehouse assignments.
Explanation
Correct Answer
C:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. This check tests the actual data, compute or access boundary before an operationally risky change.
Incorrect Answers
A:Reproduce creation, querying and session close using two independent connections. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
B:Inspect partition statistics and query profile scans before and after relevant data layout changes. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
D:Compare QUERY_HISTORY warehouse identifiers, queued time and load before and after changing session warehouse assignments. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
Question 119
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A deployment script references a table name without qualification and unexpectedly resolves a similarly named table in another schema. 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 approved design relies only on supported capabilities or explicitly plans the necessary edition change.
- Scripts target the intended database.schema.object without cross-environment ambiguity.
- Monitoring reports show expected data at the promised freshness and scope without misinterpreting latency as absence.
- Each intended array element appears as a queryable row while empty or malformed payloads are handled deliberately.
Explanation
Correct Answer
B:Tables and views live in schemas within databases; session context determines resolution of unqualified object names. The approved implementation step was: Set explicit current database and schema or use fully qualified identifiers for deployment-sensitive operations.
Incorrect Answers
A:The approved design relies only on supported capabilities or explicitly plans the necessary edition change. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
C:Monitoring reports show expected data at the promised freshness and scope without misinterpreting latency as absence. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
D:Each intended array element appears as a queryable row while empty or malformed payloads are handled deliberately. Tables and views live in schemas within databases; session context determines resolution of unqualified object names.
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.
