Databricks-ML-Pro ML Ops Practice Question
A machine learning engineer is using MLflow Tracking to log metrics and artifacts for a deep learning model. They notice that the training run logs a large number of metrics (e.g., loss per batch) and want to reduce the storage footprint and improve query performance. They also need to retain the ability to compare runs and reproduce results. Which of the following actions is most appropriate?
⚠ Common exam trap
The trap here is assuming that any reduction in logged metrics requires abandoning MLflow tracking, when in fact you can simply log less frequently using the step parameter.
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
✓
Log only the final epoch metrics and use MLflow's step parameter to log intermediate metrics less frequently.
MLflow's log_metric function can accept a step parameter to record metrics over time, but logging every batch creates a large number of entries. Reducing the logging frequency or only logging final epoch metrics significantly decreases storage and improves query speed while still providing enough data for comparison and reproducibility. Other options either lose MLflow's tracking capabilities or introduce unsupported configurations.
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 metric logging entirely and rely on TensorBoard for visualization.
Why it's wrong here
Disabling metric logging in MLflow means you lose the ability to compare runs within the MLflow UI and to programmatically query metrics. TensorBoard provides visualization but does not integrate with MLflow's tracking store for run comparison. This approach sacrifices reproducibility and the centralized tracking benefits that MLflow offers, making it a poor choice for the requirement.
- ✓
Log only the final epoch metrics and use MLflow's step parameter to log intermediate metrics less frequently.
Why this is correct
Logging metrics with the step parameter allows you to record a time series, but logging every batch can create a huge number of metric entries. By logging only final epoch metrics or reducing frequency, you decrease storage and speed up queries. MLflow still stores the history if needed, but the volume is manageable. This balances reproducibility with efficiency.
- ✗
Use a different tracking server with a NoSQL backend to handle the high volume of metrics.
Why it's wrong here
Changing the backend to NoSQL might handle volume, but MLflow's tracking server officially supports SQL-based backends like MySQL, PostgreSQL, or SQLite. NoSQL backends are not natively supported and would require custom implementation. Moreover, this does not address the root cause of excessive metric logging; it merely shifts the storage burden and adds complexity without solving query performance.
- ✗
Store metrics in a separate file and log it as an artifact instead of using mlflow.log_metric.
Why it's wrong here
Logging metrics as an artifact file bypasses MLflow's metric tracking system. While it reduces the number of metric entries in the backend store, you lose the ability to filter, sort, and compare runs based on metrics in the MLflow UI. Artifacts are not indexed for querying, so this defeats the purpose of efficient run comparison and analysis.
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.