An engineer wants to stage local files that relate to exactly one target table, without creating any stage object first, and references the staged files when running COPY INTO that table. Which stage should the engineer use, and how is it referenced?
- AThe table stage referenced as @%target_table, because each table has an implicit stage that needs no separate creation and is intended for files loaded into that one table Correct
- BA user stage referenced as @~, because every user receives a personal staging area that is automatically scoped to whichever single table they later load data into from it
- CA named internal stage referenced as @my_stage, because Snowflake provisions one named stage for each table at creation time so files placed there load only into that table
- DAn external stage referenced as @ext_stage, because external stages need no object creation and automatically bind themselves to the one table named in the following COPY INTO command
Why A is correct: Every table has an implicit table stage addressed as @%table_name that requires no CREATE STAGE step, making it the right fit for files destined for that single table.
Why B is wrong: The user stage exists per user and is referenced with @~, but it is not tied to one table, so the automatic single-table scoping claimed here is wrong.
Why C is wrong: A named stage must be explicitly created with CREATE STAGE and is not auto-provisioned per table, so this both invents a stage and contradicts the no-create requirement.
Why D is wrong: External stages must be created and point at cloud storage rather than a single table, so the no-creation and auto-binding claims here are both incorrect.