Exam DP-203 topic 1 question 93 discussion

Answer is Tumbling : Link : https://learn.microsoft.com/en-us/azure/data-factory/concepts-pipeline-execution-triggers#trigger-type-comparison "Retry capability Supported. Failed pipeline runs have a default retry policy of 0, or a policy that's specified by the user in the trigger definition. Automatically retries when the pipeline runs fail due to concurrency/server/throttling limits (that is, status codes 400: User Error, 429: Too many requests, and 500: Internal Server error)" Retry capability is not supported on Schedule trigger

Tumbling because "following a restart of the trigger." Schedule does not support restart capability https://learn.microsoft.com/en-us/azure/data-factory/concepts-pipeline-execution-triggers#trigger-type-comparison

B. tumbling

A tumbling window trigger runs at a specified interval, and if the trigger stops, it maintains its schedule when restarted. This ensures the pipeline executes exactly at 2 AM daily, even after a trigger restart. Tumbling windows are useful for consistent execution without overlap or gaps, which makes them ideal for daily fixed scheduling like in this scenario.

A tumbling window trigger runs at a specified interval, and if the trigger stops, it maintains its schedule when restarted. This ensures the pipeline executes exactly at 2 AM daily, even after a trigger restart. Tumbling windows are useful for consistent execution without overlap or gaps, which makes them ideal for daily fixed scheduling like in your scenario.

This question is not clear enough. "If a pipeline stops" can mean many different things.

Schedule at 1 , repeat once, delay 60 minutes

I'll go for A based on the use cases provided Microsoft Data Platform MVP: https://www.cathrinewilhelmsen.net/triggers-azure-data-factory/

You set up a tumbling window trigger with a window size of 1 hour and a start time of 2 AM. The trigger fires automatically at 2 AM every hour. If the trigger encounters an outage and misses a window (e.g., cannot execute at 2 AM), it automatically resumes at the beginning of the next window (i.e., at 3 AM). This ensures that the pipeline executes at 2 AM after the restart, effectively catching up for the missed execution.

in this scenario, the requirement is to execute the pipeline at a specific time every day (2 AM) and ensure that if the trigger stops, the next pipeline execution occurs at 2 AM following a restart of the trigger. A tumbling window trigger might not guarantee that the pipeline always runs at exactly 2 AM daily, especially if the trigger stops and restarts at different times. https://learn.microsoft.com/en-us/azure/data-factory/concepts-pipeline-execution-triggers#tumbling-window-trigger https://learn.microsoft.com/en-us/azure/data-factory/concepts-pipeline-execution-triggers#schedule-trigger-with-json

The answer is B Tumbling window trigger is more specific .The pipeline is trigger every 24hrs which is how a tumbling window funtion works. Scheduler is general . One can say that a schedule trigger is called Tumbling trigger when it works at non overlapping equal intervals of time just as in the pipeline case study

A Tumbling widow trigger is more specific. Scheduler is general . I can say this Schedule trigger is called Tumbling trigger..

The tumbling window trigger run waits for the triggered pipeline run to finish. Its run state reflects the state of the triggered pipeline run. For example, if a triggered pipeline run is cancelled, the corresponding tumbling window trigger run is marked cancelled. This is different from the "fire and forget" behavior of the schedule trigger, which is marked successful as long as a pipeline run started. https://learn.microsoft.com/en-us/azure/data-factory/concepts-pipeline-execution-triggers#trigger-type-comparison

I believe it's tumbling, It doesn't say that if the trigger fails from the get-go, but if it stops, and in schedule, the state of a pipe is successful if the pipeline ran at first "The tumbling window trigger run waits for the triggered pipeline run to finish. Its run state reflects the state of the triggered pipeline run. For example, if a triggered pipeline run is cancelled, the corresponding tumbling window trigger run is marked cancelled. This is different from the "fire and forget" behavior of the schedule trigger, which is marked successful as long as a pipeline run started." https://learn.microsoft.com/en-us/azure/data-factory/concepts-pipeline-execution-triggers#trigger-type-comparison

Looks to me like Tumbling

Schedule triggers allow you to schedule pipelines to run at specific times and intervals. They are also idempotent, which means that if a pipeline execution fails due to a trigger failure, the next pipeline execution will still occur at the scheduled time.

"following a restart of the trigger" sounds a lot like a "retry" and only tumbling would offer a retry not schedule.