An analytics engineer must make a large Delta table that lives in an Azure Data Lake Storage Gen2 container queryable from a "Lakehouse" in "Microsoft Fabric". The source team continues to write to that container hourly, the data must not be copied or duplicated into "OneLake", and queries must always reflect the latest writes. Which ingestion approach meets the requirement?
- ABuild a "Dataflows Gen2" query that reads the container and loads the rows into a managed Delta table in the "Lakehouse" on an hourly schedule.
- BConfigure a data pipeline Copy activity that moves the Delta files into the "Lakehouse" Files area each hour using an incremental watermark column.
- CCreate a "OneLake" shortcut in the "Lakehouse" that points at the Azure Data Lake Storage Gen2 location holding the Delta table. Correct
- DAuthor a notebook that runs COPY INTO against the storage path to bulk-load the Delta table into a "Lakehouse" table on each trigger.
Why A is wrong: A dataflow physically loads rows into "OneLake", which duplicates the data and leaves the copy stale between scheduled runs, breaking the no-copy and always-current requirements.
Why B is wrong: A Copy activity physically duplicates the files into "OneLake" and only refreshes on schedule, so it violates both the no-duplication rule and the always-current requirement.
Why C is correct: A shortcut is a reference, so the table appears in the "Lakehouse" without copying data and every query reads through to the current files the source team writes.
Why D is wrong: COPY INTO ingests by writing the rows into a target table, which copies the data into "OneLake" and leaves it stale until the next run rather than referencing the source live.