Subdomain 1.4: Orchestrate processes
1.An operations team wants a nightly pipeline to keep running indefinitely with no planned end. When they open the pipeline's schedule configuration, they find they cannot leave the end date blank. What should they do to achieve an effectively open-ended schedule?
- A.Set the schedule's end date far into the future, such as 01/01/2099, since Fabric schedules always require both a start and an end date.
- B.Leave the end date field empty and save the schedule, since Fabric interprets a blank end date as an open-ended recurrence.
- C.Configure an interval-based schedule instead, since interval-based schedules support truly open-ended, unbounded recurrence windows.
- D.Attach an event-based trigger in addition to the schedule, since combining both removes the end-date requirement for the fixed schedule.
Show answer & explanation
Correct answer: A — Set the schedule's end date far into the future, such as 01/01/2099, since Fabric schedules always require both a start and an end date.
- A. Setting the end date far in the future is correct because Fabric requires both a start and end date for a fixed schedule, with no option for a truly open-ended schedule.
- B. Leaving the end date blank is incorrect because Fabric does not accept an empty end date; a start and end date must both be specified when configuring a schedule.
- C. Interval-based schedules still require configured, non-overlapping fixed intervals and are not a way to bypass the end-date requirement of a fixed schedule.
- D. Adding an event-based trigger runs alongside a schedule but does not change or remove the end-date requirement on the fixed schedule itself.