Snowflake SnowPro Core Practice Test 89
Question 880
For an original SnowPro Core educational scenario, consider: A developer assumes every arbitrary Python package runs inside standard SQL functions without dependency or runtime controls. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Express supported filters and transformations as Snowpark operations and use governed execution runtimes for Python-specific steps.
- Check: Inspect query profile scanned partitions, predicate form and representative date distribution.
- Change: Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost.
- Download the entire warehouse dataset to a laptop as the default first step in every Snowpark query.
- Check: Compare generated SQL plans, data transfer volumes and managed package availability for a sample transform.
Explanation
Correct Answer
A:Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk. Acceptance: The pipeline processes supported data within Snowflake while downloading only necessary results.
E:Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk. Required intervention: Express supported filters and transformations as Snowpark operations and use governed execution runtimes for Python-specific steps.
Incorrect Answers
B:Check: Inspect query profile scanned partitions, predicate form and representative date distribution. Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk.
C:Change: Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost. Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk.
D:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk.
Question 881
A Snowflake engineer is examining this platform situation: A marketing report mixes row-level campaign IDs with SUM revenue and produces an invalid grouping statement. A proposed shortcut is: Add every column to GROUP BY solely to silence an error while claiming totals remain at the original business grain. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL.
- Use an appropriate MERGE with deterministic matched and unmatched clauses and validated source uniqueness.
- Add every column to GROUP BY solely to silence an error while claiming totals remain at the original business grain.
- Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it.
Explanation
Correct Answer
D:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
B:Use an appropriate MERGE with deterministic matched and unmatched clauses and validated source uniqueness. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
Question 882
A Snowflake implementation review finds: A marketing report mixes row-level campaign IDs with SUM revenue and produces an invalid grouping statement. The team proposes: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
- Window calculations evaluate over logical row partitions without necessarily collapsing rows as a GROUP BY does.
- Local or remote spill indicates execution pressure and can be affected by memory limits, join cardinality and data distribution.
- QUALIFY filters query results after window functions are evaluated and is distinct from ordinary WHERE filtering.
Explanation
Correct Answer
A:Relevant validation before approval: Check source counts, grouping keys and a small reference reconciliation with known customer transactions. This principle explains the proposed technical approach, which is: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it.
Incorrect Answers
B:Window calculations evaluate over logical row partitions without necessarily collapsing rows as a GROUP BY does. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:This option addresses a different Snowflake technical topic (Query profile spilling and repartitioning) rather than the documented Aggregations and grouping correctness decision.
D:QUALIFY filters query results after window functions are evaluated and is distinct from ordinary WHERE filtering. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
Question 883
The data platform team has not yet approved changes. Current evidence indicates: A marketing report mixes row-level campaign IDs with SUM revenue and produces an invalid grouping statement. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare query profile, clustering depth, maintenance credits and representative workload results.
- Check source counts, grouping keys and a small reference reconciliation with known customer transactions.
- Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps.
- Test source-key duplicates, matched row counts and idempotent replay of the same batch.
Explanation
Correct Answer
B:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. If confirmed, the proportionate intervention is: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it.
Incorrect Answers
A:Compare query profile, clustering depth, maintenance credits and representative workload results. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
D:Test source-key duplicates, matched row counts and idempotent replay of the same batch. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
Question 884
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A marketing report mixes row-level campaign IDs with SUM revenue and produces an invalid grouping statement. 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.
- Aggregated measures reconcile to the intended grain and avoid fanout inflation.
- Repeat eligible queries can avoid recomputing results without returning stale data after changes.
- Measured eligible queries improve sufficiently to justify serverless charges.
- The target reflects one authorized current record per business key after updates and inserts.
Explanation
Correct Answer
A:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. The approved implementation step was: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it.
Incorrect Answers
B:Repeat eligible queries can avoid recomputing results without returning stale data after changes. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Measured eligible queries improve sufficiently to justify serverless charges. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
D:The target reflects one authorized current record per business key after updates and inserts. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
Question 885
An implementation sign-off request identifies the following problem: A marketing report mixes row-level campaign IDs with SUM revenue and produces an invalid grouping statement. 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: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it. Verify: Check source counts, grouping keys and a small reference reconciliation with known customer transactions.
- Change: Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations. Verify: Test row_number or moving-average output for customers with multiple timestamps and ties.
- Change: Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL. Verify: Compare average execution versus queue time and cluster saturation during a simulated peak.
Explanation
Correct Answer
B:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. The change is successful only when: Aggregated measures reconcile to the intended grain and avoid fanout inflation.
Incorrect Answers
A:Change: Use QUALIFY to filter on the result of window functions after proper PARTITION BY and ORDER BY. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Change: Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
D:Change: Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
Question 886
A Snowflake engineer is examining this platform situation: A finance dashboard applies COUNT(*) after a fanout join and reports too many customer orders. A proposed shortcut is: Add every column to GROUP BY solely to silence an error while claiming totals remain at the original business grain. 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.
- Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it.
- Express supported filters and transformations as Snowpark operations and use governed execution runtimes for Python-specific steps.
- Add every column to GROUP BY solely to silence an error while claiming totals remain at the original business grain.
Explanation
Correct Answer
B:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. Applied case: A finance dashboard applies COUNT(*) after a fanout join and reports too many customer orders.
Incorrect Answers
A:Use selective predicates on suitable stored columns and evaluate micro-partition pruning before adding other optimizations. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Express supported filters and transformations as Snowpark operations and use governed execution runtimes for Python-specific steps. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
D:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. Use this instead: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it.
Question 887
A Snowflake implementation review finds: A finance dashboard applies COUNT(*) after a fanout join and reports too many customer orders. The team proposes: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- TRY-style conversions can yield NULL for invalid input instead of stopping an entire transform, but silently ignoring invalid values is still a quality risk.
- Snowflake metadata can skip micro-partitions whose ranges do not satisfy filters; poor layout or non-sargable expressions reduce pruning.
- Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
- Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
Explanation
Correct Answer
D:Relevant validation before approval: Check source counts, grouping keys and a small reference reconciliation with known customer transactions. Demonstrable success requires: Aggregated measures reconcile to the intended grain and avoid fanout inflation.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (TRY_CAST and malformed source records) rather than the documented Aggregations and grouping correctness decision.
B:Snowflake metadata can skip micro-partitions whose ranges do not satisfy filters; poor layout or non-sargable expressions reduce pruning. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
Question 888
The data platform team has not yet approved changes. Current evidence indicates: A finance dashboard applies COUNT(*) after a fanout join and reports too many customer orders. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare QUERY_HISTORY result reuse and query text or underlying data changes in a controlled test.
- Check source counts, grouping keys and a small reference reconciliation with known customer transactions.
- Inspect query eligibility and acceleration history plus incremental service credits for representative workloads.
- Test source-key duplicates, matched row counts and idempotent replay of the same batch.
Explanation
Correct Answer
B:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. This check tests the actual data, compute or access boundary before an operationally risky change.
Incorrect Answers
A:Compare QUERY_HISTORY result reuse and query text or underlying data changes in a controlled test. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Inspect query eligibility and acceleration history plus incremental service credits for representative workloads. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
D:Test source-key duplicates, matched row counts and idempotent replay of the same batch. A finance dashboard applies COUNT(*) after a fanout join and reports too many customer orders.
Question 889
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A finance dashboard applies COUNT(*) after a fanout join and reports too many customer orders. 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.
- Aggregated measures reconcile to the intended grain and avoid fanout inflation.
- The regression cause is measurable and the selected fix improves business performance economically.
- Important queries improve enough to justify ongoing clustering expense without changing business results.
- Each group has the intended ranked or rolling values while original row-level detail is preserved.
Explanation
Correct Answer
A:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. The result must be validated using the documented dataset or access context.
Incorrect Answers
B:The regression cause is measurable and the selected fix improves business performance economically. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Important queries improve enough to justify ongoing clustering expense without changing business results. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
D:Each group has the intended ranked or rolling values while original row-level detail is preserved. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
Question 890
For an original SnowPro Core educational scenario, consider: A finance dashboard applies COUNT(*) after a fanout join and reports too many customer orders. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it.
- Add every column to GROUP BY solely to silence an error while claiming totals remain at the original business grain.
- Change: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs.
- Check: Check source counts, grouping keys and a small reference reconciliation with known customer transactions.
- Check: Compare bytes scanned from cache, suspend-resume behavior and warehouse IDs for repeated queries.
Explanation
Correct Answer
A:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. Evidence: Check source counts, grouping keys and a small reference reconciliation with known customer transactions.
D:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. Required intervention: Match SELECT expressions to GROUP BY grain and use correct distinct or preaggregation strategy when source cardinality requires it.
Incorrect Answers
B:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
C:Change: Review dynamic table refresh history, eligibility and resource use, then set an achievable target lag for business freshness needs. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
E:Check: Compare bytes scanned from cache, suspend-resume behavior and warehouse IDs for repeated queries. Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
