Snowflake SnowPro Core Practice Test 57
Question 560
For an original SnowPro Core educational scenario, consider: A team proposes FORCE=TRUE for every COPY retry and later sees duplicate business transactions. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Compare source filenames, last loaded status, COPY output and business key counts before retry.
- Change: Review COPY load history and file metadata, using a deliberate replay or idempotent merge design when reprocessing is truly required.
- Change: Use COPY INTO <table> from the intended stage with correct file format, privileges and explicit source scope.
- Check: Inspect generated files, line headers and byte sizes across representative export volumes.
- Always use FORCE=TRUE on routine repeated COPY statements to ensure nothing is skipped.
Explanation
Correct Answer
A:Snowflake tracks staged-file loading metadata to help avoid accidental repeat loads, but forcing reloads can create duplicate rows. Acceptance: Recovery loads only missing or intentionally replaced records without accidental duplicates.
B:Snowflake tracks staged-file loading metadata to help avoid accidental repeat loads, but forcing reloads can create duplicate rows. Evidence: Compare source filenames, last loaded status, COPY output and business key counts before retry.
Incorrect Answers
C:Change: Use COPY INTO <table> from the intended stage with correct file format, privileges and explicit source scope. A team proposes FORCE=TRUE for every COPY retry and later sees duplicate business transactions.
D:Check: Inspect generated files, line headers and byte sizes across representative export volumes. Snowflake tracks staged-file loading metadata to help avoid accidental repeat loads, but forcing reloads can create duplicate rows.
E:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Snowflake tracks staged-file loading metadata to help avoid accidental repeat loads, but forcing reloads can create duplicate rows.
Question 561
A Snowflake engineer is examining this platform situation: A streaming application drops small JSON files in a cloud stage every minute but analysts need new rows without hourly manual COPY jobs. A proposed shortcut is: Resume a normal virtual warehouse every minute because Snowpipe cannot load without customer-managed warehouse compute. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Resume a normal virtual warehouse every minute because Snowpipe cannot load without customer-managed warehouse compute.
- Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions.
- Implement a supported Snowpipe Streaming client or connector path to ingest rows directly into the intended table.
- Configure appropriate COPY INTO location output options such as HEADER and MAX_FILE_SIZE where supported.
Explanation
Correct Answer
B:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. Applied case: A streaming application drops small JSON files in a cloud stage every minute but analysts need new rows without hourly manual COPY jobs.
Incorrect Answers
A:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
C:Implement a supported Snowpipe Streaming client or connector path to ingest rows directly into the intended table. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
D:Configure appropriate COPY INTO location output options such as HEADER and MAX_FILE_SIZE where supported. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
Question 562
A Snowflake implementation review finds: A streaming application drops small JSON files in a cloud stage every minute but analysts need new rows without hourly manual COPY jobs. The team proposes: Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
- Export file count and formatting depend on supported COPY output settings and result volume; exact file counts can vary with parallel execution.
- Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
- COPY error handling can abort or skip selected failures, so successful command completion does not guarantee that every source record was accepted.
Explanation
Correct Answer
C:Demonstrable success requires: Incoming valid files appear after the expected ingestion delay with observable pipe failures. Applied case: A streaming application drops small JSON files in a cloud stage every minute but analysts need new rows without hourly manual COPY jobs.
Incorrect Answers
A:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
B:Export file count and formatting depend on supported COPY output settings and result volume; exact file counts can vary with parallel execution. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
D:This option addresses a different Snowflake technical topic (COPY error handling and validation) rather than the documented Snowpipe continuous file ingestion decision.
Question 563
The data platform team has not yet approved changes. Current evidence indicates: A streaming application drops small JSON files in a cloud stage every minute but analysts need new rows without hourly manual COPY jobs. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Compare stage definitions, cloud locations, LIST output and COPY source paths for a known test file.
- Inspect location, partition definitions, metadata refresh and query against known source files.
- Inspect pipe status, cloud notifications or REST submissions, ingestion history and loaded row latency.
- Validate representative source rows, projected fields and conversion failures against target schema.
Explanation
Correct Answer
C:This check tests the actual data, compute or access boundary before an operationally risky change. Applied case: A streaming application drops small JSON files in a cloud stage every minute but analysts need new rows without hourly manual COPY jobs.
Incorrect Answers
A:Compare stage definitions, cloud locations, LIST output and COPY source paths for a known test file. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
B:Inspect location, partition definitions, metadata refresh and query against known source files. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
D:Validate representative source rows, projected fields and conversion failures against target schema. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
Question 564
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A streaming application drops small JSON files in a cloud stage every minute but analysts need new rows without hourly manual COPY jobs. 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.
- Additive supported changes load safely and incompatible changes receive a review rather than silent corruption.
- Intended files are discovered from the configured stage without exposing unrelated buckets or users' private stages.
- Required events arrive with observable offsets and no undocumented replay gaps.
- Incoming valid files appear after the expected ingestion delay with observable pipe failures.
Explanation
Correct Answer
D:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. The result must be validated using the documented dataset or access context.
Incorrect Answers
A:Additive supported changes load safely and incompatible changes receive a review rather than silent corruption. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
B:Intended files are discovered from the configured stage without exposing unrelated buckets or users' private stages. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
C:Required events arrive with observable offsets and no undocumented replay gaps. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
Question 565
An implementation sign-off request identifies the following problem: A streaming application drops small JSON files in a cloud stage every minute but analysts need new rows without hourly manual COPY jobs. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Define external tables with supported file format, partition metadata and refresh or notification configuration. Verify: Inspect location, partition definitions, metadata refresh and query against known source files.
- Change: Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions. Verify: Inspect pipe status, cloud notifications or REST submissions, ingestion history and loaded row latency.
- Change: Evaluate the connector's supported ingestion mode and configure Snowpipe Streaming or file-based Snowpipe intentionally. Verify: Inspect connector configuration, ingestion channels or stages, offset handling and end-to-end lag.
- 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.
Explanation
Correct Answer
B:The change is successful only when: Incoming valid files appear after the expected ingestion delay with observable pipe failures.
Incorrect Answers
A:Change: Define external tables with supported file format, partition metadata and refresh or notification configuration. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
C:Change: Evaluate the connector's supported ingestion mode and configure Snowpipe Streaming or file-based Snowpipe intentionally. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
D:Change: Choose the correct Snowflake internal or external stage and refer to its supported @stage path in COPY operations.
Question 566
A Snowflake engineer is examining this platform situation: A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically. A proposed shortcut is: Resume a normal virtual warehouse every minute because Snowpipe cannot load without customer-managed warehouse compute. 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.
- Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions.
- Define and apply a suitable named or inline CSV file format with delimiter, quoting, header and NULL settings.
- Resume a normal virtual warehouse every minute because Snowpipe cannot load without customer-managed warehouse compute.
Explanation
Correct Answer
B:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. Applied case: A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically.
Incorrect Answers
A:Evaluate the connector's supported ingestion mode and configure Snowpipe Streaming or file-based Snowpipe intentionally. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
C:Define and apply a suitable named or inline CSV file format with delimiter, quoting, header and NULL settings. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
D:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. Use this instead: Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions.
Question 567
A Snowflake implementation review finds: A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically. The team proposes: Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
- Snowpipe Streaming writes records directly without staged intermediate files, unlike file-based Snowpipe.
- Ingestion observability requires per-file and per-row evidence; event receipt alone does not prove records reached the destination.
- COPY parsing depends on file format parameters; incorrect assumptions about fields can corrupt typed columns without changing the source file.
Explanation
Correct Answer
A:Demonstrable success requires: Incoming valid files appear after the expected ingestion delay with observable pipe failures. Applied case: A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically.
Incorrect Answers
B:Snowpipe Streaming writes records directly without staged intermediate files, unlike file-based Snowpipe. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
C:This option addresses a different Snowflake technical topic (COPY history and ingestion troubleshooting) rather than the documented Snowpipe continuous file ingestion decision.
D:COPY parsing depends on file format parameters; incorrect assumptions about fields can corrupt typed columns without changing the source file. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
Question 568
The data platform team has not yet approved changes. Current evidence indicates: A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically. 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.
- Validate representative source rows, projected fields and conversion failures against target schema.
- Check client-channel status, offset or commit acknowledgement and measured end-to-end event latency.
- Inspect pipe status, cloud notifications or REST submissions, ingestion history and loaded row latency.
Explanation
Correct Answer
D:This check tests the actual data, compute or access boundary before an operationally risky change. Applied case: A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically.
Incorrect Answers
A:Inspect notification integration status, cloud subscription routing and sample arrival events. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
B:Validate representative source rows, projected fields and conversion failures against target schema. A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically.
C:Check client-channel status, offset or commit acknowledgement and measured end-to-end event latency. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
Question 569
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically. 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.
- Incoming valid files appear after the expected ingestion delay with observable pipe failures.
- Recovery loads only missing or intentionally replaced records without accidental duplicates.
- The destination contains only intended typed columns and malformed conversions are handled explicitly.
- Parsed columns and nulls match source semantics across representative rows.
Explanation
Correct Answer
A:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. The approved implementation step was: Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions.
Incorrect Answers
B:Recovery loads only missing or intentionally replaced records without accidental duplicates. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
C:The destination contains only intended typed columns and malformed conversions are handled explicitly. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
D:Parsed columns and nulls match source semantics across representative rows. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
Question 570
For an original SnowPro Core educational scenario, consider: A team creates a pipe without any event notification or planned file submission and assumes all future objects will load automatically. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Resume a normal virtual warehouse every minute because Snowpipe cannot load without customer-managed warehouse compute.
- Check: Inspect generated files, line headers and byte sizes across representative export volumes.
- Change: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
- Change: Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions.
- Check: Inspect pipe status, cloud notifications or REST submissions, ingestion history and loaded row latency.
Explanation
Correct Answer
D:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. Evidence: Inspect pipe status, cloud notifications or REST submissions, ingestion history and loaded row latency.
E:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. Required intervention: Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions.
Incorrect Answers
A: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 pipe without any event notification or planned file submission and assumes all future objects will load automatically.
B:Check: Inspect generated files, line headers and byte sizes across representative export volumes. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
C:Change: Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing. Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches.
