Snowflake SnowPro Core Practice Test 67
Question 660
For an original SnowPro Core educational scenario, consider: A team assumes every Kafka connector deployment automatically uses the same direct-streaming channel as a Snowpipe Streaming client. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Inspect connector configuration, ingestion channels or stages, offset handling and end-to-end lag.
- Change: Correlate COPY_HISTORY, pipe diagnostics, stage listings and target row checks to isolate load versus transformation failures.
- Treat Kafka topic retention and Snowflake COPY file-load history as exactly the same mechanism.
- Check: Inspect generated files, line headers and byte sizes across representative export volumes.
- Change: Evaluate the connector's supported ingestion mode and configure Snowpipe Streaming or file-based Snowpipe intentionally.
Explanation
Correct Answer
A:Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior. Required intervention: Evaluate the connector's supported ingestion mode and configure Snowpipe Streaming or file-based Snowpipe intentionally.
E:Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior. Evidence: Inspect connector configuration, ingestion channels or stages, offset handling and end-to-end lag.
Incorrect Answers
B:Change: Correlate COPY_HISTORY, pipe diagnostics, stage listings and target row checks to isolate load versus transformation failures. Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior.
C:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior.
D:Check: Inspect generated files, line headers and byte sizes across representative export volumes. Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior.
Question 661
A Snowflake engineer is examining this platform situation: A data lake owner wants SQL visibility over Parquet files while preserving the underlying cloud storage as source of truth. A proposed shortcut is: Delete original S3 objects immediately after creating an external table because Snowflake copied them automatically. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions.
- Delete original S3 objects immediately after creating an external table because Snowflake copied them automatically.
- Define external tables with supported file format, partition metadata and refresh or notification configuration.
- Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing.
Explanation
Correct Answer
C:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. Applied case: A data lake owner wants SQL visibility over Parquet files while preserving the underlying cloud storage as source of truth.
Incorrect Answers
A:Define a Snowpipe with its COPY statement and supported AUTO_INGEST event notifications or managed file submissions. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
B:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. For this best change assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it.
D:Apply supported schema evolution or controlled DDL changes after confirming compatible file formats and data typing. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 662
A Snowflake implementation review finds: A data lake owner wants SQL visibility over Parquet files while preserving the underlying cloud storage as source of truth. The team proposes: Define external tables with supported file format, partition metadata and refresh or notification configuration. Which platform principle most strongly supports the recommended response? Select ONE best answer.
- Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage.
- External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
- Snowpipe Streaming writes records directly without staged intermediate files, unlike file-based Snowpipe.
- Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance.
Explanation
Correct Answer
B:Demonstrable success requires: Analysts can query approved external data while file ownership and metadata freshness remain explicit. Applied case: A data lake owner wants SQL visibility over Parquet files while preserving the underlying cloud storage as source of truth.
Incorrect Answers
A:Snowpipe auto-ingest depends on cloud notifications reaching the correct pipe, not just on the existence of an S3 or Azure stage. This option addresses a different Snowflake technical topic (Cloud notification integration for auto-ingest) rather than the documented External tables and cloud file metadata decision. The case-specific mechanism is: External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. The relevant action is: Define external tables with supported file format, partition metadata and refresh or notification configuration. Discriminating evidence: Inspect location, partition definitions, metadata refresh and query against known source files. Applied case: A data lake owner wants SQL visibility over Parquet files while preserving the underlying cloud storage as source of truth.
C:Snowpipe Streaming writes records directly without staged intermediate files, unlike file-based Snowpipe. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
D:Automatic schema evolution has prerequisites and supported behaviors; incompatible type or semantic changes still require intentional governance. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 663
The data platform team has not yet approved changes. Current evidence indicates: A data lake owner wants SQL visibility over Parquet files while preserving the underlying cloud storage as source of truth. 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 generated files, line headers and byte sizes across representative export volumes.
- Inspect a staged JSON file, COPY output, TYPEOF and nested path values in loaded rows.
- Inspect location, partition definitions, metadata refresh and query against known source files.
Explanation
Correct Answer
D:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. Confirm afterward that: Analysts can query approved external data while file ownership and metadata freshness remain explicit.
Incorrect Answers
A:This option addresses a different Snowflake technical topic (Internal and external stages) rather than the documented External tables and cloud file metadata decision.
B:Inspect generated files, line headers and byte sizes across representative export volumes. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
C:Inspect a staged JSON file, COPY output, TYPEOF and nested path values in loaded rows. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 664
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A data lake owner wants SQL visibility over Parquet files while preserving the underlying cloud storage as source of truth. 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.
- Operators can explain each expected file as loaded, pending or rejected and resolve the actual cause.
- The authorized files load once into the target table with documented success or errors.
- Applications connect securely and execute only the queries their active roles permit.
Explanation
Correct Answer
A:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. The result must be validated using the documented dataset or access context.
Incorrect Answers
B:Operators can explain each expected file as loaded, pending or rejected and resolve the actual cause. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
C:The authorized files load once into the target table with documented success or errors. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
D:Applications connect securely and execute only the queries their active roles permit. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 665
An implementation sign-off request identifies the following problem: A data lake owner wants SQL visibility over Parquet files while preserving the underlying cloud storage as source of truth. Which paired technical change and validation should close the implementation review? Select ONE best answer.
- Change: Use COPY INTO <table> from the intended stage with correct file format, privileges and explicit source scope. Verify: Inspect stage LIST, COPY validation or output and load history for the specified file set.
- 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: Correlate COPY_HISTORY, pipe diagnostics, stage listings and target row checks to isolate load versus transformation failures. Verify: Inspect recent load history, file status and error messages with a controlled problem file.
- Change: Enable supported directory table metadata and maintain its refresh mechanism to inventory staged objects. Verify: Compare LIST results, directory table rows and refresh timestamp after adding a controlled file.
Explanation
Correct Answer
B:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. The change is successful only when: Analysts can query approved external data while file ownership and metadata freshness remain explicit.
Incorrect Answers
A:Change: Use COPY INTO <table> from the intended stage with correct file format, privileges and explicit source scope. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
C:Change: Correlate COPY_HISTORY, pipe diagnostics, stage listings and target row checks to isolate load versus transformation failures. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
D:Change: Enable supported directory table metadata and maintain its refresh mechanism to inventory staged objects. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 666
A Snowflake engineer is examining this platform situation: A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions. A proposed shortcut is: Delete original S3 objects immediately after creating an external table because Snowflake copied them automatically. What should the Snowflake engineer recommend as the narrowly scoped correction? Select ONE best answer.
- Use supported SELECT transformations in COPY INTO from the staged source with explicit casts and column mapping.
- Define external tables with supported file format, partition metadata and refresh or notification configuration.
- Delete original S3 objects immediately after creating an external table because Snowflake copied them automatically.
- Configure appropriate COPY INTO location output options such as HEADER and MAX_FILE_SIZE where supported.
Explanation
Correct Answer
B:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. This targeted change addresses the stated technical or governance gap without discarding necessary controls.
Incorrect Answers
A:Use supported SELECT transformations in COPY INTO from the staged source with explicit casts and column mapping. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
C:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. Use this instead: Define external tables with supported file format, partition metadata and refresh or notification configuration.
D:Configure appropriate COPY INTO location output options such as HEADER and MAX_FILE_SIZE where supported. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 667
A Snowflake implementation review finds: A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions. The team proposes: Define external tables with supported file format, partition metadata and refresh or notification configuration. 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.
- Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior.
- 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.
Explanation
Correct Answer
A:Demonstrable success requires: Analysts can query approved external data while file ownership and metadata freshness remain explicit. This principle explains the proposed technical approach, which is: Define external tables with supported file format, partition metadata and refresh or notification configuration.
Incorrect Answers
B:Kafka integrations can use different ingestion mechanisms and delivery semantics; the selected connector version and configuration determine behavior. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
C:Snowpipe Streaming writes records directly without staged intermediate files, unlike file-based Snowpipe. A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions.
D:Snowpipe processes arriving staged files on Snowflake-managed serverless compute and is designed for continuously arriving micro-batches. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 668
The data platform team has not yet approved changes. Current evidence indicates: A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions. Which evidence best tests the technical diagnosis before approving a disruptive change? Select ONE best answer.
- Inspect a staged JSON file, COPY output, TYPEOF and nested path values in loaded rows.
- Inspect location, partition definitions, metadata refresh and query against known source files.
- Compare LIST results, directory table rows and refresh timestamp after adding a controlled file.
- Inspect connector configuration, ingestion channels or stages, offset handling and end-to-end lag.
Explanation
Correct Answer
B:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. Applied case: A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions.
Incorrect Answers
A:Inspect a staged JSON file, COPY output, TYPEOF and nested path values in loaded rows. A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions.
C:Compare LIST results, directory table rows and refresh timestamp after adding a controlled file. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
D:Inspect connector configuration, ingestion channels or stages, offset handling and end-to-end lag. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 669
A candidate correction has been tested and the platform team requires a post-change acceptance check. Original problem: A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions. 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.
- Only authorized records are exported in the agreed format to a controlled destination.
- New staged files are enumerable through governed metadata without inventing extracted textual content.
- Analysts can query approved external data while file ownership and metadata freshness remain explicit.
Explanation
Correct Answer
D:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. The approved implementation step was: Define external tables with supported file format, partition metadata and refresh or notification configuration.
Incorrect Answers
A:Incoming valid files appear after the expected ingestion delay with observable pipe failures. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
B:Only authorized records are exported in the agreed format to a controlled destination. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
C:New staged files are enumerable through governed metadata without inventing extracted textual content. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
Question 670
For an original SnowPro Core educational scenario, consider: A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions. Select TWO complementary steps: the targeted correction and its strongest prechange validation.
- Check: Inspect location, partition definitions, metadata refresh and query against known source files.
- Change: Define external tables with supported file format, partition metadata and refresh or notification configuration.
- Delete original S3 objects immediately after creating an external table because Snowflake copied them automatically.
- Check: Validate representative source rows, projected fields and conversion failures against target schema.
- Change: Validate representative input with COPY validation options and set ON_ERROR according to explicit data-quality policy.
Explanation
Correct Answer
A:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. Acceptance: Analysts can query approved external data while file ownership and metadata freshness remain explicit.
B:External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables. Evidence: Inspect location, partition definitions, metadata refresh and query against known source files.
Incorrect Answers
C:For this select two assessment, the shortcut changes or bypasses the necessary correctness, governance or operational boundary rather than correcting it. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
D:Check: Validate representative source rows, projected fields and conversion failures against target schema. External tables expose metadata about data kept in cloud storage; they are not identical to internally managed loaded tables.
E:Change: Validate representative input with COPY validation options and set ON_ERROR according to explicit data-quality policy. A team expects querying an external table to automatically rewrite all cloud files into Snowflake's internal micro-partitions.
