Answer: Execute the pipeline.

## Explanation To ensure updated lineage information becomes available in Microsoft Purview after modifying an Azure Data Factory pipeline, the correct first step is to **execute the pipeline**. ### Why Option B is Correct: - **Automatic Lineage Capture**: When Azure Data Factory is properly connected and registered with Microsoft Purview, lineage data is automatically captured during pipeline execution. The Copy activity and Dataflow activities generate lineage information as they process data. - **Execution Triggers Lineage Generation**: The actual data movement and transformation operations that occur during pipeline execution are what generate the lineage metadata. Without execution, there is no operational data to create lineage from. - **Real-time Synchronization**: Microsoft Purview receives lineage information in near real-time as the pipeline activities run, ensuring the updated lineage reflects the current pipeline configuration. ### Why Other Options Are Incorrect: - **Option A (Disconnect Microsoft Purview account)**: This would break the integration entirely and prevent any lineage data from being sent to Purview. - **Option C (Execute Azure DevOps build pipeline)**: While DevOps pipelines can deploy Data Factory resources, they don't directly trigger lineage capture in Purview. Lineage is generated during Data Factory pipeline execution, not during deployment. - **Option D (Locate related asset in Microsoft Purview portal)**: This is a passive action that doesn't trigger lineage updates. You would only see existing lineage information, not generate updated lineage from the modified pipeline. ### Best Practice Consideration: The integration between Azure Data Factory and Microsoft Purview is designed to automatically capture lineage during execution without requiring manual intervention or additional configuration steps. This ensures data governance remains current with operational changes.

Author: LeetQuiz Editorial Team