Most candidates need 7 to 9 weeks of part-time study to prepare for the Databricks Certified Machine Learning Professional exam, roughly 55 to 70 hours. Engineers already running production ML on Databricks often need 4 to 5 weeks. Without Machine Learning Associate-level knowledge, budget 12 to 14 weeks.
Last updated November 2026.
The Professional exam is 59 scored questions in 120 minutes against 47 objectives, and Databricks recommends one year of hands-on experience, double the Associate's six months. The gap is not volume, it is the kind of knowledge. Most objectives describe something you only meet once a model is in production: a monitor that has to be configured, a test that has to run in the right environment, a rollout that has to shift traffic safely.
Reading about those is slow to stick. The estimates below assume you will build at least part of a pipeline while you study.
Question count, time limit and the one-year recommendation are from the Databricks Machine Learning Professional certification page and the exam guide PDF linked from it (30 Sep 2025 edition). The week and hour estimates are ours.
These assume 7 to 8 hours a week. If you are in the third group, the ML Associate study plan is the honest first step, and the Associate vs Professional comparison explains why.
This guide publishes official section weights, so the split is not guesswork.
| Section | Official weight | Of a 60-hour plan |
|---|---|---|
| 1. Model Development | 44% | About 26 hours |
| 2. MLOps | 44% | About 26 hours |
| 3. Model Deployment | 12% | About 8 hours |
Two warnings sit inside that table. First, half of the MLOps section's 20 objectives are about drift detection and monitoring, the area fewest candidates have touched in real work. Second, Model Deployment looks small, but 12% of 59 questions is about seven questions over only five objectives, so each objective there is worth more than anywhere else on the exam.
Compress or stretch: already running production ML? Fold Weeks 1 to 3 into one week of review and keep the monitoring weeks whole. Short on platform time? Add a week after Week 3 to build a small end-to-end pipeline in a workspace before starting MLOps.
Monitoring is ten objectives. If you have set up a data profiling monitor (formerly Lakehouse Monitoring) and read its drift metrics table, Weeks 5 and 6 shrink to one. If you have not, they are the weeks least safe to cut.
The lifecycle and testing objectives assume pull requests, staging tests and release branches. Candidates who work that way daily find Week 4 mostly a matter of vocabulary; notebook-only teams should give it the full week, starting with deploy code vs deploy models.
There is no published passing score to aim at. We use 70% on timed unit exams as a target and 85% on full mocks as the bar for booking, both our guidance rather than an official threshold.
Most candidates need 7 to 9 weeks of part-time study, roughly 55 to 70 hours. Engineers already running production ML on Databricks often need 4 to 5 weeks, and those without Associate-level knowledge should budget 12 to 14 weeks.
Plan for 55 to 70 hours in the typical case, at 7 to 8 hours a week. Split them by the official weights: about 44% on Model Development, 44% on MLOps and 12% on Model Deployment.
It is harder than the Associate because the questions are production scenarios with several workable options. Databricks recommends one year of hands-on experience, and the monitoring, testing and deployment objectives are difficult to learn from reading alone.
Start with Section 1, Model Development, because the later sections build on it. Then give MLOps the most protected time, since half of its 20 objectives cover drift detection and monitoring.
Yes. There is no prerequisite, so the Associate is not required. Candidates who skip it should still be comfortable with its material first: AutoML, MLflow tracking, feature tables and basic model serving.
Fifty-two short chapters in the same order as this plan, a unit exam after each of the six units, then three full-length mocks. Every unit is free to open.
Start Chapter 1 →