An analyst has a notebook that cleans and reshapes raw ingest data, and three teams now depend on running it themselves before reporting. What should change?
Select an answer to reveal the explanation.
Short Explanation
When three teams depend on it, you're in production—and a notebook someone runs by hand isn't production. Move the transformation into a managed pipeline, publish a governed output table, and let the teams query it directly.
Full Explanation
The correct choice is moving the transformation into a managed pipeline that publishes a governed output table the teams query directly. Once multiple consumers depend on a transformation, it needs the properties of production code: a defined schedule, versioning, monitoring, and a single governed output table. The pipeline provides that and reduces the consumers' job to querying a table.
Sharing the notebook more widely and documenting the cell execution order carefully is incorrect because documentation does not make manual execution reliable. Three teams running the same notebook produce three results whenever anyone runs it at a different time or skips a cell.
Having each team maintain its own copy of the notebook so they can adapt it to their needs is incorrect because per-team copies guarantee divergence. Within weeks the definitions differ and no two reports reconcile.
Scheduling the notebook to email its output as a spreadsheet each morning is incorrect because emailed spreadsheets leave the platform entirely - no governance, no lineage, no way to know which version anyone is looking at.
For the exam, treat shared dependence on a manual artefact as the trigger for promoting it to a governed pipeline.