Snowflake SnowPro Core Practice Test 84
Question 830
For an original SnowPro Core educational scenario, consider: A security log has a nested array of resource tags and a developer assumes VALUE is automatically a typed VARCHAR. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Evaluate Snowflake Search Optimization Service for supported highly selective predicates and scoped table columns.
- Check: Compare query profile, clustering depth, maintenance credits and representative workload results.
- Check: Inspect INPUT, INDEX, VALUE, missing paths and resulting expanded row counts.
- Join JSON objects using string splitting instead of parsing the supported array structure.
- Change: Use LATERAL FLATTEN and explicit path and value casts to transform arrays into relational rows.
Explanation
Correct Answer
C:Required intervention: Use LATERAL FLATTEN and explicit path and value casts to transform arrays into relational rows.
E:FLATTEN expands array elements, while VARIANT values often require explicit casts for typed calculations.
Incorrect Answers
A:Change: Evaluate Snowflake Search Optimization Service for supported highly selective predicates and scoped table columns. FLATTEN expands array elements, while VARIANT values often require explicit casts for typed calculations.
B:Check: Compare query profile, clustering depth, maintenance credits and representative workload results. FLATTEN expands array elements, while VARIANT values often require explicit casts for typed calculations.
D:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. FLATTEN expands array elements, while VARIANT values often require explicit casts for typed calculations.
Question 831
A Snowflake engineer is examining this platform situation: An incoming orders feed contains the string unknown in a field expected to be a decimal amount. A proposed shortcut is: Replace invalid numeric values with zero without logging or analyzing the data-quality impact. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation.
- Use an appropriate MERGE with deterministic matched and unmatched clauses and validated source uniqueness.
- Replace invalid numeric values with zero without logging or analyzing the data-quality impact.
- Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost.
Explanation
Correct Answer
A: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. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
B:Use an appropriate MERGE with deterministic matched and unmatched clauses and validated source uniqueness. 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.
C: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. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
D:Evaluate a supported materialized view for a repeatable eligible query with justified refresh and storage cost. 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.
Question 832
A Snowflake implementation review finds: An incoming orders feed contains the string unknown in a field expected to be a decimal amount. The team proposes: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation. 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.
- Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk.
- Search optimization maintains a search access path for eligible lookup patterns, with storage and maintenance costs distinct from warehouse scans.
Explanation
Correct Answer
A:Relevant validation before approval: Count conversion failures, review source examples and reconcile accepted versus quarantined records. Demonstrable success requires: Valid values are typed correctly and bad data is isolated rather than silently misreported.
Incorrect Answers
B:Snowflake metadata can skip micro-partitions whose ranges do not satisfy filters; poor layout or non-sargable expressions reduce pruning. 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.
C:Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk. 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.
D:Search optimization maintains a search access path for eligible lookup patterns, with storage and maintenance costs distinct from warehouse scans. 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.
Question 833
The data platform team has not yet approved changes. Current evidence indicates: An incoming orders feed contains the string unknown in a field expected to be a decimal amount. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare bytes scanned from cache, suspend-resume behavior and warehouse IDs for repeated queries.
- Count conversion failures, review source examples and reconcile accepted versus quarantined records.
- Compare query profile, clustering depth, maintenance credits and representative workload results.
- Test source-key duplicates, matched row counts and idempotent replay of the same batch.
Explanation
Correct Answer
B: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. Confirm afterward that: Valid values are typed correctly and bad data is isolated rather than silently misreported.
Incorrect Answers
A:Compare bytes scanned from cache, suspend-resume behavior and warehouse IDs for repeated queries. An incoming orders feed contains the string unknown in a field expected to be a decimal amount.
C:Compare query profile, clustering depth, maintenance credits and representative workload results. An incoming orders feed contains the string unknown in a field expected to be a decimal amount.
D:Test source-key duplicates, matched row counts and idempotent replay of the same batch. 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.
Question 834
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An incoming orders feed contains the string unknown in a field expected to be a decimal amount. 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 pipeline refreshes reliably within an accepted practical interval and alerts on failures.
- User-facing latency improves by reducing wait time while maintaining correctness and reasonable credits.
- Targeted point-lookups accelerate while maintenance costs remain proportional to business value.
- Valid values are typed correctly and bad data is isolated rather than silently misreported.
Explanation
Correct Answer
D: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. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:The pipeline refreshes reliably within an accepted practical interval and alerts on failures. 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.
B:User-facing latency improves by reducing wait time while maintaining correctness and reasonable credits. An incoming orders feed contains the string unknown in a field expected to be a decimal amount.
C:Targeted point-lookups accelerate while maintenance costs remain proportional to business value. 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.
Question 835
An implementation sign-off request identifies the following problem: An incoming orders feed contains the string unknown in a field expected to be a decimal amount. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- 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.
- 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: Use an appropriate MERGE with deterministic matched and unmatched clauses and validated source uniqueness. Verify: Test source-key duplicates, matched row counts and idempotent replay of the same batch.
- 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.
Explanation
Correct Answer
A: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. The change is successful only when: Valid values are typed correctly and bad data is isolated rather than silently misreported.
Incorrect Answers
B:This option addresses a different Snowflake technical topic (Monitoring cost and performance together) rather than the documented TRY_CAST and malformed source records decision.
C:Change: Use an appropriate MERGE with deterministic matched and unmatched clauses and validated source uniqueness. 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.
D:Change: Use appropriate window functions with PARTITION BY and ordered frames for row-level ranking or rolling calculations. 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.
Question 836
A Snowflake engineer is examining this platform situation: An ETL script blindly casts ISO date strings even when a few records contain impossible dates. A proposed shortcut is: Replace invalid numeric values with zero without logging or analyzing the data-quality impact. 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.
- Replace invalid numeric values with zero without logging or analyzing the data-quality impact.
- Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation.
- Evaluate supported Query Acceleration Service on eligible queries using its estimate and cost controls.
Explanation
Correct Answer
C: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. Applied case: An ETL script blindly casts ISO date strings even when a few records contain impossible dates.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (QUALIFY filtering window expressions) rather than the documented TRY_CAST and malformed source records decision.
B: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. Use this instead: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation.
D:Evaluate supported Query Acceleration Service on eligible queries using its estimate and cost controls. An ETL script blindly casts ISO date strings even when a few records contain impossible dates.
Question 837
A Snowflake implementation review finds: An ETL script blindly casts ISO date strings even when a few records contain impossible dates. The team proposes: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Snowflake may reuse prior query results subject to eligibility and validity conditions; this cache is different from a warehouse's local data cache.
- 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.
- Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk.
- Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute.
Explanation
Correct Answer
B:Relevant validation before approval: Count conversion failures, review source examples and reconcile accepted versus quarantined records. Applied case: An ETL script blindly casts ISO date strings even when a few records contain impossible dates.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Persisted query result cache) rather than the documented TRY_CAST and malformed source records decision.
C:Snowpark can push supported operations to Snowflake compute; premature data collection or unsupported runtime assumptions add cost and risk. An ETL script blindly casts ISO date strings even when a few records contain impossible dates.
D:Dynamic table target lag guides managed refresh behavior but does not promise zero-latency propagation or free compute. 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.
Question 838
The data platform team has not yet approved changes. Current evidence indicates: An ETL script blindly casts ISO date strings even when a few records contain impossible dates. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect query profile scanned partitions, predicate form and representative date distribution.
- Count conversion failures, review source examples and reconcile accepted versus quarantined records.
- Test source-key duplicates, matched row counts and idempotent replay of the same batch.
- Test row_number or moving-average output for customers with multiple timestamps and ties.
Explanation
Correct Answer
B: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. This check tests the actual data, compute or access boundary before an operationally risky change.
Incorrect Answers
A:Inspect query profile scanned partitions, predicate form and representative date distribution. 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.
C:Test source-key duplicates, matched row counts and idempotent replay of the same batch. An ETL script blindly casts ISO date strings even when a few records contain impossible dates.
D:Test row_number or moving-average output for customers with multiple timestamps and ties. 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.
Question 839
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: An ETL script blindly casts ISO date strings even when a few records contain impossible dates. 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.
- Valid values are typed correctly and bad data is isolated rather than silently misreported.
- Recurring reads improve without unacceptable data freshness or maintenance burden.
- The join yields expected grain and aggregate totals reconcile to source transactions.
- The regression cause is measurable and the selected fix improves business performance economically.
Explanation
Correct Answer
A: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. The approved implementation step was: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation.
Incorrect Answers
B:Recurring reads improve without unacceptable data freshness or maintenance burden. 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.
C:The join yields expected grain and aggregate totals reconcile to source transactions. An ETL script blindly casts ISO date strings even when a few records contain impossible dates.
D:The regression cause is measurable and the selected fix improves business performance economically. An ETL script blindly casts ISO date strings even when a few records contain impossible dates.
Question 840
For an original SnowPro Core educational scenario, consider: An ETL script blindly casts ISO date strings even when a few records contain impossible dates. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Replace invalid numeric values with zero without logging or analyzing the data-quality impact.
- Change: Express supported filters and transformations as Snowpark operations and use governed execution runtimes for Python-specific steps.
- Check: Count conversion failures, review source examples and reconcile accepted versus quarantined records.
- Check: Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA.
- Change: Use suitable TRY_TO_NUMBER or TRY_TO_DATE style conversions with separate bad-record detection and remediation.
Explanation
Correct Answer
C: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. Acceptance: Valid values are typed correctly and bad data is isolated rather than silently misreported.
E: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. Evidence: Count conversion failures, review source examples and reconcile accepted versus quarantined records.
Incorrect Answers
A:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. 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.
B:Change: Express supported filters and transformations as Snowpark operations and use governed execution runtimes for Python-specific steps. 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.
D:Check: Compare actual refresh lag, failures, dependency graphs and credits against required reporting SLA. 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.