Snowflake SnowPro Core Practice Test 60
Question 590
For an original SnowPro Core educational scenario, consider: Two pipelines listen to the same bucket and one receives unexpected files outside its designated prefix. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Change: Configure supported event or notification integrations and stage prefixes with appropriate subscription permissions.
- Check: Test stage preview, file-format properties and sample loaded row values including quoted delimiters.
- Check: Inspect notification integration status, cloud subscription routing and sample arrival events.
- Assume defining an external stage alone subscribes Snowflake to every cloud storage event.
- Change: Configure appropriate COPY INTO location output options such as HEADER and MAX_FILE_SIZE where supported.
Explanation
Correct Answer
A:Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage. Acceptance: Only files in the configured scope trigger ingestion and missing notifications are detectable.
C:Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage. Required intervention: Configure supported event or notification integrations and stage prefixes with appropriate subscription permissions.
Incorrect Answers
B:Check: Test stage preview, file-format properties and sample loaded row values including quoted delimiters. Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage.
D:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage.
E:Change: Configure appropriate COPY INTO location output options such as HEADER and MAX_FILE_SIZE where supported. Two pipelines listen to the same bucket and one receives unexpected files outside its designated prefix.
Question 591
A Snowflake engineer is examining this platform situation: A daily ingestion adds an optional attribute and fails because its target schema was fixed before the new field appeared. A proposed shortcut is: Enable schema evolution and assume every arbitrary type change is automatically harmless. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
- Correlate COPY_HISTORY, pipe diagnostics, stage listings and target row checks to isolate load versus transformation failures.
- Enable schema evolution and assume every arbitrary type change is automatically harmless.
- Choose the correct Snowflake internal or external stage and refer to its supported @stage path in COPY operations.
Explanation
Correct Answer
A:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. Applied case: A daily ingestion adds an optional attribute and fails because its target schema was fixed before the new field appeared.
Incorrect Answers
B:Correlate COPY_HISTORY, pipe diagnostics, stage listings and target row checks to isolate load versus transformation failures. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
C:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
D:Choose the correct Snowflake internal or external stage and refer to its supported @stage path in COPY operations. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
Question 592
A Snowflake implementation review finds: A daily ingestion adds an optional attribute and fails because its target schema was fixed before the new field appeared. The team proposes: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
- Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage.
- JSON loading preserves semi-structured structure that can be navigated or transformed later, unlike flat delimiter parsing.
- Stages identify files in Snowflake-managed or external cloud storage, and their scopes and access methods differ.
Explanation
Correct Answer
A:Demonstrable success requires: Additive supported changes load safely and incompatible changes receive a review rather than silent corruption. This principle explains the proposed technical approach, which is: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
Incorrect Answers
B:Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
C:JSON loading preserves semi-structured structure that can be navigated or transformed later, unlike flat delimiter parsing. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
D:Stages identify files in Snowflake-managed or external cloud storage, and their scopes and access methods differ. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
Question 593
The data platform team has not yet approved changes. Current evidence indicates: A daily ingestion adds an optional attribute and fails because its target schema was fixed before the new field appeared. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Check export query permissions, target path, file format, partitioning and sample file contents.
- Compare source row count, COPY result error counts, rejected records and target count.
- Compare source schema, table evolution settings, COPY metadata and downstream validation tests.
- Inspect stage LIST, COPY validation or output and load history for the specified file set.
Explanation
Correct Answer
C:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. If confirmed, the proportionate intervention is: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
Incorrect Answers
A:Check export query permissions, target path, file format, partitioning and sample file contents. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
B:Compare source row count, COPY result error counts, rejected records and target count. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
D:Inspect stage LIST, COPY validation or output and load history for the specified file set. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
Question 594
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A daily ingestion adds an optional attribute and fails because its target schema was fixed before the new field appeared. 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.
- Recipients can parse exported records within their documented file constraints.
- Parsed columns and nulls match source semantics across representative rows.
- New staged files are enumerable through governed metadata without inventing extracted textual content.
- Additive supported changes load safely and incompatible changes receive a review rather than silent corruption.
Explanation
Correct Answer
D:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. The approved implementation step was: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
Incorrect Answers
A:Recipients can parse exported records within their documented file constraints. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
B:Parsed columns and nulls match source semantics across representative rows. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
C:New staged files are enumerable through governed metadata without inventing extracted textual content. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
Question 595
An implementation sign-off request identifies the following problem: A daily ingestion adds an optional attribute and fails because its target schema was fixed before the new field appeared. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Use COPY INTO <location> with a supported file format, target stage or secure external location and governed permissions. Verify: Check export query permissions, target path, file format, partitioning and sample file contents.
- Change: Review COPY load history and file metadata, using a deliberate replay or idempotent merge design when reprocessing is truly required. Verify: Compare source filenames, last loaded status, COPY output and business key counts before retry.
- Change: Choose the correct Snowflake internal or external stage and refer to its supported @stage path in COPY operations. Verify: Compare stage definitions, cloud locations, LIST output and COPY source paths for a known test file.
- Change: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing. Verify: Compare source schema, table evolution settings, COPY metadata and downstream validation tests.
Explanation
Correct Answer
D:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. The change is successful only when: Additive supported changes load safely and incompatible changes receive a review rather than silent corruption.
Incorrect Answers
A:Change: Use COPY INTO <location> with a supported file format, target stage or secure external location and governed permissions. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
B:Change: Review COPY load history and file metadata, using a deliberate replay or idempotent merge design when reprocessing is truly required. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
C:Change: Choose the correct Snowflake internal or external stage and refer to its supported @stage path in COPY operations. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
Question 596
A Snowflake engineer is examining this platform situation: A feed changes an amount column from integer to text and management expects all historical numeric reports to remain correct. A proposed shortcut is: Enable schema evolution and assume every arbitrary type change is automatically harmless. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Evaluate the connector's supported ingestion mode and configure Snowpipe Streaming or file-based Snowpipe intentionally.
- Use supported SELECT transformations in COPY INTO from the staged source with explicit casts and column mapping.
- Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
- Enable schema evolution and assume every arbitrary type change is automatically harmless.
Explanation
Correct Answer
C:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. Applied case: A feed changes an amount column from integer to text and management expects all historical numeric reports to remain correct.
Incorrect Answers
A:Evaluate the connector's supported ingestion mode and configure Snowpipe Streaming or file-based Snowpipe intentionally. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
B:Use supported SELECT transformations in COPY INTO from the staged source with explicit casts and column mapping. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
D:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. Use this instead: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
Question 597
A Snowflake implementation review finds: A feed changes an amount column from integer to text and management expects all historical numeric reports to remain correct. The team proposes: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior.
- Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
- Snowflake tracks staged-file loading metadata to help avoid accidental repeat loads, but forcing reloads can create duplicate rows.
- Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage.
Explanation
Correct Answer
B:Demonstrable success requires: Additive supported changes load safely and incompatible changes receive a review rather than silent corruption. Applied case: A feed changes an amount column from integer to text and management expects all historical numeric reports to remain correct.
Incorrect Answers
A:Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
C:Snowflake tracks staged-file loading metadata to help avoid accidental repeat loads, but forcing reloads can create duplicate rows. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
D:Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage. A feed changes an amount column from integer to text and management expects all historical numeric reports to remain correct.
Question 598
The data platform team has not yet approved changes. Current evidence indicates: A feed changes an amount column from integer to text and management expects all historical numeric reports to remain correct. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect notification integration status, cloud subscription routing and sample arrival events.
- Test a connection with the intended library, role, warehouse, TLS and a representative query.
- Inspect connector configuration, ingestion channels or stages, offset handling and end-to-end lag.
- Compare source schema, table evolution settings, COPY metadata and downstream validation tests.
Explanation
Correct Answer
D:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. Confirm afterward that: Additive supported changes load safely and incompatible changes receive a review rather than silent corruption.
Incorrect Answers
A:Inspect notification integration status, cloud subscription routing and sample arrival events. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
B:Test a connection with the intended library, role, warehouse, TLS and a representative query. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
C:Inspect connector configuration, ingestion channels or stages, offset handling and end-to-end lag. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
Question 599
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A feed changes an amount column from integer to text and management expects all historical numeric reports to remain correct. 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.
- Analysts can query approved external data while file ownership and metadata freshness remain explicit.
- Additive supported changes load safely and incompatible changes receive a review rather than silent corruption.
- The destination contains only intended typed columns and malformed conversions are handled explicitly.
- Recovery loads only missing or intentionally replaced records without accidental duplicates.
Explanation
Correct Answer
B:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Analysts can query approved external data while file ownership and metadata freshness remain explicit. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
C:The destination contains only intended typed columns and malformed conversions are handled explicitly. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
D:Recovery loads only missing or intentionally replaced records without accidental duplicates. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
Question 600
For an original SnowPro Core educational scenario, consider: A feed changes an amount column from integer to text and management expects all historical numeric reports to remain correct. Select THREE compatible elements: a proper correction, a targeted diagnostic and an acceptance result.
- Check: Compare source schema, table evolution settings, COPY metadata and downstream validation tests.
- Result: Parsed columns and nulls match source semantics across representative rows.
- Change: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
- Check: Compare source row count, COPY result error counts, rejected records and target count.
- Change: Use supported SELECT transformations in COPY INTO from the staged source with explicit casts and column mapping.
- Result: Additive supported changes load safely and incompatible changes receive a review rather than silent corruption.
Explanation
Correct Answer
A:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. Required intervention: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
C:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. Acceptance: Additive supported changes load safely and incompatible changes receive a review rather than silent corruption.
F:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. Evidence: Compare source schema, table evolution settings, COPY metadata and downstream validation tests.
Incorrect Answers
B:Result: Parsed columns and nulls match source semantics across representative rows. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
D:Check: Compare source row count, COPY result error counts, rejected records and target count. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
E:Change: Use supported SELECT transformations in COPY INTO from the staged source with explicit casts and column mapping. Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
