Data Engineer Professional · Domain 4: Monitoring and Alerting · 10% of the exam
Task 4.4: Use Databricks Lakehouse alerts to monitor governed business metrics, data quality and anomaly signals, usage and cost, SQL warehouse/query health, audit and security events, AI agent quality, and Lakeflow Job branching.
Databricks SQL alerts, their conditions and schedules, notifications, alert tasks in jobs, and alerts over system tables and data quality results.
Try each one before opening the answer. Every option is explained, with the Databricks documentation page that proves it.
Question 1 · choose 1
A Databricks SQL alert checks for negative inventory every hour on its own schedule. The data team also needs it evaluated right after the nightly load job finishes, which happens at a different time each night, with the result sent to the load team. The hourly schedule must keep running. What should they do?
AChange the alert's schedule to a cron time after the usual end of the load, notifying the load team
BAdd a SQL task that runs the alert's query after the load task
CAdd a SQL alert task that points to a legacy alert copied from it
DAdd a SQL alert task after the load task, with the load team as subscribers
Show the answer and why
AChange the alert's schedule to a cron time after the usual end of the load, notifying the load team
Incorrect
The load ends at a different time each night, and this replaces the hourly schedule.
BAdd a SQL task that runs the alert's query after the load task
Incorrect
A SQL task runs the query but does not evaluate the alert condition or send the alert's notifications.
CAdd a SQL alert task that points to a legacy alert copied from it
Incorrect
SQL alert tasks support only Databricks SQL alerts, not legacy alerts.
DAdd a SQL alert task after the load task, with the load team as subscribers
Correct
The task evaluates the alert independently of its schedule and notifies the subscribers configured on the task.
A SQL alert task runs the alert's query on a pro or serverless warehouse, evaluates its condition and notifies the task's subscribers. It evaluates the alert independently of any schedule on the alert, which is not affected by the job run.
A job's SQL alert task evaluates an alert whose condition is met. What status does the task report?
AFailed, because the alert condition was met
BSucceeded, because the alert was evaluated
CSkipped, because notifications were sent
DSucceeded with failures
Show the answer and why
AFailed, because the alert condition was met
Incorrect
Failed is reported for evaluation errors such as query failures.
BSucceeded, because the alert was evaluated
Correct
The task reports Succeeded when evaluation works, whether or not the condition triggered.
CSkipped, because notifications were sent
Incorrect
Notification delivery does not skip the task.
DSucceeded with failures
Incorrect
That status describes job runs where some tasks failed.
A SQL alert task reports Succeeded when the alert was evaluated, regardless of the condition, and Failed when evaluation hit an error, such as a warehouse connectivity issue or a query error.