To orchestrate this workflow in Microsoft Fabric, a data pipeline is the correct tool. The pipeline's schedule must be configured to run daily at 07:00 UTC (E). Inside the pipeline, the Notebook activity for Notebook1 needs its retry policy set to 2 to handle transient failures as required (A). To ensure the semantic model is refreshed only upon the successful completion of the data ingestion and transformation steps, the Semantic model refresh activity must be linked to the Notebook activity using the "On success" dependency condition (C). This creates a sequential, conditional workflow that meets all specified requirements.

B. The "On completion" condition would trigger the refresh regardless of whether the notebook succeeded or failed, which violates the requirement to refresh only after successful execution.

D. The orchestration and scheduling are managed by the pipeline, not the individual notebook's schedule settings. The pipeline's schedule controls the entire workflow's execution time.

F. The requirement explicitly states that Notebook1 should be retried, not the semantic model refresh activity. Applying the retry setting to the wrong activity fails to meet the requirement.

1. Pipeline Scheduling (Option E): Microsoft Learn. (2024). Schedule data pipelines in Microsoft Fabric. "You can run a data pipeline on-demand or on a schedule... You can also select a specific time zone that the schedule's start and end dates will be based on." This confirms that scheduling

including time zone

is a pipeline-level setting.

Source: Microsoft Fabric Documentation

"Schedule data pipelines in Microsoft Fabric".

2. Activity Retry Policy (Option A): Microsoft Learn. (2024). Activity policy settings in Data Factory for Microsoft Fabric. "You can use activity policies to configure the runtime behavior of an activity... Retry: Number of retries. The maximum is 10." This shows that retry settings are configured per activity within a pipeline.

Source: Microsoft Fabric Documentation

"Activity policy settings in Data Factory for Microsoft Fabric".

3. Activity Dependencies (Option C): Microsoft Learn. (2024). How to add activities to a pipeline. "You can chain two activities by dragging the output of one activity to the input of another... The default dependency is On success." This documentation explains how to link activities and specifies the "On success" condition

which ensures the second activity runs only if the first one succeeds.

Source: Microsoft Fabric Documentation

"How to add activities to a pipeline".

4. Notebook and Refresh Activities: Microsoft Learn. (2024). How to use Notebook activity in a pipeline and Semantic model refresh activity in Data Factory for Microsoft Fabric. These documents confirm that both running a notebook and refreshing a semantic model are available as distinct activities that can be added to and orchestrated within a Fabric data pipeline.

Source: Microsoft Fabric Documentation.