DP-203 · Question #89
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. Get Metadata alone retrieves file-level metadata but does not write that metadata into Table1. The activity returns the DateTime value as a pipeline variable/expression, but it cannot by itself insert rows or map that value as a column in the destination table - a separate…
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this scenario, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure Synapse Analytics dedicated SQL pool that contains a table named Table1. You have files that are ingested and loaded into an Azure Data Lake Storage Gen2 container named container1. You plan to insert data from the files into Table1 and azure Data Lake Storage Gen2 container named container1. You plan to insert data from the files into Table1 and transform the data. Each row of data in the files will produce one row in the serving layer of Table1. You need to ensure that when the source data files are loaded to container1, the DateTime is stored as an additional column in Table1. Solution: In an Azure Synapse Analytics pipeline, you use a Get Metadata activity that retrieves the DateTime of the files. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(17 responses)- A18% (3)
- B82% (14)
Explanation
Get Metadata alone retrieves file-level metadata but does not write that metadata into Table1. The activity returns the DateTime value as a pipeline variable/expression, but it cannot by itself insert rows or map that value as a column in the destination table - a separate loading step is still required.
Why "Yes" (A) is wrong: Simply reading the DateTime from a file does not fulfill the full requirement. The pipeline must also pass that DateTime value into the data load step (e.g., a Copy Data activity with "Additional columns" configured, or a Mapping Data Flow with a derived column). Get Metadata is just a prerequisite step, not a complete solution on its own.
The correct approach would be to use a Mapping Data Flow with a derived column transformation that references the file's last modified date, or configure a Copy Data activity's Additional Columns feature to inject the file DateTime as a column during the load - either of these would meet the goal end-to-end.
Memory tip: Think of Get Metadata as a "read-only scout" - it finds information about a file but never touches the destination table. If the goal involves writing a value into Table1, you need an activity that actually performs the write (Copy Data or Data Flow). Whenever a solution uses Get Metadata alone for a transformation goal, the answer is almost always No.
Topics
Community Discussion
No community discussion yet for this question.