Exam Databricks-Certified-Data-Analyst-Associate Topic 3 Question 32 Discussion
Actual exam question for Databricks's Databricks-Certified-Data-Analyst-Associate exam
Question #: 32
Topic #: 3
Question #: 32
Topic #: 3
A data analyst has been asked to configure an alert for a query that returns the income in the accounts_receivable table for a date range. The date range is configurable using a Date query parameter.
The Alert does not work.
Which of the following describes why the Alert does not work?
The Alert does not work.
Which of the following describes why the Alert does not work?
Suggested Answer: D Vote an answer
The reason the alert is not functioning as expected is because Databricks SQL Alerts do not support query parameters. This limitation applies to all types of parameters, including date parameters.
Here's why:
Alerts require static, deterministic query results so they can compare values consistently during scheduled executions.
When a query includes parameters (e.g., a date range parameter), its results may change based on user input or the default value set in the query editor.
However, Databricks SQL Alerts will always use the default value set for the parameter at the time the alert is created. This means the alert doesn't dynamically adapt to new date ranges and will not reflect changes unless the query is manually updated.
As a result, if the business logic behind the alert depends on changing date ranges or any user input, the alert will not trigger correctly, or may never trigger at all.
Therefore, the correct explanation contradicts Option B, which is incorrect in saying that alerts cannot work with date-based queries at all. In fact, they can-as long as the query is static (i.e., without parameters).
Reference:
Databricks SQL Alerts Documentation
Databricks Knowledge: "You cannot use alerts with queries that contain parameters."
Here's why:
Alerts require static, deterministic query results so they can compare values consistently during scheduled executions.
When a query includes parameters (e.g., a date range parameter), its results may change based on user input or the default value set in the query editor.
However, Databricks SQL Alerts will always use the default value set for the parameter at the time the alert is created. This means the alert doesn't dynamically adapt to new date ranges and will not reflect changes unless the query is manually updated.
As a result, if the business logic behind the alert depends on changing date ranges or any user input, the alert will not trigger correctly, or may never trigger at all.
Therefore, the correct explanation contradicts Option B, which is incorrect in saying that alerts cannot work with date-based queries at all. In fact, they can-as long as the query is static (i.e., without parameters).
Reference:
Databricks SQL Alerts Documentation
Databricks Knowledge: "You cannot use alerts with queries that contain parameters."
by Philipppa at Jun 21, 2026, 12:49 PM
0
0
0
10
Comments
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).