A data engineer needs a personal staging area to hold ad hoc files that may later be loaded into several different tables, and does not want to create any stage object or share the files with teammates. Which Snowflake stage best meets this need?
- AA table stage, addressed as @%orders, because the implicit per-table stage is private to the user and can stage files that load into several different tables at once
- BThe user stage, addressed as @~, because each user automatically has a private staging area that holds files for loading into any tables the user can access Correct
- CA named internal stage, addressed as @adhoc_stage, because it is private to the creating user by default and requires no CREATE STAGE statement before files can be uploaded
- DAn external stage, addressed as @adhoc_ext, because it gives each user a private cloud area with no setup that can feed loads into many different tables freely
Why A is wrong: A table stage is private but is tied to its one table, so it cannot serve files destined for several different tables, which breaks the multi-table requirement.
Why B is correct: Each Snowflake user has an implicit private user stage referenced with @~ that needs no creation and can stage files bound for many tables, matching every part of the requirement.
Why C is wrong: A named internal stage is shareable via grants and must be created explicitly, so the private-by-default and no-creation claims here are both wrong.
Why D is wrong: An external stage points at customer cloud storage and must be configured first, so it is neither per-user private nor setup-free as this option asserts.