Databricks-ML-Pro Model Development Practice Question
When evaluating a classification model on Databricks, a team needs to generate a custom performance report that is not natively provided by MLflow. What is the recommended strategy to ensure this report is persisted and associated with the training run?
⚠ Common exam trap
Candidates often try to use direct print statements or UI screenshot functions, forgetting that custom programmatic reports must be saved as local files first before being uploaded via log_artifact.
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
✓
Save the report to a local temporary file and use MLflow.log_artifact to upload it to the run.
Logging custom plots and reports as artifacts is the recommended way to enrich MLflow run metadata. By saving visualizations or summary statistics as files (e.g., HTML, PNG, or JSON) and using 'log_artifact', the team ensures that non-standard evaluation metrics are permanently stored. This practice allows stakeholders to review specific model performance indicators without needing to re-run the training code, which is vital for compliance and post-training analysis.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Print the report to the notebook output and rely on the notebook's command history.
Why it's wrong here
Notebook command history is volatile and not intended for permanent artifact storage. It cannot be easily integrated into downstream CI/CD pipelines or shared with non-technical stakeholders in a formalized report structure. Using the MLflow artifact store ensures reports are versioned and tied to the specific model training run.
- ✓
Save the report to a local temporary file and use MLflow.log_artifact to upload it to the run.
Why this is correct
The 'log_artifact' method is the standard way to attach any file, including custom reports, images, or plots, to an MLflow run. This provides a robust and centralized way to keep evaluation results alongside the model, enabling comprehensive documentation of the model lifecycle directly within the Databricks MLflow tracking environment.
- ✗
Store the report in an external database and manually link it via a comment in the run.
Why it's wrong here
This approach breaks the association between the model and its artifacts. It introduces complexity in retrieval and auditing, as the external link may become broken or unreachable. Maintaining all relevant experiment data within the MLflow ecosystem is crucial for ensuring the reproducibility and auditability of the machine learning pipeline.
- ✗
Re-generate the report every time the model is loaded for inference.
Why it's wrong here
Re-generating reports during inference is inefficient and can introduce latency in production environments. Evaluation reports should be generated at training time and stored as metadata. Inference services should focus on performance and reliability, not on the computational overhead of re-calculating performance metrics for every prediction request made by users.
About these practice questions
Courseiva writes every Databricks-ML-Pro question from scratch — 300 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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-ML-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-ML-Pro exam.