Tableau Server checks for data-driven alert conditions based on two primary triggers. First, there is a server-wide background process that checks alerts at a configurable frequency. By default, this interval is set to every 60 minutes. Second, for any view that is built upon a data extract, the alert condition is specifically checked immediately after the scheduled refresh for that extract completes. This ensures that alerts are evaluated against the most current data available in the extract. These two mechanisms work together to provide timely notifications when data crosses a specified threshold.

B. Every 10 minutes: This frequency is too high. The default and most frequent server-wide check interval for data-driven alerts is 60 minutes, not 10.

C. Whenever a new extract is published: Publishing a new extract is a one-time setup event. Alert checks are recurring processes tied to scheduled refreshes of existing extracts, not the initial publication.

1. Tableau Server Documentation, "Send Data-Driven Alerts from Tableau Server":

Reference for A: In the section "How data-driven alerts work," the documentation states, "By default, Tableau Server checks every 60 minutes to see if data conditions for alerts are true." This directly supports the 60-minute interval.

Reference for D: In the same section, it clarifies the behavior for extracts: "If the view uses an extract, the alert runs on the extract's refresh schedule." This confirms that extract refreshes are a primary trigger.

2. Tableau Server Documentation, "tsm configuration set Options":

Reference for A & B: The configuration key dataAlerts.checkIntervalInMinutes controls the server-wide check frequency. The documentation specifies its default value is 60. This confirms that 60 minutes is the standard interval and that 10 minutes is not the default.