An Azure SQL Database source feeds a silver Delta table in Microsoft Fabric. The source customer table receives inserts, updates, and physical deletes, and the silver layer must reflect deletes as well as changes. The source already has a feature enabled that exposes which rows changed since a given version through a system function, without storing the full before-and-after column values. Which source change-detection mechanism does this describe, and is it sufficient to drive the load?
- AIt describes a high-water-mark watermark on a LastModified column, which is sufficient because the maximum timestamp identifies every insert, update, and delete to apply.
- BIt describes change data capture, which is sufficient because it retains the full before-and-after column images of every changed row in dedicated capture tables.
- CIt describes a OneLake shortcut to the source, which is sufficient because the shortcut surfaces source deletes automatically without any change-detection query.
- DIt describes change tracking, which is sufficient because it returns the keys and change type of rows changed since a version, including deletes, so the load can apply each change. Correct
Why A is wrong: A LastModified watermark catches inserts and updates but cannot reveal physically deleted rows, since a deleted row leaves no timestamp to compare; it is tempting but misses the delete requirement entirely.
Why B is wrong: Change data capture does retain full before-and-after column images, but the scenario states the feature does not store full column values; that detail rules out change data capture even though it would also handle deletes.
Why C is wrong: A shortcut exposes existing data in place and is not a row-level change-detection mechanism; it does not tell the load which rows changed or were deleted since a version, so it cannot drive an incremental upsert-and-delete.
Why D is correct: Change tracking records which rows changed and the operation type, including deletes, by version without retaining column history; the changed keys plus change type let the load upsert and remove rows, which is exactly what is needed.