Develop data processing →mediumMultiple ChoiceObjective-mapped

DP-203 Develop data processing Practice Question

Exhibit

{
  "name": "CopyTradeData",
  "properties": {
    "activities": [
      {
        "name": "CopyData",
        "type": "Copy",
        "inputs": [{"referenceName": "SourceDataset", "type": "DatasetReference"}],
        "outputs": [{"referenceName": "SinkDataset", "type": "DatasetReference"}],
        "typeProperties": {
          "source": {
            "type": "AzureBlobStorageSource",
            "recursive": true
          },
          "sink": {
            "type": "AzureSqlSink",
            "writeBatchSize": 10000,
            "preCopyScript": "TRUNCATE TABLE dbo.Trades"
          }
        }
      }
    ]
  }
}

Refer to the exhibit. You have an Azure Data Factory pipeline that copies trade data from Azure Blob Storage to Azure SQL Database. The pipeline runs every hour and truncates the destination table before each copy. However, users report that data is missing during the copy window. What is the most likely cause?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The preCopyScript truncates the table before the copy completes, causing a period with no data

The preCopyScript truncates the destination table before the copy operation begins. During the copy window, if the copy takes time or fails, the table remains empty, causing users to see missing data. Option A is incorrect because the output dataset configuration does not cause this issue. Option B is incorrect because writeBatchSize affects performance but not data loss. Option D is incorrect because recursive setting affects source file selection, not data loss.

Answer analysis

Option-by-option breakdown

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

✗
The output dataset is not correctly configured
Why it's wrong here
It is configured.
✗
The writeBatchSize is too low, causing timeouts
Why it's wrong here
Does not cause data loss.
✓
The preCopyScript truncates the table before the copy completes, causing a period with no data
Why this is correct
Table is empty during copy.
✗
The source dataset is set to recursive, which includes unwanted files
Why it's wrong here
Recursive only affects file discovery.

Quick reference

Azure Blob Storage Tier Comparison

Tier	Storage Cost	Retrieval Cost	Latency	Use Case
Hot	Highest	Lowest	Immediate	Active data, frequent reads
Cool	Lower	Higher	Immediate	Data accessed < once / month
Cold	Lower still	Higher	Immediate	Data accessed < once / quarter
Archive	Lowest	Highest + rehydration delay	Hours	Long-term compliance retention

Go deeper

DP-203 Develop data processing Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Azure Blob Storage Tier Comparison

Related to this question