SnowPro Associate: Platform Question 58
Single answer○ Create objects (for example: databases, schemas, stages)A data engineering team needs a landing area for CSV files generated by an internal process that runs on a developer's workstation. They want to create the Snowflake objects needed so the files can be uploaded with the PUT command and later loaded into a table in the SALES_RAW schema. The engineer wants the stage to be available only within that schema and not visible as a standalone named object across the account. Which approach should the engineer use?
- A
Create an internal named stage in the SALES_RAW schema using CREATE STAGE, then use PUT to upload the files to that stage.
- B
Create an external stage in the SALES_RAW schema pointing to the developer's local file system, then use PUT to upload the files.
- C
Create a temporary stage at the account level so it is hidden from other schemas, then use PUT to upload the files.
- D
Use the table stage for the target table in SALES_RAW and upload the files there with PUT instead of creating a named stage.
Show answer and explanation
Correct answer: D
Explanation
This question tests practical knowledge of creating and using Snowflake objects for data loading. Snowflake supports three main stage types relevant at the associate level: named stages, table stages, and user stages. Named stages are explicit schema objects created with CREATE STAGE. Table stages and user stages are automatically available internal stages and do not require separate creation. The PUT command uploads data only to internal stages, not external stages. External stages are metadata objects that reference files already stored in supported cloud storage services and cannot reference a local workstation. Because the requirement is to keep the stage scoped to the schema's loading target without creating a visible standalone object, the table stage is the most appropriate choice. This aligns with Snowflake documentation on stages, CREATE STAGE, and PUT/COPY workflows.
- A. Incorrect.
Incorrect. A named internal stage created with CREATE STAGE would work for storing files and receiving uploads from PUT, but the scenario specifically says the engineer does not want the stage visible as a standalone named object. A named stage is a schema-level object and is explicitly created and managed as its own object.
- B. Incorrect.
Incorrect. External stages reference cloud storage locations such as Amazon S3, Google Cloud Storage, or Azure Blob Storage. They do not point to a developer's local file system. In addition, PUT uploads files from a local file system only to internal stages, not external stages.
- C. Incorrect.
Incorrect. Snowflake does not support an account-level temporary stage object for this use case. Temporary objects exist for certain object types such as tables, but a stage is created within a database and schema context. This option also incorrectly suggests that PUT would target an account-level temporary stage.
- D. Correct.
Correct. Snowflake automatically provides table stages, user stages, and named stages. A table stage is tied to a specific table and is not a standalone named object in the schema. PUT can upload files from a local file system to internal stages, including a table stage. Since the files are intended to be loaded into a table in SALES_RAW and the team wants to avoid creating a separate named stage, using the target table's table stage is the best fit.