Snowflake SnowPro Core Practice Test 24
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.
Question 231
A Snowflake engineer is examining this platform situation: A pipeline refreshes three dependent transformations manually and often serves yesterday's results because one step is missed. A proposed shortcut is: Treat a target lag declaration as an unconditional guarantee of per-row instantaneous propagation. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Treat a target lag declaration as an unconditional guarantee of per-row instantaneous propagation.
- Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
- Express supported transformations with Snowpark DataFrames and materialize results using an execution action on Snowflake compute.
- Use appropriate staged file storage, directory metadata and supported unstructured file references or processing functions as needed.
Explanation
Correct Answer
B:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. Applied case: A pipeline refreshes three dependent transformations manually and often serves yesterday's results because one step is missed.
Incorrect Answers
A:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
C:This option addresses a different Snowflake technical topic (Snowpark DataFrame execution) rather than the documented Dynamic tables for declarative pipelines decision.
D:This option addresses a different Snowflake technical topic (Unstructured data and directory metadata) rather than the documented Dynamic tables for declarative pipelines decision.
Question 232
A Snowflake implementation review finds: A pipeline refreshes three dependent transformations manually and often serves yesterday's results because one step is missed. The team proposes: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Temporary tables exist only for their creating session and are removed when the session ends.
- Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
- An idle warehouse can be suspended to stop compute consumption and resumed when authorized work requires it.
- Semi-structured paths and types must match document structure; missing keys and invalid casts need intentional treatment.
Explanation
Correct Answer
B:Demonstrable success requires: Derived data updates at the expected operational cadence with refresh failures observable. Applied case: A pipeline refreshes three dependent transformations manually and often serves yesterday's results because one step is missed.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Session-scoped temporary tables) rather than the documented Dynamic tables for declarative pipelines decision.
C:This option addresses a different Snowflake technical topic (Warehouse auto-suspend and auto-resume) rather than the documented Dynamic tables for declarative pipelines decision.
D:This option addresses a different Snowflake technical topic (Semi-structured path navigation) rather than the documented Dynamic tables for declarative pipelines decision.
Question 233
The data platform team has not yet approved changes. Current evidence indicates: A pipeline refreshes three dependent transformations manually and often serves yesterday's results because one step is missed. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- 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.
- Inspect partition statistics and query profile scans before and after relevant data layout changes.
- Check table persistence after warehouse suspension and trace a query through authorization, optimization and independent compute.
Explanation
Correct Answer
B:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. This check tests the actual data, compute or access boundary before an operationally risky change.
Incorrect Answers
A:Compare requested time window, privileges, ingestion lag and query history against a sample event. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
C:Inspect partition statistics and query profile scans before and after relevant data layout changes. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
D:This option addresses a different Snowflake technical topic (Three-layer Snowflake architecture) rather than the documented Dynamic tables for declarative pipelines decision.
Question 234
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A pipeline refreshes three dependent transformations manually and often serves yesterday's results because one step is missed. 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 targeted memory-intensive job succeeds economically without changing unrelated dashboard infrastructure.
- Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity.
- The prior valid state is inspected or restored without overwriting unrelated current records.
- Derived data updates at the expected operational cadence with refresh failures observable.
Explanation
Correct Answer
D:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:The targeted memory-intensive job succeeds economically without changing unrelated dashboard infrastructure. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
B:Clusters grow for meaningful demand and shrink when the service target permits without sustaining idle peak capacity. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
C:The prior valid state is inspected or restored without overwriting unrelated current records. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
Question 235
An implementation sign-off request identifies the following problem: A pipeline refreshes three dependent transformations manually and often serves yesterday's results because one step is missed. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Distinguish cloud-services-layer functions from virtual warehouse execution when analyzing processing and billable consumption. Verify: Compare service-level billing and account usage with warehouse usage for the relevant reporting period.
- Change: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism. Verify: Verify table type, historical retention expiration and documented support/recovery process before planning restoration.
- 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: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. Verify: Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
Explanation
Correct Answer
D:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. The change is successful only when: Derived data updates at the expected operational cadence with refresh failures observable.
Incorrect Answers
A:Change: Distinguish cloud-services-layer functions from virtual warehouse execution when analyzing processing and billable consumption. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
B:Change: Use Time Travel for self-service history and regard Fail-safe on eligible permanent objects as a limited Snowflake-assisted recovery mechanism. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
C:Change: Tune MIN_CLUSTER_COUNT, MAX_CLUSTER_COUNT and supported scaling policy against measured concurrency requirements. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
Question 236
A Snowflake engineer is examining this platform situation: A team expects a dynamic table with a ten-minute target lag to guarantee every row is visible exactly ten minutes after insertion under all conditions. A proposed shortcut is: Treat a target lag declaration as an unconditional guarantee of per-row instantaneous propagation. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
- Treat a target lag declaration as an unconditional guarantee of per-row instantaneous propagation.
- Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields.
- Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets.
Explanation
Correct Answer
A:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
B:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. Use this instead: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
C:Use LATERAL FLATTEN against the appropriate VARIANT array and select the expanded VALUE fields. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
D:Use supported Notebooks in Workspaces and verify migration requirements for any legacy notebook assets. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
Question 237
A Snowflake implementation review finds: A team expects a dynamic table with a ten-minute target lag to guarantee every row is visible exactly ten minutes after insertion under all conditions. The team proposes: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations. 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.
- Task graphs express dependencies and execute on assigned compute or supported serverless resources; schedules alone do not imply upstream completion.
- Snowflake editions have different availability and limits for selected features; architectural claims must match the purchased edition and current documentation.
- Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
Explanation
Correct Answer
D:Demonstrable success requires: Derived data updates at the expected operational cadence with refresh failures observable. This principle explains the proposed technical approach, which is: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Permanent versus transient table retention) rather than the documented Dynamic tables for declarative pipelines decision.
B:This option addresses a different Snowflake technical topic (Tasks and DAG scheduling) rather than the documented Dynamic tables for declarative pipelines decision.
C:Snowflake editions have different availability and limits for selected features; architectural claims must match the purchased edition and current documentation. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
Question 238
The data platform team has not yet approved changes. Current evidence indicates: A team expects a dynamic table with a ten-minute target lag to guarantee every row is visible exactly ten minutes after insertion under all conditions. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs.
- Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
- Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session.
- Inspect partition statistics and query profile scans before and after relevant data layout changes.
Explanation
Correct Answer
B:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. Applied case: A team expects a dynamic table with a ten-minute target lag to guarantee every row is visible exactly ten minutes after insertion under all conditions.
Incorrect Answers
A:Compare query profile spill bytes, elapsed time, warehouse size and warehouse credits under equivalent inputs. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
C:Inspect CURRENT_DATABASE, CURRENT_SCHEMA, SHOW TABLES and fully qualified object names in the deployment session. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
D:Inspect partition statistics and query profile scans before and after relevant data layout changes. A team expects a dynamic table with a ten-minute target lag to guarantee every row is visible exactly ten minutes after insertion under all conditions.
Question 239
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A team expects a dynamic table with a ten-minute target lag to guarantee every row is visible exactly ten minutes after insertion under all conditions. 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 prior valid state is inspected or restored without overwriting unrelated current records.
- Derived data updates at the expected operational cadence with refresh failures observable.
- The approved design relies only on supported capabilities or explicitly plans the necessary edition change.
- The recovery runbook specifies the correct mechanism and realistic timing for historical incidents.
Explanation
Correct Answer
B:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. The approved implementation step was: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
Incorrect Answers
A:The prior valid state is inspected or restored without overwriting unrelated current records. A team expects a dynamic table with a ten-minute target lag to guarantee every row is visible exactly ten minutes after insertion under all conditions.
C:The approved design relies only on supported capabilities or explicitly plans the necessary edition change. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
D:The recovery runbook specifies the correct mechanism and realistic timing for historical incidents. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
Question 240
For an original SnowPro Core educational scenario, consider: A team expects a dynamic table with a ten-minute target lag to guarantee every row is visible exactly ten minutes after insertion under all conditions. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
- Treat a target lag declaration as an unconditional guarantee of per-row instantaneous propagation.
- Change: Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules.
- Check: Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
- Check: Verify table type, historical retention expiration and documented support/recovery process before planning restoration.
Explanation
Correct Answer
A:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. Evidence: Inspect refresh history, dependencies, actual lag and warehouse or serverless resource configuration.
D:Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA. Required intervention: Use dynamic tables with target lag, supported refresh mode and dependency monitoring for declarative transformations.
Incorrect Answers
B:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
C:Change: Place ETL and interactive queries on independently configured warehouses with workload-appropriate sizes and schedules. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
E:Check: Verify table type, historical retention expiration and documented support/recovery process before planning restoration. Dynamic tables maintain query-defined results through managed refresh scheduling; target lag is an objective, not a hard real-time SLA.
