Snowflake SnowPro Core Practice Test 23
Question 220
For an original SnowPro Core educational scenario, consider: An architect claims an Iceberg table uses the same Snowflake-controlled internal storage as every native table. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute.
- Check: Review warehouse configuration, idle duration and metered credit history around overnight gaps.
- Change: Design a supported Snowflake Iceberg table with its external cloud data and metadata location and appropriate catalog configuration.
- Move all Iceberg files into a warehouse's ephemeral local disk and bypass table metadata.
- Check: Review catalog choice, external volume, object storage paths and metadata refresh requirements.
Explanation
Correct Answer
C:Iceberg tables use external cloud object storage and Iceberg metadata rather than Snowflake's native managed storage layout. Acceptance: A governed Iceberg table can be queried with supported capabilities while its files remain in the configured external location.
E:Iceberg tables use external cloud object storage and Iceberg metadata rather than Snowflake's native managed storage layout. Required intervention: Design a supported Snowflake Iceberg table with its external cloud data and metadata location and appropriate catalog configuration.
Incorrect Answers
A:Change: Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute. Iceberg tables use external cloud object storage and Iceberg metadata rather than Snowflake's native managed storage layout.
B:Check: Review warehouse configuration, idle duration and metered credit history around overnight gaps. Iceberg tables use external cloud object storage and Iceberg metadata rather than Snowflake's native managed storage layout.
D:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Iceberg tables use external cloud object storage and Iceberg metadata rather than Snowflake's native managed storage layout.
Question 221
A Snowflake engineer is examining this platform situation: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions. A proposed shortcut is: Assume an ordinary analytical table enforces every primary and foreign key constraint by default. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans.
- Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute.
- Assume an ordinary analytical table enforces every primary and foreign key constraint by default.
- Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
Explanation
Correct Answer
A:The required acceptance condition is: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage. Applied case: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions.
Incorrect Answers
B:Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
C:Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
D:Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions.
Question 222
A Snowflake implementation review finds: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions. The team proposes: Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Iceberg tables use external cloud object storage and Iceberg metadata rather than Snowflake's native managed storage layout.
- Snowflake's legacy notebook experience is being superseded by Notebooks in Workspaces; availability and workflows depend on account rollout and current documentation.
- VARIANT can hold semi-structured values and path-based access, while typed columns support explicit relational validation and calculations.
- Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
Explanation
Correct Answer
D:Demonstrable success requires: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage. Applied case: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions.
Incorrect Answers
A:Iceberg tables use external cloud object storage and Iceberg metadata rather than Snowflake's native managed storage layout. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
B:Snowflake's legacy notebook experience is being superseded by Notebooks in Workspaces; availability and workflows depend on account rollout and current documentation. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
C:VARIANT can hold semi-structured values and path-based access, while typed columns support explicit relational validation and calculations. A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions.
Question 223
The data platform team has not yet approved changes. Current evidence indicates: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare QUERY_HISTORY warehouse identifiers, queued time and load before and after changing session warehouse assignments.
- Compare access pattern, index availability, concurrency, constraint enforcement and compute cost.
- Inspect execution history before and after actions such as collect or write and compare data transfer size.
- Review warehouse configuration, idle duration and metered credit history around overnight gaps.
Explanation
Correct Answer
B:Confirm afterward that: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage. Applied case: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions.
Incorrect Answers
A:Compare QUERY_HISTORY warehouse identifiers, queued time and load before and after changing session warehouse assignments. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
C:Inspect execution history before and after actions such as collect or write and compare data transfer size. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
D:Review warehouse configuration, idle duration and metered credit history around overnight gaps. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
Question 224
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions. 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.
- Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection.
- Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage.
- Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior.
- Scripts target the intended database.schema.object without cross-environment ambiguity.
Explanation
Correct Answer
B:Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads. Applied case: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions.
Incorrect Answers
A:Staging data meets low-cost lifecycle goals while critical source-of-record data retains required recovery protection. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
C:Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
D:Scripts target the intended database.schema.object without cross-environment ambiguity. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
Question 225
An implementation sign-off request identifies the following problem: A small order-entry app needs low-latency row lookups, enforced uniqueness and referential integrity for operational transactions. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- 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: 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: 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: Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules. Verify: Compare QUERY_HISTORY warehouse identifiers, queued time and load before and after changing session warehouse assignments.
Explanation
Correct Answer
B:The change is successful only when: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage.
Incorrect Answers
A:Change: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
C:This option addresses a different Snowflake technical topic (Micro-partitioned columnar table storage) rather than the documented Hybrid tables and transactional constraints decision.
D:Change: Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
Question 226
A Snowflake engineer is examining this platform situation: An analytics team chooses a hybrid table solely to accelerate a petabyte-scale aggregation with no point-lookup or transaction need. A proposed shortcut is: Assume an ordinary analytical table enforces every primary and foreign key constraint by default. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Select Snowsight for suitable interactive tasks and supported Snowflake connectors, drivers or CLI for automated access.
- Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans.
- Assume an ordinary analytical table enforces every primary and foreign key constraint by default.
- Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
Explanation
Correct Answer
B:The required acceptance condition is: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Snowsight and programmatic tools) rather than the documented Hybrid tables and transactional constraints decision.
C:Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads. Use this instead: Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans.
D:This option addresses a different Snowflake technical topic (Warehouse resizing for resource-intensive queries) rather than the documented Hybrid tables and transactional constraints decision.
Question 227
A Snowflake implementation review finds: An analytics team chooses a hybrid table solely to accelerate a petabyte-scale aggregation with no point-lookup or transaction need. The team proposes: Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
- Transient tables forgo Fail-safe; permanent tables generally support both Time Travel and Fail-safe subject to edition and object retention settings.
- Snowflake persists managed data outside a particular warehouse while cloud services coordinate authentication, metadata and optimization and warehouses execute work.
- Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
Explanation
Correct Answer
D:Demonstrable success requires: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage. This principle explains the proposed technical approach, which is: Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans.
Incorrect Answers
A:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
B: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.
C:This option addresses a different Snowflake technical topic (Three-layer Snowflake architecture) rather than the documented Hybrid tables and transactional constraints decision.
Question 228
The data platform team has not yet approved changes. Current evidence indicates: An analytics team chooses a hybrid table solely to accelerate a petabyte-scale aggregation with no point-lookup or transaction need. 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.
- Compare account identifiers, regions, sharing or replication configuration and permitted data paths.
- Compare the account's notebook navigation, supported runtimes, role access and legacy migration capability.
- Compare access pattern, index availability, concurrency, constraint enforcement and compute cost.
Explanation
Correct Answer
D:Confirm afterward that: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage. Applied case: An analytics team chooses a hybrid table solely to accelerate a petabyte-scale aggregation with no point-lookup or transaction need.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (FLATTEN on array elements) rather than the documented Hybrid tables and transactional constraints decision.
B:Compare account identifiers, regions, sharing or replication configuration and permitted data paths. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
C:Compare the account's notebook navigation, supported runtimes, role access and legacy migration capability. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
Question 229
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An analytics team chooses a hybrid table solely to accelerate a petabyte-scale aggregation with no point-lookup or transaction need. 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.
- A governed Iceberg table can be queried with supported capabilities while its files remain in the configured external location.
- Intermediate results are isolated to the working session and durable outputs remain accessible afterward.
- Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage.
- Each consumer processes only its authorized new changes without missing events due to another consumer's offset.
Explanation
Correct Answer
C:Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:A governed Iceberg table can be queried with supported capabilities while its files remain in the configured external location. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
B:Intermediate results are isolated to the working session and durable outputs remain accessible afterward. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
D:This option addresses a different Snowflake technical topic (Streams for change data capture) rather than the documented Hybrid tables and transactional constraints decision.
Question 230
For an original SnowPro Core educational scenario, consider: An analytics team chooses a hybrid table solely to accelerate a petabyte-scale aggregation with no point-lookup or transaction need. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets.
- Check: Create a controlled clone, compare initial storage and query results, then modify only the clone.
- Check: Compare access pattern, index availability, concurrency, constraint enforcement and compute cost.
- Change: Evaluate hybrid tables for supported transactional, index-based row workloads and standard tables for large-scale analytic scans.
- Assume an ordinary analytical table enforces every primary and foreign key constraint by default.
Explanation
Correct Answer
C:Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads. Acceptance: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage.
D:Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads. Applied case: An analytics team chooses a hybrid table solely to accelerate a petabyte-scale aggregation with no point-lookup or transaction need.
Incorrect Answers
A:Change: Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
B:Check: Create a controlled clone, compare initial storage and query results, then modify only the clone. Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
E:Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads. Assume an ordinary analytical table enforces every primary and foreign key constraint by default.
