Snowflake SnowPro Core Practice Test 10
Question 90
For an original SnowPro Core educational scenario, consider: An architect says security checks and query compilation run entirely inside user-selected warehouses. 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.
- Check: Compare service-level billing and account usage with warehouse usage for the relevant reporting period.
- Change: Distinguish cloud-services-layer functions from virtual warehouse execution when analyzing processing and billable consumption.
- Change: Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window.
- Attribute all Snowflake charges solely to elapsed SQL warehouse runtime.
Explanation
Correct Answer
B:Required intervention: Distinguish cloud-services-layer functions from virtual warehouse execution when analyzing processing and billable consumption.
C:Evidence: Compare service-level billing and account usage with warehouse usage for the relevant reporting period.
Incorrect Answers
A:Check: Compare account identifiers, regions, sharing or replication configuration and permitted data paths. Snowflake-managed cloud services coordinate metadata, access decisions and query optimization independently of warehouse compute.
D:Change: Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window. Snowflake-managed cloud services coordinate metadata, access decisions and query optimization independently of warehouse compute.
E:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Applied case: An architect says security checks and query compilation run entirely inside user-selected warehouses.
Question 91
A Snowflake engineer is examining this platform situation: A data engineer wants to hand-create 100 MB file chunks inside Snowflake's standard managed table before inserts. A proposed shortcut is: Manually edit internal Snowflake micro-partition files to change table data. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Evaluate Snowpark-optimized warehouse configurations only for supported memory-intensive Snowpark operations with measured benefit.
- Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
- Manually edit internal Snowflake micro-partition files to change table data.
- Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window.
Explanation
Correct Answer
B:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:Evaluate Snowpark-optimized warehouse configurations only for supported memory-intensive Snowpark operations with measured benefit. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
C:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
D:Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
Question 92
A Snowflake implementation review finds: A data engineer wants to hand-create 100 MB file chunks inside Snowflake's standard managed table before inserts. The team proposes: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Semi-structured paths and types must match document structure; missing keys and invalid casts need intentional treatment.
- UI and programmatic clients connect to the same governed account but differ in interaction, automation and authentication patterns.
- Specialized warehouse types provide different memory-to-compute characteristics and cost profiles; they are not universally preferable for SQL reporting.
- Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
Explanation
Correct Answer
D:Relevant validation before approval: Inspect partition statistics and query profile scans before and after relevant data layout changes. This principle explains the proposed technical approach, which is: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Semi-structured path navigation) rather than the documented Micro-partitioned columnar table storage decision.
B:This option addresses a different Snowflake technical topic (Snowsight and programmatic tools) rather than the documented Micro-partitioned columnar table storage decision.
C:Specialized warehouse types provide different memory-to-compute characteristics and cost profiles; they are not universally preferable for SQL reporting. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
Question 93
The data platform team has not yet approved changes. Current evidence indicates: A data engineer wants to hand-create 100 MB file chunks inside Snowflake's standard managed table before inserts. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare access pattern, index availability, concurrency, constraint enforcement and compute cost.
- Inspect partition statistics and query profile scans before and after relevant data layout changes.
- Compare requested time window, privileges, ingestion lag and query history against a sample event.
- Validate path selection, output row counts, INDEX and VALUE on arrays including empty and missing cases.
Explanation
Correct Answer
B:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. If confirmed, the proportionate intervention is: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
Incorrect Answers
A:Compare access pattern, index availability, concurrency, constraint enforcement and compute cost. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
C:Compare requested time window, privileges, ingestion lag and query history against a sample event. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
D:Validate path selection, output row counts, INDEX and VALUE on arrays including empty and missing cases. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
Question 94
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A data engineer wants to hand-create 100 MB file chunks inside Snowflake's standard managed table before inserts. 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.
- Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior.
- A governed Iceberg table can be queried with supported capabilities while its files remain in the configured external location.
- Each consumer processes only its authorized new changes without missing events due to another consumer's offset.
- Queries operate over managed table storage and pruning reduces unnecessary scan work for selective predicates.
Explanation
Correct Answer
D:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. The approved implementation step was: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
Incorrect Answers
A:Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
B:A governed Iceberg table can be queried with supported capabilities while its files remain in the configured external location. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
C:Each consumer processes only its authorized new changes without missing events due to another consumer's offset. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
Question 95
An implementation sign-off request identifies the following problem: A data engineer wants to hand-create 100 MB file chunks inside Snowflake's standard managed table before inserts. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- 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: 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: Separate persistent cloud storage from independently provisioned warehouse compute and Snowflake-managed cloud services when designing the architecture. Verify: Check table persistence after warehouse suspension and trace a query through authorization, optimization and independent compute.
Explanation
Correct Answer
B:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. The change is successful only when: Queries operate over managed table storage and pruning reduces unnecessary scan work for selective predicates.
Incorrect Answers
A:Change: Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
C:Change: Select Information Schema or ACCOUNT_USAGE views based on required object scope, privileges, history and documented latency.
D:Change: Separate persistent cloud storage from independently provisioned warehouse compute and Snowflake-managed cloud services when designing the architecture.
Question 96
A Snowflake engineer is examining this platform situation: A developer expects an ordinary Snowflake table to persist rows as uncompressed CSV files on the warehouse node. A proposed shortcut is: Manually edit internal Snowflake micro-partition files to change table data. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Manually edit internal Snowflake micro-partition files to change table data.
- Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields.
- Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
- Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window.
Explanation
Correct Answer
C:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. Validate the premise using: Inspect partition statistics and query profile scans before and after relevant data layout changes.
Incorrect Answers
A:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. Use this instead: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
B:Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
D:Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window. A developer expects an ordinary Snowflake table to persist rows as uncompressed CSV files on the warehouse node.
Question 97
A Snowflake implementation review finds: A developer expects an ordinary Snowflake table to persist rows as uncompressed CSV files on the warehouse node. The team proposes: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
- Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
- Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition.
- Managed AI functions can operate within supported Snowflake services, but model output requires governance and validation rather than assumption of determinism.
Explanation
Correct Answer
A:Relevant validation before approval: Inspect partition statistics and query profile scans before and after relevant data layout changes. Demonstrable success requires: Queries operate over managed table storage and pruning reduces unnecessary scan work for selective predicates.
Incorrect Answers
B:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
C:Historical data versions remain queryable within Time Travel retention, which depends on object type, settings and edition. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
D:Managed AI functions can operate within supported Snowflake services, but model output requires governance and validation rather than assumption of determinism. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
Question 98
The data platform team has not yet approved changes. Current evidence indicates: A developer expects an ordinary Snowflake table to persist rows as uncompressed CSV files on the warehouse node. 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.
- Inspect partition statistics and query profile scans before and after relevant data layout changes.
- 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:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. Confirm afterward that: Queries operate over managed table storage and pruning reduces unnecessary scan work for selective predicates.
Incorrect Answers
A:Review catalog choice, external volume, object storage paths and metadata refresh requirements. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
C:Inspect execution history before and after actions such as collect or write and compare data transfer size. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
D:Review warehouse configuration, idle duration and metered credit history around overnight gaps. A developer expects an ordinary Snowflake table to persist rows as uncompressed CSV files on the warehouse node.
Question 99
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A developer expects an ordinary Snowflake table to persist rows as uncompressed CSV files on the warehouse node. 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.
- Batch workloads no longer consume the interactive warehouse's slots while both read consistent shared tables.
- Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior.
- Approved use cases generate useful drafts without bypassing classification or uncritically treating model output as factual truth.
- Queries operate over managed table storage and pruning reduces unnecessary scan work for selective predicates.
Explanation
Correct Answer
D:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Independent virtual warehouse workload isolation) rather than the documented Micro-partitioned columnar table storage decision.
B:Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. A developer expects an ordinary Snowflake table to persist rows as uncompressed CSV files on the warehouse node.
C:Approved use cases generate useful drafts without bypassing classification or uncritically treating model output as factual truth. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
Question 100
For an original SnowPro Core educational scenario, consider: A developer expects an ordinary Snowflake table to persist rows as uncompressed CSV files on the warehouse node. Select THREE compatible elements: a proper correction, a targeted diagnostic and an acceptance result.
- Check: Inspect partition statistics and query profile scans before and after relevant data layout changes.
- Check: Compare the job's memory failures, execution time, supported workload requirements and credits on both warehouse types.
- Result: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage.
- Result: Queries operate over managed table storage and pruning reduces unnecessary scan work for selective predicates.
- Change: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
- Change: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows.
Explanation
Correct Answer
A:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. Required intervention: Let Snowflake manage compressed columnar micro-partitions for native table data and use pruning-aware design where necessary.
D:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. Evidence: Inspect partition statistics and query profile scans before and after relevant data layout changes.
E:Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files. Acceptance: Queries operate over managed table storage and pruning reduces unnecessary scan work for selective predicates.
Incorrect Answers
B:Check: Compare the job's memory failures, execution time, supported workload requirements and credits on both warehouse types. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
C:Result: Operational lookups and constraints behave as required while bulk analytics use fit-for-purpose storage. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
F:Change: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows. Standard Snowflake table storage is automatically organized into immutable columnar micro-partitions and their metadata rather than manually managed warehouse files.
