nerdexam
Microsoft

DP-600 · Question #29

You have a Fabric tenant that contains a lakehouse named Lakehouse1. Lakehouse1 contains a table named Tablet. You are creating a new data pipeline. You plan to copy external data to Table1. The…

The correct answer is B. From the Destination tab, set Table action to Overwrite. To satisfy both requirements - replacing the schema of Table1 with the external data's schema, and replacing all existing data - the correct setting is to set Table action to 'Overwrite' on the Destination tab (B). The Overwrite action drops and recreates the destination table…

Submitted by chiamaka_o· Apr 18, 2026Prepare and serve data

Question

You have a Fabric tenant that contains a lakehouse named Lakehouse1. Lakehouse1 contains a table named Tablet. You are creating a new data pipeline. You plan to copy external data to Table1. The schema of the external data changes regularly. You need the copy operation to meet the following requirements:

  • Replace Table1 with the schema of the external data.
  • Replace all the data in Table1 with the rows in the external data.

You add a Copy data activity to the pipeline. What should you do for the Copy data activity?

Options

  • AFrom the Source tab, add additional columns.
  • BFrom the Destination tab, set Table action to Overwrite.
  • CFrom the Settings tab, select Enable staging.
  • DFrom the Source tab, select Enable partition discovery.
  • EFrom the Source tab, select Recursively.

How the community answered

(30 responses)
  • A
    3% (1)
  • B
    83% (25)
  • C
    3% (1)
  • D
    10% (3)

Explanation

To satisfy both requirements - replacing the schema of Table1 with the external data's schema, and replacing all existing data - the correct setting is to set Table action to 'Overwrite' on the Destination tab (B). The Overwrite action drops and recreates the destination table using the source schema, then loads all source rows. This handles schema drift automatically. 'Append' would add rows without schema changes. Adding additional columns (A) enriches source data but does not replace the table. Enabling staging (C) improves performance for large loads but does not address schema replacement. Partition discovery (D) and recursive copy (E) are source-side options unrelated to destination table management.

Topics

#Fabric Data Pipelines#Copy data activity#Lakehouse#Data ingestion strategy

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DP-600 Practice