COF-C03 Data Loading, Unloading, and Connectivity Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  COPY INTO my_table FROM 'file:///tmp/data.csv'

  Why it's wrong here

  COPY INTO cannot read directly from a local filesystem path. The FROM clause must reference a stage, an external location, or a table, not a file:// URI. Snowflake has no access to the client's local disk, so this statement would error out. Local files must first be uploaded with PUT to a stage before COPY INTO can read them.

• ✗

  PUT file:///tmp/data.csv @my_table

  Why it's wrong here

  The PUT command uploads a local file to a stage, but its target must be a stage, not a table. Using @my_table as the target is invalid syntax and would fail. Even if corrected to a stage, PUT alone does not load data into the table; a separate COPY INTO is required to move the staged file into the table.

• ✗

  COPY INTO my_table FROM @my_named_stage

  Why it's wrong here

  This command references a named internal stage, which the engineer explicitly wants to avoid creating. While it would work if the stage already existed and the file had been PUT to it, it does not match the requirement of the simplest path without a named stage. It also omits the file format and the actual file upload step.

• ✓

  PUT file:///tmp/data.csv @%my_table; then COPY INTO my_table FROM @%my_table

  Why this is correct

  The table stage @%my_table is created automatically with the table, so no named stage is needed. PUT uploads the local CSV to that table stage, and COPY INTO reads it into the table. This two-step sequence is the standard simplest path for loading a local file without creating a separate named internal stage.