Snowflake SnowPro Core Practice Test 26
Question 250
For an original SnowPro Core educational scenario, consider: Two independent downstream consumers share one stream object and one consumes changes before the other processes them. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Create appropriate streams to expose change data and give independently checkpointed consumers their own streams when needed.
- Change: Use supported CLONE operations for a point-in-time logical snapshot and treat later changes to source and clone as separate.
- Check: Check table persistence after warehouse suspension and trace a query through authorization, optimization and independent compute.
- Treat a stream as an unlimited append-only event archive that multiple pipelines can consume without offset coordination.
- Check: Inspect stream contents and consumption behavior using controlled inserts, updates and two separate downstream consumers.
Explanation
Correct Answer
A:Acceptance: Each consumer processes only its authorized new changes without missing events due to another consumer's offset. Applied case: Two independent downstream consumers share one stream object and one consumes changes before the other processes them.
E:Acceptance: Each consumer processes only its authorized new changes without missing events due to another consumer's offset. Streams track table change offsets; consuming a stream in committed DML advances its position, so independent consumers need separate offsets.
Incorrect Answers
B:This option addresses a different Snowflake technical topic (Zero-copy cloning of database objects) rather than the documented Streams for change data capture decision.
C:This option addresses a different Snowflake technical topic (Three-layer Snowflake architecture) rather than the documented Streams for change data capture decision.
D:Streams track table change offsets; consuming a stream in committed DML advances its position, so independent consumers need separate offsets. Use this instead: Create appropriate streams to expose change data and give independently checkpointed consumers their own streams when needed.
Question 251
A Snowflake engineer is examining this platform situation: A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap. A proposed shortcut is: Schedule every dependent job at the same minute without dependency orchestration. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Schedule every dependent job at the same minute without dependency orchestration.
- Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules.
- Use appropriate staged file storage, directory metadata and supported unstructured file references or processing functions as needed.
- Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows.
Explanation
Correct Answer
D:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. Applied case: A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap.
Incorrect Answers
A:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
B:Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules. A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap.
C:Use appropriate staged file storage, directory metadata and supported unstructured file references or processing functions as needed. A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap.
Question 252
A Snowflake implementation review finds: A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap. The team proposes: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Managed AI functions can operate within supported Snowflake services, but model output requires governance and validation rather than assumption of determinism.
- Temporary tables exist only for their creating session and are removed when the session ends.
- Information Schema and Snowflake shared-account usage views provide different metadata scopes and refresh characteristics.
- Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
Explanation
Correct Answer
D:Demonstrable success requires: Downstream work starts only after its required predecessor succeeds and failures are visible to operators. Applied case: A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap.
Incorrect Answers
A:Managed AI functions can operate within supported Snowflake services, but model output requires governance and validation rather than assumption of determinism. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
B:Temporary tables exist only for their creating session and are removed when the session ends. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
C:Information Schema and Snowflake shared-account usage views provide different metadata scopes and refresh characteristics. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
Question 253
The data platform team has not yet approved changes. Current evidence indicates: A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect edition, feature availability and limits for the named requirement in an isolated test account.
- Compare requested time window, privileges, ingestion lag and query history against a sample event.
- Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
- Examine task graph history, predecessor states, warehouse permissions and failure handling.
Explanation
Correct Answer
D:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. Confirm afterward that: Downstream work starts only after its required predecessor succeeds and failures are visible to operators.
Incorrect Answers
A:Inspect edition, feature availability and limits for the named requirement in an isolated test account. A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap.
B:Compare requested time window, privileges, ingestion lag and query history against a sample event. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
C:Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
Question 254
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap. 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.
- Target queries finish within agreed latency while extra compute cost remains justified.
- A governed Iceberg table can be queried with supported capabilities while its files remain in the configured external location.
- Approved use cases generate useful drafts without bypassing classification or uncritically treating model output as factual truth.
- Downstream work starts only after its required predecessor succeeds and failures are visible to operators.
Explanation
Correct Answer
D:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Target queries finish within agreed latency while extra compute cost remains justified. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
B:This option addresses a different Snowflake technical topic (Apache Iceberg table architecture) rather than the documented Tasks and DAG scheduling decision.
C:Approved use cases generate useful drafts without bypassing classification or uncritically treating model output as factual truth. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
Question 255
An implementation sign-off request identifies the following problem: A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- 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: 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: 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: Evaluate Snowpark-optimized warehouse configurations only for supported memory-intensive Snowpark operations with measured benefit. Verify: Compare the job's memory failures, execution time, supported workload requirements and credits on both warehouse types.
Explanation
Correct Answer
C:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. The change is successful only when: Downstream work starts only after its required predecessor succeeds and failures are visible to operators.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Semi-structured path navigation) rather than the documented Tasks and DAG scheduling decision.
B:Change: Select Information Schema or ACCOUNT_USAGE views based on required object scope, privileges, history and documented latency. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
D:Change: Evaluate Snowpark-optimized warehouse configurations only for supported memory-intensive Snowpark operations with measured benefit. A daily enrichment step runs before its upstream load finishes because independent cron schedules overlap.
Question 256
A Snowflake engineer is examining this platform situation: A team wants two transformations to run after a successful normalization step and requires retry visibility. A proposed shortcut is: Schedule every dependent job at the same minute without dependency orchestration. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows.
- Use temporary tables only for intermediate data confined to a session and persist required results in durable table types.
- Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing.
- Schedule every dependent job at the same minute without dependency orchestration.
Explanation
Correct Answer
A:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. Applied case: A team wants two transformations to run after a successful normalization step and requires retry visibility.
Incorrect Answers
B:Use temporary tables only for intermediate data confined to a session and persist required results in durable table types. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
C:Set workload-suitable AUTO_SUSPEND and AUTO_RESUME values and validate startup behavior and billing. A team wants two transformations to run after a successful normalization step and requires retry visibility.
D:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. Use this instead: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows.
Question 257
A Snowflake implementation review finds: A team wants two transformations to run after a successful normalization step and requires retry visibility. The team proposes: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows. 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.
- Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
- Multi-cluster minimum and scaling choices balance response time and credit consumption; maximum clusters alone do not guarantee optimal cost.
- Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration.
Explanation
Correct Answer
B:Demonstrable success requires: Downstream work starts only after its required predecessor succeeds and failures are visible to operators. Applied case: A team wants two transformations to run after a successful normalization step and requires retry visibility.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Snowsight and programmatic tools) rather than the documented Tasks and DAG scheduling decision.
C:This option addresses a different Snowflake technical topic (Warehouse scaling mode and minimum clusters) rather than the documented Tasks and DAG scheduling decision.
D:Snowflake separates account-specific resources and regions; cross-account data access and disaster recovery require supported configuration. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
Question 258
The data platform team has not yet approved changes. Current evidence indicates: A team wants two transformations to run after a successful normalization step and requires retry visibility. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare service-level billing and account usage with warehouse usage for the relevant reporting period.
- Examine task graph history, predecessor states, warehouse permissions and failure handling.
- Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs.
- Inspect execution history before and after actions such as collect or write and compare data transfer size.
Explanation
Correct Answer
B:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. This check tests the actual data, compute or access boundary before an operationally risky change.
Incorrect Answers
A:Compare service-level billing and account usage with warehouse usage for the relevant reporting period. A team wants two transformations to run after a successful normalization step and requires retry visibility.
C:Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
D:This option addresses a different Snowflake technical topic (Snowpark DataFrame execution) rather than the documented Tasks and DAG scheduling decision.
Question 259
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A team wants two transformations to run after a successful normalization step and requires retry visibility. 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.
- Target queries finish within agreed latency while extra compute cost remains justified.
- The peak workload completes with reduced queuing while the cluster count contracts after demand subsides.
- Derived data updates at the expected operational cadence with refresh failures observable.
- Downstream work starts only after its required predecessor succeeds and failures are visible to operators.
Explanation
Correct Answer
D:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. The approved implementation step was: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows.
Incorrect Answers
A:Target queries finish within agreed latency while extra compute cost remains justified. A team wants two transformations to run after a successful normalization step and requires retry visibility.
B:This option addresses a different Snowflake technical topic (Multi-cluster warehouse concurrency) rather than the documented Tasks and DAG scheduling decision.
C:Derived data updates at the expected operational cadence with refresh failures observable. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
Question 260
For an original SnowPro Core educational scenario, consider: A team wants two transformations to run after a successful normalization step and requires retry visibility. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Examine task graph history, predecessor states, warehouse permissions and failure handling.
- Check: Compare account identifiers, regions, sharing or replication configuration and permitted data paths.
- Schedule every dependent job at the same minute without dependency orchestration.
- Change: Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields.
- Change: Use Snowflake tasks with explicit predecessors and monitored task graph behavior for supported SQL or procedure workflows.
Explanation
Correct Answer
A:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. Acceptance: Downstream work starts only after its required predecessor succeeds and failures are visible to operators.
E:Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion. Evidence: Examine task graph history, predecessor states, warehouse permissions and failure handling.
Incorrect Answers
B:Check: Compare account identifiers, regions, sharing or replication configuration and permitted data paths. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
C:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
D:Change: Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields. A team wants two transformations to run after a successful normalization step and requires retry visibility.
