Develop data processing →hardMultiple ChoiceObjective-mapped

DP-203 Develop data processing Practice Question

Exhibit

Refer to the exhibit.

{
  "name": "sales_orders",
  "properties": {
    "folder": "orders",
    "type": "AzureBlobFSLocation",
    "linkedServiceName": {
      "referenceName": "ADLSGen2",
      "type": "LinkedServiceReference"
    },
    "typeProperties": {
      "fileName": "sales_orders.parquet",
      "folderPath": "data/orders/year=2023/month=01/day=15/"
    },
    "compressionCodec": "snappy",
    "columnDelimiter": ","
  }
}

Refer to the exhibit. You have an Azure Data Factory dataset definition for a Parquet file stored in Azure Data Lake Storage Gen2. You attempt to use this dataset as a source in a copy activity, but the copy activity fails with an error indicating that the file is not found. The file 'sales_orders.parquet' exists at the specified path. What is the most likely cause of the error?

⚠ Common exam trap

A common mix-up: candidates assume the error is due to authentication or configuration issues (like linked service keys or location types) rather than recognizing that the dataset's explicit file name prevents ADF from scanning subdirectories for partitioned files.

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 dataset is configured with a specific file name, but the data is partitioned across multiple folders; you should use a wildcard pattern in the folderPath.

The dataset definition specifies a single file name ('sales_orders.parquet') in the 'fileName' property, but the actual data is likely stored across multiple Parquet files in a partitioned folder structure (e.g., 'sales_orders/year=2024/month=01/'). When a copy activity uses this dataset as a source, Azure Data Factory looks for the exact file name at the specified path, not finding any file because the data is spread across subfolders. Using a wildcard pattern (e.g., '*.parquet') in the 'folderPath' or setting 'fileName' to '*' allows the copy activity to read all Parquet files in the folder, resolving the 'file not found' error.

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 dataset is configured with a specific file name, but the data is partitioned across multiple folders; you should use a wildcard pattern in the folderPath.
Why this is correct
While the exhibit shows a single file, the error suggests the file is not found, likely because the dataset expects a different path structure. Using wildcards would allow the copy activity to find the file within the partition structure.
✗
The compression codec 'snappy' is not supported for Parquet files.
Why it's wrong here
Snappy is a commonly used compression codec for Parquet.
✗
The dataset type should be 'AzureBlobStorageLocation' instead of 'AzureBlobFSLocation'.
Why it's wrong here
AzureBlobFSLocation is correct for ADLS Gen2.
✗
The linked service 'ADLSGen2' is not properly configured with the storage account key.
Why it's wrong here
The error message indicates file not found, not authentication failure.

Visual reference

Go deeper

DP-203 Develop data processing Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question