Fabric Copy Activity Partitioning Prerequisites

You have a Fabric tenant that contains a lakehouse named Lakehouse1. Lakehouse1 contains an unpartitioned table named Table1. You plan to copy data to Table1 and partition the table based on a date column in the source data. You create a Copy activity to copy the data to Table1. You need to specify the partition column in the Destination settings of the Copy activity. What should you do first?

  1. From the Destination tab, set Mode to Append.
  2. From the Destination tab, select the partition column.
  3. From the Source tab, select Enable partition discovery.
  4. From the Destination tabs, set Mode to Overwrite. Correct Answer
Answer Correct answer: D — Set the Mode to Overwrite in the Destination tab to enable partition column selection.

Community Insight

The exam tests the specific dependency between the Table Action (Overwrite) and the visibility of the Partition Columns configuration in the Destination tab.

In Microsoft Fabric, configuring partition columns in a Copy activity requires the table action to be set to Overwrite. This question establishes that Overwrite mode is the mandatory prerequisite for accessing partition settings.

Many learners choose Append because they associate partitioning with incremental data loads, but Fabric's Copy activity only exposes partition options when Overwrite is selected.

Community Discussion (28 comments)

ViniciusPA 👍 1 Selected: A
Quando o modo está como Sobrescrever, o particionamento fica desabilitado, porque sobrescrever recria a tabela inteira e ignora partições. Portanto, o correto é A. Na aba Destino, definir o Modo como Anexar.
snowq 👍 1 Selected: A
The key detail is that Table1 is currently unpartitioned. In Fabric Copy Activity, you cannot select a partition column until the destination table is already configured to append data into partitions.
Sowwy1 👍 1 Selected: D
I think it s D
evest 👍 1 Selected: A
In the info i next to Enable partitions is said "Create partitions in folder structure based on one or multiple columns. Each distinct column value (pair) will be a new partition (e.g. year=2000/month=01/file). It supports insert-only mode and requires an empty directory in sink." In this case there is a Table1 and it is not mentioned that it is empty. But we want a working solution that is why Append seams to be more certain answer.
KitHsia 👍 1 Selected: D
I'll go with A or D. I just found that 'Enable partitions' is available in both Overwrite and Append modes.
KitHsia 👍 1
It will goes C if the source data is a file, you must first select 'Enable partitions' in the Source section.
8b9f9a0 👍 1 Selected: A
In Fabric’s Copy activity, the option to specify a partition column in the Destination settings is only available when the write mode is set to “Append”.
dee2593 👍 1 Selected: A
In Fabric Data Pipeline’s Copy activity, when you load data into a Delta table (like your Lakehouse table), partitioning settings for the destination are only available in Append mode. If the mode is Overwrite, partition settings won’t appear because the table would be fully replaced. Once you set Mode = Append, you’ll see the option to specify a partition column in the Destination tab. Why not the others? B. From the Destination tab, select the partition column → You can’t select it until you switch to Append mode. C. From the Source tab, select Enable partition discovery → That’s for reading partitioned data from the source, not for writing with partitioning in the destination.
dee2593 👍 1
correction is: Option D; https://learn.microsoft.com/en-us/fabric/data-factory/tutorial-lakehouse-partition#load-data-to-lakehouse-using-partition-columns
Pegooli 👍 4 Selected: A
In Microsoft Fabric, partitioning a table during a Copy activity is only supported in "Append" mode, not "Overwrite" mode.
praticewizards 👍 2 Selected: A
To partition data in a destination table, you need to ensure that new data is appended. Setting the mode to "Append" is the first step because: Partitioning requires Append mode. Overwrite mode would replace the entire table, negating any partitioning structure you aim to achieve. Once Append mode is set, you can specify the partition column in the Destination settings. Why not the other options? B. From the Destination tab, select the partition column: You cannot select the partition column until the mode is set to Append first. C. From the Source tab, select Enable partition discovery: This option is useful for discovering partitions in source data, but it is unrelated to configuring partitioning in the destination table. D. From the Destination tab, set Mode to Overwrite: Overwrite mode deletes existing data in the table, which contradicts the goal of appending and partitioning the data.
emboutchamani 👍 1 Selected: A
What should you do first ? Before setting partition you have to set mode toappend after you can select partition column
emboutchamani 👍 1
correction: D
Brainny 👍 1
C. The "first" thing to do is to Enable Partition Discovery from the Source tab, this will enable the destination tab identify the partition column, then the destination tab can be set to overwrite. https://learn.microsoft.com/en-us/fabric/data-factory/connector-lakehouse-copy-activity
a2675f7 👍 1
only when the source table is partitioned first... Enable partition discovery: For files that are partitioned, specify whether to parse the partitions from the file path and add them as extra source columns, in this case source is unpartitioned
Pegooli 👍 1 Selected: C
Enabling partition discovery on the Source tab allows the Copy activity to recognize the partition structure of the incoming data. This step is essential because it ensures that the data is copied into the destination table (Table1) with the correct partitions based on the specified date column.
dev2dev 👍 1 Selected: D
those who still think B is the answer, emphasis on "What should you do first?"
Data_Works 👍 1 Selected: D
D. From the Destination tabs, set Mode to Overwrite. in the question, it is specified that "we are going to specify the partition column". Yes, we will do that, BUT before that we have to set the "Table action" option to "Overwrite". say, if you first set the partition column & after that you select the "overwrite" mode, then the selected partition column will be cleared & you will have to select that again. And "overwrite" is necessary because the table is not currently partitioned. we need to re-write the existing data leveraging partition.
282b85d 👍 3 Selected: C
Enable Partition Discovery: This option ensures that the Copy activity can identify the partition column and apply it correctly to the destination table. By enabling partition discovery, you make sure that the source data's partitioning information is considered during the copy process. Why Not: A. From the Destination tab, set Mode to Append: This setting controls how data is added to the existing table (whether new data is appended or existing data is overwritten). It does not directly address partitioning setup. B. From the Destination tab, select the partition column: While this is necessary to specify the partition column, it is logically the next step after enabling partition discovery. The system needs to recognize partitions before you can configure them. D. From the Destination tabs, set Mode to Overwrite: Similar to the Append mode, this setting determines how data is handled during the copy process but does not enable partitioning.
David_Webb 👍 1 Selected: D
Partition option need to switch to Overwrite mode first.
stilferx 👍 4 Selected: D
IMHO, the answer is "D". Because: Expand Advanced, in Table action, select Overwrite, and then select Enable partition, under Partition columns, select Add column, and choose the column you want to use as the partition column. You can choose to use a single column or multiple columns as the partition column. in https://learn.microsoft.com/en-us/fabric/data-factory/tutorial-lakehouse-partition#load-data-to-lakehouse-using-partition-columns
VAzureD 👍 7 Selected: D
D. From the Destination tabs, set Mode to Overwrite. https://learn.microsoft.com/en-us/fabric/data-factory/tutorial-lakehouse-partition#load-data-to-lakehouse-using-partition-columns Expand Advanced, in Table action, select Overwrite, and then select Enable partition, under Partition columns, select Add column, and choose the column you want to use as the partition column. You can choose to use a single column or multiple columns as the partition column.
emmanuelkech 👍 3 Selected: B
From the Destination tab, select the partition column. This ensures that the data is partitioned based on the specified column in the destination table
estrelle2008 👍 6 Selected: D
A makes no sense, it leaves data that is already in table1 unpartitioned B makes no sense, it is the statement that you are asked to decide for the step before that. C MIGHT assign date column in source data as requested partition column, but only and if source data is complete and unambiguous D re-creates table1, ensuring that the partitioning is applied consistently. Hoping that the data that is already in table1 is also in this source data, D should be recommended answer, I guess?
lengzhai 👍 4 Selected: D
D is correct. Partition is available when Overwrite is checked
SamuComqi 👍 15 Selected: D
D. From the Destination tabs, set Mode to Overwrite. When setting up the Copy Activity, you need to choose the Overwrite mode to make the partition option appear (not visibile in Append mode).
Momoanwar 👍 3 Selected: C
I think its C. For partition in pipeline we have to specify column in source
Bharat 👍 1
The table is unpartitioned to begin with.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

To specify a partition column in the Destination settings of a Copy activity in Microsoft Fabric, you must first set the Table action to Overwrite. According to official documentation, the 'Enable partition' option and the ability to select partition columns are only available under Advanced settings when Overwrite is chosen. This ensures the entire dataset is re-partitioned consistently.

Why the Other Options Are Wrong

Append mode does not expose partition column selection in the UI; it simply adds data without restructuring existing partitions in the same way. Selecting the partition column directly is impossible until the correct mode (Overwrite) is active. Enable partition discovery is a source-side feature for detecting folder structures, not a prerequisite for defining destination partition columns in this context.

Community Comment Notes

Community consensus strongly favors D, with users noting that the partition option remains hidden or disabled unless Overwrite is selected. One user clarified that while Append is common for partitions in other tools, Fabric's implementation here specifically requires Overwrite to apply the partition structure during the copy.

Official Reference

Exam Strategy

Always verify if the tool requires a specific mode (like Overwrite vs. Append) to unlock advanced features like partitioning. In Fabric Data Factory, assume Overwrite is needed for complex schema or partition modifications unless stated otherwise.

Frequently Asked Questions

Why can't I use Append mode for partitioning?

In Microsoft Fabric Copy activities, partition column configuration is only exposed when the Table action is set to Overwrite.

Is partition discovery needed for Lakehouse tables?

Partition discovery helps identify source folder structures, but it is not the primary step for defining destination partition columns.

More DP-600 FAQ →

Related Analysis

Practice All DP-600 Questions

Access 115 questions with complete answers and detailed explanations.

View Full DP-600 Practice Test →

← Back to DP-600 Study Guide