A Fabric notebook ingestion process must run daily at 7:00 AM and retry up to two times if source missing; minimal development effort. Which approach meets this?

• A. Create a pipeline. Add Notebook1 to the pipeline. Schedule the pipeline to run daily.
• B. Create a pipeline with Notebook1 added three times with dependencies; schedule daily.
• C. From the Notebook schedule, configure daily runs and retry settings.
• D. Create individual notebooks for each run and time segment.

Answer: (A)

The key idea here is to orchestrate a daily ingestion with a single, reusable workflow that can handle automatic retries. Put Notebook1 into a pipeline and schedule that pipeline to run every day at 7:00 AM. This creates one centralized process you can manage and monitor, and you can configure a retry policy on the pipeline so that if the source is missing, it will automatically retry up to two times. This approach satisfies the “minimal development effort” requirement because you avoid duplicating notebooks or building multiple separate run configurations.

Adding the notebook three times with dependencies would add unnecessary complexity and maintenance overhead. Relying on the Notebook’s own scheduling alone can work, but it scatters scheduling and retry behavior across notebooks instead of keeping them in one place. Creating separate notebooks for each run and time segment multiplies artifacts and makes updates harder to propagate.