Databricks-ML-Pro Model Development Practice Question
A data scientist is developing a scikit-learn model on Databricks and wants to log the model artifact to MLflow so that it can later be deployed for online inference. They call mlflow.sklearn.log_model() without providing a signature. What is the primary consequence of omitting the model signature?
⚠ Common exam trap
The trap here is assuming that a model signature is required for logging or that its absence prevents serving, when in fact it is optional metadata that affects schema validation and deployment robustness.
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
✓
The model will be logged, but MLflow cannot infer the input and output schema for deployment, potentially causing issues in serving or scoring.
Providing a signature when logging a model captures the expected input and output schema, which is essential for reliable deployment and scoring. Without it, MLflow cannot validate incoming data against the model's expectations, potentially leading to errors in serving or batch inference. The model still logs successfully, but the lack of schema metadata can cause integration problems.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
MLflow will not log the model at all because a signature is mandatory for scikit-learn models.
Why it's wrong here
MLflow does not require a signature to log a scikit-learn model. The log_model function will successfully store the model artifact even without a signature. The signature is optional metadata that describes input and output schema. Omitting it does not prevent logging; it only means the model lacks schema information, which can affect downstream validation and serving.
- ✗
The model will be logged, but MLflow Model Serving will reject requests because it cannot validate the input schema.
Why it's wrong here
MLflow Model Serving can still serve a model without a signature, although it may not perform strict input validation. The absence of a signature does not cause requests to be rejected outright. However, without a signature, the serving endpoint cannot enforce schema constraints, which may lead to runtime errors if inputs are malformed. This is a limitation but not an automatic rejection.
- ✓
The model will be logged, but MLflow cannot infer the input and output schema for deployment, potentially causing issues in serving or scoring.
Why this is correct
Without a signature, MLflow lacks a formal description of the model's expected input and output types. This can cause problems when deploying to Model Serving or when using the model in a batch scoring job that expects schema validation. The model artifact itself is still usable, but the missing schema may lead to integration issues or ambiguous behavior.
- ✗
MLflow will automatically generate a signature by inspecting the training data, so omitting it has no effect.
Why it's wrong here
MLflow does not automatically generate a signature from training data unless you explicitly call mlflow.models.infer_signature() and pass the result. The log_model function does not infer schema on its own. Therefore, omitting the signature means no schema is recorded, which can affect downstream deployment and validation.
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.