Valid Databricks-Certified-Professional-Data-Engineer Dumps shared by EduDump.com for Helping Passing Databricks-Certified-Professional-Data-Engineer Exam! EduDump.com now offer the newest Databricks-Certified-Professional-Data-Engineer exam dumps, the EduDump.com Databricks-Certified-Professional-Data-Engineer exam questions have been updated and answers have been corrected get the newest EduDump.com Databricks-Certified-Professional-Data-Engineer dumps with Test Engine here:
A data team is automating a daily multi-task ETL pipeline in Databricks. The pipeline includes a notebook for ingesting raw data, a Python wheel task for data transformation, and a SQL query to update aggregates. They want to trigger the pipeline programmatically and see previous runs in the GUI. They need to ensure tasks are retried on failure and stakeholders are notified by email if any task fails. Which two approaches will meet these requirements? (Choose 2 answers)
Correct Answer: B,C
Comprehensive and Detailed Explanation From Exact Extract of Databricks Data Engineer Documents: Databricks Jobs supports defining multi-task workflows that include notebooks, SQL statements, and Python wheel tasks. These can be configured with retry policies, dependency chains, and failure notifications. The correct practice, as stated in the documentation, is to use the Jobs REST API (/jobs/create) or Databricks Asset Bundles to define multi-task jobs, and then trigger them programmatically using /jobs/run-now, CLI, or SDK. This allows the team to maintain full job history, handle retries automatically, and receive alerts via configured email notifications. Using /jobs/runs/submit creates one-off ad hoc runs without maintaining dependency visibility. Therefore, options B and C together satisfy the operational, automation, and governance requirements.