Databricks-DE-Pro Monitoring and Alerting Practice Question
A data engineer has set up a Databricks SQL alert on a query that returns the count of failed jobs in the last hour. The alert is configured to trigger when the count exceeds 5. The engineer wants to receive notifications via email and also wants to view the alert history to understand past triggers. Which statement accurately describes the alert notification and history capabilities?
⚠ Common exam trap
The trap here is assuming that alerts only support email and that history is not readily available, when in fact Databricks provides multiple notification integrations and UI-based history.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Alerts can send notifications to email, Slack, and other destinations, and the alert history is available in the Databricks SQL UI.
Databricks SQL alerts are versatile: they can notify via email, Slack, PagerDuty, or webhooks, and they maintain a history of triggers that can be reviewed in the UI. This allows teams to audit past alert conditions and responses. The other options either limit notification channels or incorrectly describe history retention, making them inaccurate.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Alerts can only send notifications to email addresses and do not retain any history of triggers.
Why it's wrong here
Databricks SQL alerts support multiple notification destinations beyond email, including Slack, PagerDuty, and webhooks. Additionally, alert history is retained and can be viewed in the Databricks SQL UI. This statement incorrectly limits both notification channels and history retention, so it is not accurate.
- ✗
Alerts can only be configured to trigger once and then must be manually reset, and history is only available via the API.
Why it's wrong here
Alerts can be scheduled to run periodically and trigger each time the condition is met; they do not require manual reset. History is available in the UI, not exclusively via API. This statement misrepresents both the triggering behavior and the accessibility of alert history.
- ✗
Alerts can send notifications only to the alert owner's email, and history is stored for 7 days.
Why it's wrong here
Alerts can be configured to notify multiple recipients and external services, not just the owner. The retention period for alert history is not limited to 7 days; it is retained according to workspace settings. This statement incorrectly restricts notification recipients and misstates the history retention policy.
- ✓
Alerts can send notifications to email, Slack, and other destinations, and the alert history is available in the Databricks SQL UI.
Why this is correct
Databricks SQL alerts support email, Slack, PagerDuty, and webhook notifications. The alert history, including trigger times and query results, is accessible in the Databricks SQL UI under the alert's details. This statement correctly describes both the notification flexibility and the history feature, making it the accurate choice.
About these practice questions
This Databricks-DE-Pro question is part of Courseiva's 267-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-DE-Pro practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-DE-Pro exam.