Snowflake SnowPro Core Practice Test 11
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.
Question 101
A Snowflake engineer is examining this platform situation: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup. A proposed shortcut is: Treat all Snowflake accounts globally as one common set of tables and warehouses by default. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Treat all Snowflake accounts globally as one common set of tables and warehouses by default.
- Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets.
- Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access.
- Distinguish cloud-services-layer functions from virtual warehouse execution when analyzing processing and billable consumption.
Explanation
Correct Answer
C:The required acceptance condition is: Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. Applied case: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup.
Incorrect Answers
A:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
B:Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
D:Distinguish cloud-services-layer functions from virtual warehouse execution when analyzing processing and billable consumption. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Question 102
A Snowflake implementation review finds: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup. The team proposes: Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- UI and programmatic clients connect to the same governed account but differ in interaction, automation and authentication patterns.
- Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
- VARIANT can hold semi-structured values and path-based access, while typed columns support explicit relational validation and calculations.
- Information Schema and Snowflake shared-account usage views provide different metadata scopes and refresh characteristics.
Explanation
Correct Answer
B:Demonstrable success requires: Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. Applied case: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Snowsight and programmatic tools) rather than the documented Cross-region and cross-cloud account boundaries decision.
C:VARIANT can hold semi-structured values and path-based access, while typed columns support explicit relational validation and calculations. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
D:Information Schema and Snowflake shared-account usage views provide different metadata scopes and refresh characteristics. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Question 103
The data platform team has not yet approved changes. Current evidence indicates: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session.
- Compare the job's memory failures, execution time, supported workload requirements and credits on both warehouse types.
- Check retention settings, query timestamp and a before/after row sample before restoring.
- Compare account identifiers, regions, sharing or replication configuration and permitted data paths.
Explanation
Correct Answer
D:Confirm afterward that: Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. Applied case: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup.
Incorrect Answers
A:Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
B:Compare the job's memory failures, execution time, supported workload requirements and credits on both warehouse types. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
C:Check retention settings, query timestamp and a before/after row sample before restoring. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Question 104
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup. 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 source remains unchanged and a practical test clone is created without an immediate full physical duplication.
- 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.
- Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior.
Explanation
Correct Answer
D:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Applied case: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup.
Incorrect Answers
A:The source remains unchanged and a practical test clone is created without an immediate full physical duplication. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
B:Downstream work starts only after its required predecessor succeeds and failures are visible to operators. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
C:The peak workload completes with reduced queuing while the cluster count contracts after demand subsides. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Question 105
An implementation sign-off request identifies the following problem: An architect assumes a warehouse in one Snowflake account can execute directly against another account's private table without access-sharing setup. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- 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: Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access. Verify: Compare account identifiers, regions, sharing or replication configuration and permitted data paths.
- Change: Use appropriate staged file storage, directory metadata and supported unstructured file references or processing functions as needed. Verify: Inspect stage file listings, directory table refresh and supported document-processing entry points.
- Change: Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window. Verify: Check retention settings, query timestamp and a before/after row sample before restoring.
Explanation
Correct Answer
B:The change is successful only when: Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior.
Incorrect Answers
A:Change: Select Information Schema or ACCOUNT_USAGE views based on required object scope, privileges, history and documented latency. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
C:Change: Use appropriate staged file storage, directory metadata and supported unstructured file references or processing functions as needed. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
D:Change: Use supported Time Travel AT or BEFORE query and restore patterns within the object's applicable retention window. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Question 106
A Snowflake engineer is examining this platform situation: A failover plan expects a Snowflake account in a second region to use the primary region's data automatically. A proposed shortcut is: Treat all Snowflake accounts globally as one common set of tables and warehouses by default. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Treat all Snowflake accounts globally as one common set of tables and warehouses by default.
- Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits.
- Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields.
- Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access.
Explanation
Correct Answer
D:The required acceptance condition is: Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Use this instead: Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access.
B:Test a larger warehouse size for the memory- or compute-bound individual query and review profile improvement versus credits. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
C:Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Question 107
A Snowflake implementation review finds: A failover plan expects a Snowflake account in a second region to use the primary region's data automatically. The team proposes: Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access. 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.
- Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency.
- Hybrid tables favor low-latency indexed operations and enforced relational constraints, whereas ordinary Snowflake tables are optimized for analytical workloads.
- Streams track table change offsets; consuming a stream in committed DML advances its position, so independent consumers need separate offsets.
Explanation
Correct Answer
A:Demonstrable success requires: Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. This principle explains the proposed technical approach, which is: Model account and region boundaries and plan supported sharing or replication/failover for cross-boundary access.
Incorrect Answers
B:Resizing generally provides more per-cluster resources for demanding individual queries, whereas multi-cluster scaling primarily addresses concurrency. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
C:This option addresses a different Snowflake technical topic (Hybrid tables and transactional constraints) rather than the documented Cross-region and cross-cloud account boundaries decision.
D:Streams track table change offsets; consuming a stream in committed DML advances its position, so independent consumers need separate offsets. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Question 108
The data platform team has not yet approved changes. Current evidence indicates: A failover plan expects a Snowflake account in a second region to use the primary region's data automatically. 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 account identifiers, regions, sharing or replication configuration and permitted data paths.
- Compare requested time window, privileges, ingestion lag and query history against a sample event.
- Inspect parsed JSON values, TYPEOF results and casts for null, numeric, Boolean and string examples.
Explanation
Correct Answer
B:Confirm afterward that: Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior. Applied case: A failover plan expects a Snowflake account in a second region to use the primary region's data automatically.
Incorrect Answers
A:Compare QUERY_HISTORY warehouse identifiers, queued time and load before and after changing session warehouse assignments. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
C:Compare requested time window, privileges, ingestion lag and query history against a sample event. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
D:Inspect parsed JSON values, TYPEOF results and casts for null, numeric, Boolean and string examples. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Question 109
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A failover plan expects a Snowflake account in a second region to use the primary region's data automatically. 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.
- 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.
- Only authorized cross-boundary data is accessible and recovery assumptions match configured replication behavior.
Explanation
Correct Answer
D:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:The approved design relies only on supported capabilities or explicitly plans the necessary edition change. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
B:This option addresses a different Snowflake technical topic (Apache Iceberg table architecture) rather than the documented Cross-region and cross-cloud account boundaries decision.
C:Each consumer processes only its authorized new changes without missing events due to another consumer's offset. Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
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.
