Snowflake SnowPro Core Practice Test 87
Question 860
For an original SnowPro Core educational scenario, consider: A team creates temporary tables for downstream reports that must outlive the session. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Define correct join keys and grain, deduplicate where required and validate output cardinality before aggregation.
- Assume every CTAS table is automatically a dynamic view that refreshes whenever source data changes.
- Check: Inspect profile operator times, spilled bytes, join row counts and warehouse configuration.
- Check: Compare created table schema, row count, retention settings and downstream access after the initial session.
- Change: Use CREATE TABLE AS SELECT with an appropriate table type and explicit lifecycle or dependency management.
Explanation
Correct Answer
D:CTAS materializes query results into a new table; its persistence and storage cost depend on the target table type. Acceptance: Required transformed datasets remain available for the intended lifecycle without accidental duplication.
E:CTAS materializes query results into a new table; its persistence and storage cost depend on the target table type. Evidence: Compare created table schema, row count, retention settings and downstream access after the initial session.
Incorrect Answers
A:Change: Define correct join keys and grain, deduplicate where required and validate output cardinality before aggregation. CTAS materializes query results into a new table; its persistence and storage cost depend on the target table type.
B:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. CTAS materializes query results into a new table; its persistence and storage cost depend on the target table type.
C:Check: Inspect profile operator times, spilled bytes, join row counts and warehouse configuration. CTAS materializes query results into a new table; its persistence and storage cost depend on the target table type.
Question 861
A Snowflake engineer is examining this platform situation: A reporting dynamic table shows stale records because its refresh job repeatedly fails despite a short target lag. A proposed shortcut is: Treat a declared TARGET_LAG as a hard contractual guarantee that no row can be late. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use selective predicates on suitable stored columns and evaluate micro-partition pruning before adding other optimizations.
- Use CREATE TABLE AS SELECT with an appropriate table type and explicit lifecycle or dependency management.
- Treat a declared TARGET_LAG as a hard contractual guarantee that no row can be late.
- Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
Explanation
Correct Answer
D:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. Applied case: A reporting dynamic table shows stale records because its refresh job repeatedly fails despite a short target lag.
Incorrect Answers
A:Use selective predicates on suitable stored columns and evaluate micro-partition pruning before adding other optimizations. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
B:Use CREATE TABLE AS SELECT with an appropriate table type and explicit lifecycle or dependency management. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
C:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
Question 862
A Snowflake implementation review finds: A reporting dynamic table shows stale records because its refresh job repeatedly fails despite a short target lag. The team proposes: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Snowflake performance optimization is an economic and service-level tradeoff; faster response alone does not prove improved efficiency.
- Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
- CTAS materializes query results into a new table; its persistence and storage cost depend on the target table type.
- High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Explanation
Correct Answer
B:Demonstrable success requires: The pipeline refreshes reliably within an accepted practical interval and alerts on failures. This principle explains the proposed technical approach, which is: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
Incorrect Answers
A:Snowflake performance optimization is an economic and service-level tradeoff; faster response alone does not prove improved efficiency. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
C:CTAS materializes query results into a new table; its persistence and storage cost depend on the target table type. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
D:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
Question 863
The data platform team has not yet approved changes. Current evidence indicates: A reporting dynamic table shows stale records because its refresh job repeatedly fails despite a short target lag. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare eligible predicates, row selectivity, search access path use and service credit cost.
- Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA.
- Compare source key uniqueness, pre-join counts and resulting row counts for representative business IDs.
- Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps.
Explanation
Correct Answer
B:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. If confirmed, the proportionate intervention is: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
Incorrect Answers
A:Compare eligible predicates, row selectivity, search access path use and service credit cost. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
C:Compare source key uniqueness, pre-join counts and resulting row counts for representative business IDs. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
D:Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
Question 864
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A reporting dynamic table shows stale records because its refresh job repeatedly fails despite a short target lag. 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.
- Important queries improve enough to justify ongoing clustering expense without changing business results.
- Repeat eligible queries can avoid recomputing results without returning stale data after changes.
- Valid values are typed correctly and bad data is isolated rather than silently misreported.
- The pipeline refreshes reliably within an accepted practical interval and alerts on failures.
Explanation
Correct Answer
D:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. The approved implementation step was: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
Incorrect Answers
A:Important queries improve enough to justify ongoing clustering expense without changing business results. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
B:Repeat eligible queries can avoid recomputing results without returning stale data after changes. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
C:Valid values are typed correctly and bad data is isolated rather than silently misreported. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
Question 865
An implementation sign-off request identifies the following problem: A reporting dynamic table shows stale records because its refresh job repeatedly fails despite a short target lag. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Use QUALIFY to filter on the result of window functions after proper PARTITION BY and ORDER BY. Verify: Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps.
- Change: Evaluate supported Query Acceleration Service on eligible queries using its estimate and cost controls. Verify: Inspect query eligibility and acceleration history plus incremental service credits for representative workloads.
- Change: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs. Verify: Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA.
- Change: Define correct join keys and grain, deduplicate where required and validate output cardinality before aggregation. Verify: Compare source key uniqueness, pre-join counts and resulting row counts for representative business IDs.
Explanation
Correct Answer
C:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. The change is successful only when: The pipeline refreshes reliably within an accepted practical interval and alerts on failures.
Incorrect Answers
A:Change: Use QUALIFY to filter on the result of window functions after proper PARTITION BY and ORDER BY. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
B:Change: Evaluate supported Query Acceleration Service on eligible queries using its estimate and cost controls. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
D:Change: Define correct join keys and grain, deduplicate where required and validate output cardinality before aggregation. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
Question 866
A Snowflake engineer is examining this platform situation: A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency. A proposed shortcut is: Treat a declared TARGET_LAG as a hard contractual guarantee that no row can be late. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations.
- Treat a declared TARGET_LAG as a hard contractual guarantee that no row can be late.
- Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
- Tune appropriate suspension and workload locality after measuring warehouse data-cache benefit and idle credit cost.
Explanation
Correct Answer
C:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. Applied case: A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency.
Incorrect Answers
A:Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
B:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. Use this instead: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
D:Tune appropriate suspension and workload locality after measuring warehouse data-cache benefit and idle credit cost. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
Question 867
A Snowflake implementation review finds: A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency. The team proposes: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Local warehouse cache is associated with running compute and does not equal reusable persisted query results across warehouses.
- Window calculations evaluate over logical row partitions without necessarily collapsing rows as a GROUP BY does.
- Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
- Local or remote spill indicates execution pressure and can be affected by memory limits, join cardinality and data distribution.
Explanation
Correct Answer
C:Demonstrable success requires: The pipeline refreshes reliably within an accepted practical interval and alerts on failures. Applied case: A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency.
Incorrect Answers
A:Local warehouse cache is associated with running compute and does not equal reusable persisted query results across warehouses. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
B:Window calculations evaluate over logical row partitions without necessarily collapsing rows as a GROUP BY does. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
D:This option addresses a different Snowflake technical topic (Query profile spilling and repartitioning) rather than the documented Dynamic table target lag and refresh economics decision.
Question 868
The data platform team has not yet approved changes. Current evidence indicates: A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA.
- Compare eligible predicates, row selectivity, search access path use and service credit cost.
- Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps.
- Inspect INPUT, INDEX, VALUE, missing paths and resulting expanded row counts.
Explanation
Correct Answer
A:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. This check tests the actual data, compute or access boundary before an operationally risky change.
Incorrect Answers
B:Compare eligible predicates, row selectivity, search access path use and service credit cost. A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency.
C:Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps. A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency.
D:Inspect INPUT, INDEX, VALUE, missing paths and resulting expanded row counts. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
Question 869
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency. 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.
- Each intended nested element is represented with correct types and no accidental Cartesian explosion.
- Each group has the intended ranked or rolling values while original row-level detail is preserved.
- The pipeline refreshes reliably within an accepted practical interval and alerts on failures.
- Recurring reads improve without unacceptable data freshness or maintenance burden.
Explanation
Correct Answer
C:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Each intended nested element is represented with correct types and no accidental Cartesian explosion. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
B:Each group has the intended ranked or rolling values while original row-level detail is preserved. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
D:Recurring reads improve without unacceptable data freshness or maintenance burden. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
Question 870
For an original SnowPro Core educational scenario, consider: A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Evaluate supported Query Acceleration Service on eligible queries using its estimate and cost controls.
- Change: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
- Check: Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA.
- Treat a declared TARGET_LAG as a hard contractual guarantee that no row can be late.
- Check: Compare average execution versus queue time and cluster saturation during a simulated peak.
Explanation
Correct Answer
B:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. Evidence: Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA.
C:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. Required intervention: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
Incorrect Answers
A:Change: Evaluate supported Query Acceleration Service on eligible queries using its estimate and cost controls. A team configures a one-minute target lag for expensive multi-stage work without checking compute cost or source update frequency.
D:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
E:Check: Compare average execution versus queue time and cluster saturation during a simulated peak. Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.