Join the H13-531 Discussion
mark
Commented on July 26, 2025
very informative
EUROPEAN UNION
gm
Commented on July 26, 2025
Question 77: Answer should be all
Bulk copy from an External Stage:
This involves using the COPY INTO command to load data from files stored in external cloud storage locations (e.g., Amazon S3, Azure Blob Storage, Google Cloud Storage) into a Snowflake table.
Continuous load using Snowpipe REST API:
Snowpipe enables continuous data loading from staged files as soon as they become available. The Snowpipe REST API can be used to trigger the loading process for new files in an external stage.
The Snowflake Web Interface (UI) data loading wizard:
Snowsight, Snowflake's web interface, provides a user-friendly wizard that guides users through the process of loading data into tables, often from local files or staged files.
Bulk copy from an Internal Stage:
Similar to external stages, data can be bulk loaded from internal stages (storage locations within Snowflake) into tables using the COPY INTO command. Files can be placed in internal stages using commands like PUT.
Anonymous
gm
Commented on July 26, 2025
Question 68:
Explanation:
INSERT:
When inserting data into a table, Snowflake usually writes to new partitions, allowing other queries to access the existing data simultaneously.
COPY:
Similar to INSERT, the COPY command often writes to new partitions, enabling parallel execution with other operations.
Why other options are incorrect:
UPDATE:
This command modifies existing data in a table, which requires locking the affected rows to prevent conflicts. This makes it a blocking operation, meaning other queries that need to access the same rows will have to wait until the UPDATE finishes.
MERGE:
Like UPDATE, the MERGE command modifies data in a table, requiring locks and thus being a blocking operation. It combines data from multiple sources into a target table, which can involve modifying existing rows.
Anonymous