How can you monitor data lineage changes when data pipelines are updated?

• A. Lineage is not supported
• B. Only monitor data volumes
• C. Observe lineage updates in the catalog, monitor changes in pipeline definitions, and validate that lineage reflects the latest data movement.
• D. Lineage never changes

Answer: (C)

When pipelines are updated, lineage changes because the paths data takes, the transformations applied, and the final destinations can all shift. The best way to monitor this is to keep the lineage metadata in the catalog in sync with the actual pipeline definitions: watch for updates in the catalog’s lineage graph and for changes in the pipelines themselves, then verify that the stored lineage now matches the latest data movement. This means after a deployment, you check that new sources, transformed edges, and new or updated destinations are reflected in the lineage, and you run validation to ensure the lineage graph accurately represents what the pipeline moved. Using versioned pipelines and automated reconciliation checks helps catch drift quickly, rather than assuming lineage stays the same or focusing only on data volumes.