Snowflake SnowPro Core Practice Test 78
Question 770
For an original SnowPro Core educational scenario, consider: A warehouse change reduced duration for some queries while credits doubled and the team claims universal optimization. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Use QUERY_HISTORY and Query Profile metrics to compare consistent workloads, warehouse changes and time periods.
- Check: Compare query IDs, duration, queue time, bytes scanned, spill and credits over equivalent workloads.
- Change: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation.
- Judge performance solely from a single user's stopwatch without query history or workload context.
- Check: Compare QUERY_HISTORY result reuse and query text or underlying data changes in a controlled test.
Explanation
Correct Answer
A:Query latency and credit use can change for multiple reasons including plan, data volume, queuing and warehouse resources. Evidence: Compare query IDs, duration, queue time, bytes scanned, spill and credits over equivalent workloads.
B:Query latency and credit use can change for multiple reasons including plan, data volume, queuing and warehouse resources. Required intervention: Use QUERY_HISTORY and Query Profile metrics to compare consistent workloads, warehouse changes and time periods.
Incorrect Answers
C:Change: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation. Query latency and credit use can change for multiple reasons including plan, data volume, queuing and warehouse resources.
D:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Query latency and credit use can change for multiple reasons including plan, data volume, queuing and warehouse resources.
E:Check: Compare QUERY_HISTORY result reuse and query text or underlying data changes in a controlled test. Query latency and credit use can change for multiple reasons including plan, data volume, queuing and warehouse resources.
Question 771
A Snowflake engineer is examining this platform situation: A BI warehouse has low average query execution time but dashboards stall because hundreds of simultaneous requests queue. A proposed shortcut is: Assume query queuing can be eliminated by adding ORDER BY to every SELECT. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use QUALIFY to filter on the result of window functions after proper PARTITION BY and ORDER BY.
- Assume query queuing can be eliminated by adding ORDER BY to every SELECT.
- Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL.
- Use LATERAL FLATTEN and explicit path and value casts to transform arrays into relational rows.
Explanation
Correct Answer
C:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. Applied case: A BI warehouse has low average query execution time but dashboards stall because hundreds of simultaneous requests queue.
Incorrect Answers
A:Use QUALIFY to filter on the result of window functions after proper PARTITION BY and ORDER BY. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
B:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
D:Use LATERAL FLATTEN and explicit path and value casts to transform arrays into relational rows. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Question 772
A Snowflake implementation review finds: A BI warehouse has low average query execution time but dashboards stall because hundreds of simultaneous requests queue. The team proposes: Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
- Clustering can improve locality and pruning but consumes maintenance resources and is not a universal tuning step.
- Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals.
- Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk.
Explanation
Correct Answer
A:Relevant validation before approval: Compare average execution versus queue time and cluster saturation during a simulated peak. Applied case: A BI warehouse has low average query execution time but dashboards stall because hundreds of simultaneous requests queue.
Incorrect Answers
B:Clustering can improve locality and pruning but consumes maintenance resources and is not a universal tuning step. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
C:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
D:This option addresses a different Snowflake technical topic (Snowpark pushdown and Python UDF boundaries) rather than the documented Warehouse concurrency and queuing decision.
Question 773
The data platform team has not yet approved changes. Current evidence indicates: A BI warehouse has low average query execution time but dashboards stall because hundreds of simultaneous requests queue. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps.
- Compare average execution versus queue time and cluster saturation during a simulated peak.
- Count conversion failures, review source examples and reconcile accepted versus quarantined records.
- Compare query profile, clustering depth, maintenance credits and representative workload results.
Explanation
Correct Answer
B:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. Confirm afterward that: User-facing latency improves by reducing wait time while maintaining correctness and reasonable credits.
Incorrect Answers
A:Compare an equivalent subquery with QUALIFY and test tie handling using ordered timestamps. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
C:Count conversion failures, review source examples and reconcile accepted versus quarantined records. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
D:Compare query profile, clustering depth, maintenance credits and representative workload results. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Question 774
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A BI warehouse has low average query execution time but dashboards stall because hundreds of simultaneous requests queue. 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.
- User-facing latency improves by reducing wait time while maintaining correctness and reasonable credits.
- The pipeline refreshes reliably within an accepted practical interval and alerts on failures.
- The chosen configuration meets deadlines while improving or justifying cost per delivered result.
Explanation
Correct Answer
B:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Important queries improve enough to justify ongoing clustering expense without changing business results. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
C:The pipeline refreshes reliably within an accepted practical interval and alerts on failures. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
D:The chosen configuration meets deadlines while improving or justifying cost per delivered result. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Question 775
An implementation sign-off request identifies the following problem: A BI warehouse has low average query execution time but dashboards stall because hundreds of simultaneous requests queue. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Tune appropriate suspension and workload locality after measuring warehouse data-cache benefit and idle credit cost. Verify: Compare bytes scanned from cache, suspend-resume behavior and warehouse IDs for repeated queries.
- Change: Track query duration, warehouse and serverless credits, data volume and service objectives together for tuning decisions. Verify: Compare task throughput, credits per successful run, latency and error rates before and after each change.
- Change: Evaluate persisted query result reuse conditions, including unchanged underlying data and eligible query determinism. Verify: Compare QUERY_HISTORY result reuse and query text or underlying data changes in a controlled test.
- 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
D:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. The change is successful only when: User-facing latency improves by reducing wait time while maintaining correctness and reasonable credits.
Incorrect Answers
A:Change: Tune appropriate suspension and workload locality after measuring warehouse data-cache benefit and idle credit cost. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
B:Change: Track query duration, warehouse and serverless credits, data volume and service objectives together for tuning decisions. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
C:Change: Evaluate persisted query result reuse conditions, including unchanged underlying data and eligible query determinism. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Question 776
A Snowflake engineer is examining this platform situation: An engineer modifies every SQL statement despite queue time dominating the end-to-end latency. A proposed shortcut is: Assume query queuing can be eliminated by adding ORDER BY to every SELECT. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Assume query queuing can be eliminated by adding ORDER BY to every SELECT.
- Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations.
- Evaluate clustering depth and selective query benefit before choosing a supported clustering key on a sufficiently large table.
- Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL.
Explanation
Correct Answer
D:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. Use this instead: Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL.
B:Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
C:Evaluate clustering depth and selective query benefit before choosing a supported clustering key on a sufficiently large table. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Question 777
A Snowflake implementation review finds: An engineer modifies every SQL statement despite queue time dominating the end-to-end latency. The team proposes: Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- 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.
- MERGE performs conditional updates, deletes or inserts from source rows; nondeterministic source matches can cause errors or incorrect outcomes.
- High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Explanation
Correct Answer
D:Relevant validation before approval: Compare average execution versus queue time and cluster saturation during a simulated peak. Demonstrable success requires: User-facing latency improves by reducing wait time while maintaining correctness and reasonable credits.
Incorrect Answers
A:Local or remote spill indicates execution pressure and can be affected by memory limits, join cardinality and data distribution. An engineer modifies every SQL statement despite queue time dominating the end-to-end latency.
B:QUALIFY filters query results after window functions are evaluated and is distinct from ordinary WHERE filtering. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
C:MERGE performs conditional updates, deletes or inserts from source rows; nondeterministic source matches can cause errors or incorrect outcomes. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Question 778
The data platform team has not yet approved changes. Current evidence indicates: An engineer modifies every SQL statement despite queue time dominating the end-to-end latency. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Check source counts, grouping keys and a small reference reconciliation with known customer transactions.
- Compare created table schema, row count, retention settings and downstream access after the initial session.
- Compare query profile, clustering depth, maintenance credits and representative workload results.
- Compare average execution versus queue time and cluster saturation during a simulated peak.
Explanation
Correct Answer
D:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. Applied case: An engineer modifies every SQL statement despite queue time dominating the end-to-end latency.
Incorrect Answers
A:Check source counts, grouping keys and a small reference reconciliation with known customer transactions. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
B:Compare created table schema, row count, retention settings and downstream access after the initial session. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
C:Compare query profile, clustering depth, maintenance credits and representative workload results. An engineer modifies every SQL statement despite queue time dominating the end-to-end latency.
Question 779
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An engineer modifies every SQL statement despite queue time dominating the end-to-end latency. 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.
- User-facing latency improves by reducing wait time while maintaining correctness and reasonable credits.
- Recurring reads improve without unacceptable data freshness or maintenance burden.
- Measured eligible queries improve sufficiently to justify serverless charges.
Explanation
Correct Answer
B:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. The approved implementation step was: Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL.
Incorrect Answers
A:Important queries improve enough to justify ongoing clustering expense without changing business results. An engineer modifies every SQL statement despite queue time dominating the end-to-end latency.
C:Recurring reads improve without unacceptable data freshness or maintenance burden. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
D:Measured eligible queries improve sufficiently to justify serverless charges. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
Question 780
For an original SnowPro Core educational scenario, consider: An engineer modifies every SQL statement despite queue time dominating the end-to-end latency. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Compare query profile, clustering depth, maintenance credits and representative workload results.
- Change: Tune appropriate suspension and workload locality after measuring warehouse data-cache benefit and idle credit cost.
- Assume query queuing can be eliminated by adding ORDER BY to every SELECT.
- Check: Compare average execution versus queue time and cluster saturation during a simulated peak.
- Change: Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL.
Explanation
Correct Answer
D:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. Acceptance: User-facing latency improves by reducing wait time while maintaining correctness and reasonable credits.
E:High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand. Evidence: Compare average execution versus queue time and cluster saturation during a simulated peak.
Incorrect Answers
A:Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL.
B:Change: Tune appropriate suspension and workload locality after measuring warehouse data-cache benefit and idle credit cost. An engineer modifies every SQL statement despite queue time dominating the end-to-end latency.
C:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. High concurrency can cause queuing independently of individual query efficiency; multi-cluster compute targets concurrent demand.
