To meet the requirement of a date dimension spanning 2010 through the end of the current year, which method can be used to populate the date dimension table?

• A. Dataflow
• B. Copy activity in a pipeline
• C. T-SQL view
• D. Stored procedure in a pipeline

Answer: (A)

Generating a calendar date range inside a data transformation flow is the most straightforward way to populate a date dimension. A dataflow lets you define a start date (2010-01-01) and an end date (the end of the current year) and produce one row per date, then derive useful attributes (year, month, quarter, day, day of week, etc.) all within the same flow. Finally, you load that enriched set into the date dimension table. This approach doesn’t rely on an existing source of dates or on a SQL engine outside the data flow, and it can adapt automatically as the current year changes.

Copying data would require an existing source of dates to copy from, which isn’t suitable for generating a brand-new calendar. A T-SQL view can show data but doesn’t populate the table by itself. A stored procedure in a pipeline could populate the table, but it relies on SQL code outside the flow; the dataflow option is typically more integrated and flexible for this kind of date-dimension generation within Fabric.