Azure Data Factory Scheduled Trigger Configuration

Data Factory Triggers

You have an Azure Data Factory pipeline named P1. You need to schedule P1 to run at 10:15 AM, 12:15 PM, 2:15 PM, and 4:15 PM every day. Which frequency and interval should you configure for the scheduled trigger?

Frequency: Month -
Frequency: Day - Source Reference Answer
Frequency: Minute -
Frequency: Hour -

Community Votes

65%

35%

65% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The question tests the understanding that a single scheduled trigger can execute multiple times per day by specifying discrete hours/minutes, rather than requiring hourly frequency or multiple separate triggers.

This question tests the correct configuration of Azure Data Factory scheduled triggers to run a pipeline multiple times within a single day. The community consensus, supported by exam reports, indicates that 'Frequency: Day' is the intended answer, leveraging the trigger's ability to specify multiple hours and minutes.

Candidates often select Option D (Hourly) because the intervals are two hours apart. However, Hourly frequency with an interval of 2 would continue running indefinitely throughout the day, failing to stop after the last specified time (4:15 PM).

Community Discussion (6 comments)

Saranya22 👍 6 Selected: D

The frequency of Hour with an interval of 2 would run the pipeline every 2 hours.

erz 👍 5 Selected: B

The frequency is a Day and interval 1, since every day should execute 4x. Within a day 4 times are fixed.

renan_ineu 👍 1 Selected: B

Frequency is 1 day (every day). After choosing the frequency (recurrence), set the hours and the minutes. No need to create one for each hour, because the setting accepts several hours and minutes. In Linux, this would be a cron setting: 15 10,12,14,16 The fields, separated by a space are: minute hour day-of-month month week-day This means that the task will run: every minute 15 on every hours 10, 12, 14 and 16 on every day of the month on every month no matter which day-of-week it falls It is possible to read that the frequency is "every 2h, every day, every week, every month, and every year", but for the Data Factory configuration, the recurrence is "day". Attention here: ADF calls it recurrence, not frequency. Looks the same, but the ogres that write these questions may decide to whatever they want. Other Linux cron doing the same, to be more clear: 15 10-16/2 15 10-16/2 /1 /1 *

Alongi 👍 1 Selected: B

I found this question on my exam 30/04/2024, and I put B. I passed the exam with a high score, but I'm not sure if the answer is correct.

Delphin_8150 👍 2 Selected: B

Correct me if I am wrong guys, but if option B is correct does that mean you have to create 4 separate triggers with the Frequency: Day and Interval: 1? If that is the case then I am more inclined to B, since D will still run even after 4:15PM. If we want it to run only for the 4 times specified above then B is a more accurate answer.

Alongi 👍 2 Selected: B

Interval Day. You have to schedule 4 trigger but daily

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Option B is correct because Azure Data Factory scheduled triggers allow you to define a recurrence based on days, where you can specify exact hours and minutes for execution. By setting Frequency to Day and configuring the specific hours (10, 12, 14, 16) and minutes (15), the trigger executes exactly at those four times each day and then stops until the next day.

Why the Other Options Are Wrong

Option D (Hourly) is incorrect because it implies a continuous recurrence pattern. An hourly trigger with an interval of 2 would run at 10:15, 12:15, 14:15, 16:15, 18:15, 20:15, etc., violating the requirement to run only at the specified four times. Options A (Month) and C (Minute) do not fit the daily recurring schedule described.

Community Comment Notes

Comment [5] provides valuable context by comparing the behavior to a Linux cron expression (15 10,12,14,16 *), which accurately reflects how the trigger handles multiple discrete times within a day. Comments [1] and [3] correctly identify why Hourly fails (it doesn't stop after 4:15 PM). Comment [6] confirms this was a real exam question in April 2024, validating the official stance.

Official Reference

https://learn.microsoft.com/en-us/azure/data-factory/how-to-create-scheduled-trigger#schedule-tab

Exam Strategy

When scheduling multiple executions per day, look for the 'Day' frequency option combined with specific hour/minute inputs. Avoid 'Hourly' unless the requirement is for continuous execution without a defined end time within the cycle.

Related Analysis

← Back to DP-203 Study Guide