Question 380
For this Snowflake situation — A source provider sends multiple compressed Parquet files and wants Snowflake to ingest them without converting to CSV. — the team adopts: Use a compatible Parquet file format and a COPY INTO operation against the approved stage. Which ongoing practice BEST limits the same problem recurring?
Explanation
Correct Answer
The relevant ongoing safeguard is: Retest schema and data type mappings after upstream exports change. It controls the recurring exposure associated with this mechanism: Snowflake supports bulk loading of supported columnar file formats from stages. The original action, use a compatible Parquet file format and a COPY INTO operation against the approved stage., still needs operational checks when the environment or workload changes.
Incorrect Answers
The suggested review tracks a different technical risk: File format settings govern how Snowflake interprets staged file bytes before loading. Here the sustained control must address: Snowflake supports bulk loading of supported columnar file formats from stages. Choose “Retest schema and data type mappings after upstream exports change”.
This routine guards against another mechanism: Scheduled SQL tasks and direct streaming ingestion solve different arrival and processing patterns. The recurring exposure in the current case is: Snowflake supports bulk loading of supported columnar file formats from stages. The matching preventive check is “Retest schema and data type mappings after upstream exports change”.
The suggested review tracks a different technical risk: JDBC supplies a standard driver interface for compatible client applications, distinct from direct browser interfaces. Here the sustained control must address: Snowflake supports bulk loading of supported columnar file formats from stages. Choose “Retest schema and data type mappings after upstream exports change”.