DEA-C02 Data Movement 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.

• ✗

  MAX_FILE_SIZE = 64 and SINGLE = FALSE

  Why it's wrong here

  MAX_FILE_SIZE is expressed in bytes, not megabytes, so a value of 64 would target 64-byte files, which is unusable for a large fact table. SINGLE = FALSE is appropriate for parallelism, but the size parameter is wrong by six orders of magnitude. The engineer must specify the byte equivalent of 64 MB.

• ✗

  MAX_FILE_SIZE = 67108864 and SINGLE = TRUE

  Why it's wrong here

  SINGLE = TRUE forces the unload into one file, which conflicts with the requirement for many small files that the downstream consumer can process in parallel. MAX_FILE_SIZE is correct, but it becomes effectively irrelevant because a single output file is produced. This option satisfies the size cap only if the total output happens to be small.

• ✓

  MAX_FILE_SIZE = 67108864 and SINGLE = FALSE

  Why this is correct

  MAX_FILE_SIZE caps the size of each output file using a byte value, and 67108864 bytes equals 64 MB. SINGLE = FALSE allows Snowflake to produce multiple files across the available parallelism, which suits the consumer's need for many small files. This combination directly meets both stated requirements for the unload.

• ✗

  FILE_FORMAT = (TYPE = CSV COMPRESSION = GZIP) and SINGLE = FALSE

  Why it's wrong here

  Compression and multi-file output are useful, but nothing here enforces a 64 MB per-file ceiling. Without MAX_FILE_SIZE, Snowflake sizes files based on parallelism and data volume, so individual files could exceed the consumer's limit. This option addresses file count but not the explicit size constraint in the scenario.