In Fabric, which statement best describes data lineage?

• A. Data lineage is not supported in Fabric.
• B. Data lineage records the origin and transformations of data, enabling impact analysis and governance.
• C. Data lineage is solely for security auditing and offers no governance benefits.
• D. Data lineage only tracks ingestion timestamps.

Answer: (B)

Data lineage traces where data comes from, how it moves, and what transformations it undergoes. In Fabric, this visibility lets you map the origin of a dataset, the steps applied along the way, and where the results wind up, which is essential for governance and impact analysis. When changes occur upstream, you can quickly see which reports, dashboards, or downstream datasets are affected, assess risk, and ensure data quality and regulatory compliance. That’s why the statement describing lineage as recording origin and transformations and enabling impact analysis and governance is the best fit. The other options miss the mark: data lineage is supported in Fabric, it isn’t solely for security auditing and doesn’t ignore governance benefits, and it doesn’t only track ingestion timestamps.