Databricks-DE-Pro Debugging and Deploying Practice Question
A data engineer needs to ensure that a Databricks job can be retried automatically if it fails due to a transient cluster error. The job is configured with a maximum of 3 retries. After the third failure, the engineer wants to receive an email notification. Which feature should be used to accomplish this?
⚠ Common exam trap
The trap here is overlooking the native email notification feature and instead considering external alerting mechanisms that add unnecessary complexity.
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
✓
Configure the job's `email_notifications` with `on_failure` and set the email address.
Databricks jobs support built-in email notifications that can be triggered on failure. By configuring `email_notifications` with `on_failure`, the specified recipients receive an email after the job fails, including after all retries are exhausted. This is the most direct and native method. Other options require external services or are not designed for this purpose.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set up a Databricks SQL alert on the job's run history table.
Why it's wrong here
Databricks SQL alerts can monitor query results, but they are not designed for job failure notifications. While you could query the job run history via the Jobs API or system tables, setting up an alert would be indirect and more complex. The native `email_notifications` feature is simpler and purpose-built for this scenario.
- ✗
Configure the job to use a job cluster with autoscaling and set a retry policy.
Why it's wrong here
Autoscaling and retry policies affect job execution but do not send email notifications. A retry policy is already mentioned as configured, but it does not handle notifications. This option confuses cluster configuration with notification settings. The engineer needs a notification mechanism, not a cluster scaling feature.
- ✗
Use a webhook to call an external service that sends an email.
Why it's wrong here
Webhooks can notify external services, but they require additional setup and an external email service. The scenario asks for a built-in feature to receive an email notification, so using a webhook is overkill and not the simplest solution. Databricks provides native email notifications without external dependencies.
- ✓
Configure the job's `email_notifications` with `on_failure` and set the email address.
Why this is correct
The `email_notifications` setting in a Databricks job allows you to specify email addresses to notify on failure. When combined with retries, the notification is sent after all retries are exhausted (i.e., after the final failure). This is the standard way to alert on job failure. It requires no additional infrastructure and is built into the job configuration.
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.