Snowflake SnowPro Core Practice Test 73
Question 720
For an original SnowPro Core educational scenario, consider: A product owner enables search optimization on every column of a bulk aggregate table despite low selectivity. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Assume search optimization automatically speeds every large GROUP BY or full-table aggregation.
- Check: Compare eligible predicates, row selectivity, search access path use and service credit cost.
- Change: Track query duration, warehouse and serverless credits, data volume and service objectives together for tuning decisions.
- Change: Evaluate Snowflake Search Optimization Service for supported highly selective predicates and scoped table columns.
- Check: Inspect profile operator times, spilled bytes, join row counts and warehouse configuration.
Explanation
Correct Answer
B:Search optimization maintains a search access path for eligible lookup patterns, with storage and maintenance costs distinct from warehouse scans. Acceptance: Targeted point-lookups accelerate while maintenance costs remain proportional to business value.
D:Search optimization maintains a search access path for eligible lookup patterns, with storage and maintenance costs distinct from warehouse scans. Evidence: Compare eligible predicates, row selectivity, search access path use and service credit cost.
Incorrect Answers
A:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Search optimization maintains a search access path for eligible lookup patterns, with storage and maintenance costs distinct from warehouse scans.
C:Change: Track query duration, warehouse and serverless credits, data volume and service objectives together for tuning decisions. Search optimization maintains a search access path for eligible lookup patterns, with storage and maintenance costs distinct from warehouse scans.
E:Check: Inspect profile operator times, spilled bytes, join row counts and warehouse configuration. Search optimization maintains a search access path for eligible lookup patterns, with storage and maintenance costs distinct from warehouse scans.
Question 721
A Snowflake engineer is examining this platform situation: A BI dashboard repeatedly computes the same expensive filtered aggregation over a large stable fact table. A proposed shortcut is: Assume any arbitrary multi-join SQL statement is supported inside a materialized view. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Assume any arbitrary multi-join SQL statement is supported inside a materialized view.
- Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation.
- Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost.
- Use QUALIFY to filter on the result of window functions after proper PARTITION BY and ORDER BY.
Explanation
Correct Answer
C:The required acceptance condition is: Recurring reads improve without unacceptable data freshness or maintenance burden. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
B:Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
D:Use QUALIFY to filter on the result of window functions after proper PARTITION BY and ORDER BY. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 722
A Snowflake implementation review finds: A BI dashboard repeatedly computes the same expensive filtered aggregation over a large stable fact table. The team proposes: Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Window calculations evaluate over logical row partitions without necessarily collapsing rows as a GROUP BY does.
- Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk.
- Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
- Snowflake performance optimization is an economic and service-level tradeoff; faster response alone does not prove improved efficiency.
Explanation
Correct Answer
C:Relevant validation before approval: Check query eligibility, refresh behavior, query rewrite usage and storage or maintenance charges. Demonstrable success requires: Recurring reads improve without unacceptable data freshness or maintenance burden.
Incorrect Answers
A:Window calculations evaluate over logical row partitions without necessarily collapsing rows as a GROUP BY does. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
B:Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
D:Snowflake performance optimization is an economic and service-level tradeoff; faster response alone does not prove improved efficiency. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 723
The data platform team has not yet approved changes. Current evidence indicates: A BI dashboard repeatedly computes the same expensive filtered aggregation over a large stable fact table. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect profile operator times, spilled bytes, join row counts and warehouse configuration.
- Check query eligibility, refresh behavior, query rewrite usage and storage or maintenance charges.
- Test source-key duplicates, matched row counts and idempotent replay of the same batch.
- Compare task throughput, credits per successful run, latency and error rates before and after each change.
Explanation
Correct Answer
B:This check tests the actual data, compute or access boundary before an operationally risky change. Confirm afterward that: Recurring reads improve without unacceptable data freshness or maintenance burden.
Incorrect Answers
A:Inspect profile operator times, spilled bytes, join row counts and warehouse configuration. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
C:Test source-key duplicates, matched row counts and idempotent replay of the same batch. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
D:Compare task throughput, credits per successful run, latency and error rates before and after each change. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 724
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A BI dashboard repeatedly computes the same expensive filtered aggregation over a large stable fact table. 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 chosen configuration meets deadlines while improving or justifying cost per delivered result.
- Recurring reads improve without unacceptable data freshness or maintenance burden.
- The regression cause is measurable and the selected fix improves business performance economically.
- Repeat eligible queries can avoid recomputing results without returning stale data after changes.
Explanation
Correct Answer
B:The approved implementation step was: Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:The chosen configuration meets deadlines while improving or justifying cost per delivered result. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
C:The regression cause is measurable and the selected fix improves business performance economically. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
D:Repeat eligible queries can avoid recomputing results without returning stale data after changes. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 725
An implementation sign-off request identifies the following problem: A BI dashboard repeatedly computes the same expensive filtered aggregation over a large stable fact table. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Use selective predicates on suitable stored columns and evaluate micro-partition pruning before adding other optimizations. Verify: 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. Verify: Check query eligibility, refresh behavior, query rewrite usage and storage or maintenance charges.
- 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.
- Change: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation. Verify: Count conversion failures, review source examples and reconcile accepted versus quarantined records.
Explanation
Correct Answer
B:The change is successful only when: Recurring reads improve without unacceptable data freshness or maintenance burden.
Incorrect Answers
A:Change: Use selective predicates on suitable stored columns and evaluate micro-partition pruning before adding other optimizations.
C:Change: Evaluate concurrency scaling or workload separation and review queued overload time before rewriting correct SQL.
D:Change: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 726
A Snowflake engineer is examining this platform situation: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption. A proposed shortcut is: Assume any arbitrary multi-join SQL statement is supported inside a materialized view. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Assume any arbitrary multi-join SQL statement is supported inside a materialized view.
- Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation.
- Tune appropriate suspension and workload locality after measuring warehouse data-cache benefit and idle credit cost.
- Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost.
Explanation
Correct Answer
D:The required acceptance condition is: Recurring reads improve without unacceptable data freshness or maintenance burden. Applied case: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption.
Incorrect Answers
A:For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Applied case: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption.
B:Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation. A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption.
C:Tune appropriate suspension and workload locality after measuring warehouse data-cache benefit and idle credit cost. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 727
A Snowflake implementation review finds: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption. The team proposes: Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost. 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.
- Local warehouse cache is associated with running compute and does not equal reusable persisted query results across warehouses.
- Local or remote spill indicates execution pressure and can be affected by memory limits, join cardinality and data distribution.
- Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Explanation
Correct Answer
D:Relevant validation before approval: Check query eligibility, refresh behavior, query rewrite usage and storage or maintenance charges. Applied case: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption.
Incorrect Answers
A:Grouping defines output grain and aggregate semantics, so duplicates and non-grouped columns can invalidate or distort totals. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
B:Local warehouse cache is associated with running compute and does not equal reusable persisted query results across warehouses. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
C:Local or remote spill indicates execution pressure and can be affected by memory limits, join cardinality and data distribution. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 728
The data platform team has not yet approved changes. Current evidence indicates: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Check query eligibility, refresh behavior, query rewrite usage and storage or maintenance charges.
- Compare average execution versus queue time and cluster saturation during a simulated peak.
- Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA.
- Compare bytes scanned from cache, suspend-resume behavior and warehouse IDs for repeated queries.
Explanation
Correct Answer
A:This check tests the actual data, compute or access boundary before an operationally risky change. Applied case: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption.
Incorrect Answers
B:Compare average execution versus queue time and cluster saturation during a simulated peak. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
C:Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
D:Compare bytes scanned from cache, suspend-resume behavior and warehouse IDs for repeated queries. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 729
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption. 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.
- Targeted point-lookups accelerate while maintenance costs remain proportional to business value.
- The regression cause is measurable and the selected fix improves business performance economically.
- The query reads fewer relevant partitions while returning identical filtered rows.
- Recurring reads improve without unacceptable data freshness or maintenance burden.
Explanation
Correct Answer
D:The approved implementation step was: Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost. Applied case: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption.
Incorrect Answers
A:Targeted point-lookups accelerate while maintenance costs remain proportional to business value. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
B:The regression cause is measurable and the selected fix improves business performance economically. A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption.
C:The query reads fewer relevant partitions while returning identical filtered rows. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
Question 730
For an original SnowPro Core educational scenario, consider: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations.
- Assume any arbitrary multi-join SQL statement is supported inside a materialized view.
- Check: Inspect INPUT, INDEX, VALUE, missing paths and resulting expanded row counts.
- Change: Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost.
- Check: Check query eligibility, refresh behavior, query rewrite usage and storage or maintenance charges.
Explanation
Correct Answer
D:Acceptance: Recurring reads improve without unacceptable data freshness or maintenance burden.
E:Required intervention: Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost.
Incorrect Answers
A:Change: Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
B:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Applied case: A team creates a materialized view for a one-off exploratory query and ignores refresh maintenance consumption.
C:Check: Inspect INPUT, INDEX, VALUE, missing paths and resulting expanded row counts. Materialized views retain precomputed query results and have feature restrictions and maintenance tradeoffs.
