What should you do to schedule Notebook1 to run daily as part of an ingestion workflow?

What should you do to schedule Notebook1 to run daily as part of an ingestion workflow?

• A. Create a notebook with a built-in scheduler and run daily.
• B. Create a dataflow and schedule it.
• C. Create a pipeline. Add Notebook1 to the pipeline. Schedule the pipeline to run daily.
• D. Use an external orchestrator to trigger Notebook1.

Answer: (C)

Use a pipeline to orchestrate the daily run of Notebook1. Pipelines let you assemble the steps of an ingestion workflow, add notebooks as tasks, define the order and dependencies, and schedule the whole process to execute on a regular cadence. By adding Notebook1 to the pipeline and scheduling the pipeline to run daily, Notebook1 becomes a defined part of a repeatable, observable workflow with built-in monitoring and retry behavior. This keeps scheduling centralized and aligned with the ingestion process. Other approaches—scheduling the notebook directly, building a separate dataflow, or triggering the notebook from an external orchestrator—either duplicate functionality, require extra setup, or don’t automatically tie Notebook1 into the end-to-end workflow.

Use a pipeline to orchestrate the daily run of Notebook1. Pipelines let you assemble the steps of an ingestion workflow, add notebooks as tasks, define the order and dependencies, and schedule the whole process to execute on a regular cadence. By adding Notebook1 to the pipeline and scheduling the pipeline to run daily, Notebook1 becomes a defined part of a repeatable, observable workflow with built-in monitoring and retry behavior. This keeps scheduling centralized and aligned with the ingestion process. Other approaches—scheduling the notebook directly, building a separate dataflow, or triggering the notebook from an external orchestrator—either duplicate functionality, require extra setup, or don’t automatically tie Notebook1 into the end-to-end workflow.