Databricks-ML-Pro Model Development Practice Question
A machine learning team is using `mlflow.autolog()` to track experiments. They notice that certain custom metrics are not being captured. What is the most effective way to address this?
⚠ Common exam trap
Candidates mistakenly believe that enabling `mlflow.autolog()` is sufficient to capture all domain-specific or custom business KPIs without writing explicit logging statements.
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
✓
Implement a custom callback in the training loop that uses mlflow.log_metric for the specific metrics.
While autologging captures standard metrics like accuracy, custom metrics require explicit logging calls using `mlflow.log_metric`. This is important because business-specific KPIs, such as profit margin or specific domain-based error rates, often require custom logic that framework-specific autologgers cannot infer automatically. Explicit logging ensures comprehensive experiment visibility and allows for precise model selection based on business goals rather than just technical performance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Disable autologging and manually log every single parameter and metric.
Why it's wrong here
Disabling autologging is inefficient and eliminates the benefit of automatic tracking of standard training metadata. A hybrid approach, where autologging captures standard performance metrics and manual logging handles custom KPIs, is the industry standard for maintaining both operational efficiency and business-specific requirement tracking in ML experiments.
- ✓
Implement a custom callback in the training loop that uses mlflow.log_metric for the specific metrics.
Why this is correct
Using standard MLflow logging functions within a training loop allows for the integration of domain-specific metrics alongside the automatically logged framework metrics. This approach provides maximum flexibility, ensuring that all necessary data for model evaluation is captured in a single, unified experiment run record for analysis.
- ✗
Increase the logging frequency of the autologger via the configuration file.
Why it's wrong here
Increasing the logging frequency of an autologger only captures more frequent updates of standard metrics; it does not add the capability to calculate or log custom metrics that the library is not designed to compute automatically. Custom metrics must be defined and logged programmatically by the user.
- ✗
Create a custom Python class that inherits from the MLflow Autologger base class.
Why it's wrong here
Creating a custom autologger class is an overly complex and unsupported way to capture custom metrics. MLflow is designed to be extensible via standard API calls within the training code, and extending the internal autologger architecture is prone to breaking as the MLflow library updates over time.
About these practice questions
One of 300 original Databricks-ML-Pro practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.