Which method helps ensure lineage reflects the latest data movement after pipeline updates?

• A. Rely on automatic lineage updates without checks.
• B. Ignore lineage during updates.
• C. Regularly replay pipeline executions and refresh lineage metadata in the catalog.
• D. Only track data volumes.

Answer: (A)

Maintaining accurate data lineage after pipeline updates requires validating the actual data movement that occurs with the current pipeline configuration. When pipelines change—new steps, altered data sources or targets, or modified transforms—the paths data takes and the relationships between datasets can shift. If you rely on automatic lineage updates without checks, you risk having a lineage record that doesn’t match reality, which can hamper impact analysis and governance.

Replaying pipeline executions and refreshing the lineage metadata in the catalog ensures the lineage graph reflects the true data movement for the latest pipeline, including any new steps or changed connections. This explicit refresh captures the exact sources, transformations, and destinations involved, providing an up-to-date, auditable view of data lineage.

In contrast, ignoring lineage during updates or only tracking data volumes fails to capture how data moves and how its provenance changes. Relying solely on automatic updates without validation can also lead to gaps or inconsistencies in the lineage information.