DEA-C02 · Question #60
A Data Engineer would like to define a file structure for loading and unloading data. Where can the file structure be defined? (Choose three.)
The correct answer is A. COPY command C. FILE FORMAT object E. STAGE object. In Snowflake, file structure (format) for loading/unloading data can be defined in three places: the COPY INTO command allows inline FILE_FORMAT options directly in the statement; a FILE FORMAT object is a named, reusable schema object that encapsulates format settings (CSV delim
Question
A Data Engineer would like to define a file structure for loading and unloading data. Where can the file structure be defined? (Choose three.)
Options
- ACOPY command
- BMERGE command
- CFILE FORMAT object
- DPIPE object
- ESTAGE object
- FINSERT command
How the community answered
(46 responses)- A78% (36)
- B7% (3)
- D2% (1)
- F13% (6)
Explanation
In Snowflake, file structure (format) for loading/unloading data can be defined in three places: the COPY INTO command allows inline FILE_FORMAT options directly in the statement; a FILE FORMAT object is a named, reusable schema object that encapsulates format settings (CSV delimiters, JSON strip nulls, Parquet compression, etc.); and a STAGE object can have a file format baked in at creation time, so any COPY that references that stage inherits the format automatically.
The distractors fail because MERGE (B) and INSERT (F) are standard DML statements that operate on table rows - they have no concept of external file structure. PIPE (D) is a Snowpipe automation object that references a COPY command internally, but the file structure lives in that embedded COPY, not in the PIPE definition itself.
Memory tip: Think "CSE" - COPY command, Stage object, filE format object - the three places where you tell Snowflake how a file is shaped before data ever touches a table.
Topics
Community Discussion
No community discussion yet for this question.