Databricks-ML-Assoc Practice Test 3 — 10 Questions

Question 1

When a data scientist needs to share an MLflow experiment with a team member, what is the best practice for ensuring collaborative access within Databricks?

Accepted Answer

Granting appropriate permissions on the experiment within the MLflow UI.. Sharing experiments is done by managing permissions on the experiment object itself. In Databricks, you can grant specific permissions (e.g., CAN_VIEW, CAN_MANAGE) to individual users or groups. This allows for controlled collaboration where team members can see experiment results without necessarily having the ability to modify or delete them, adhering to the principle of least privilege while fostering efficient teamwork during the development process.

Answer

Exporting the experiment to a CSV file and emailing it.

Answer

Moving the experiment to a public folder in DBFS.

Answer

Giving everyone admin access to the workspace.

Question 2

An ML engineer wants to package a training project so it can be run reproducibly from a Databricks Job across environments, with its Python dependencies and entry point defined. Which MLflow capability should be used?

Accepted Answer

MLflow Projects, using an MLproject file to declare the entry point and environment.. MLflow Projects are the packaging mechanism for reproducible runs: the MLproject file specifies the entry point and the environment via a conda or pip specification, and executing the project records source and parameters in a run. Models capture artifacts, Tracking records results, and Recipes impose a specific template, so none of those define a reusable training entry point with dependencies for a Databricks Job.

Answer

MLflow Tracking, by logging parameters and metrics for each run.

Answer

MLflow Recipes, by defining a step-based pipeline with profiles.

Answer

MLflow Models, by saving the estimator with a signature.

Question 3

What is the primary technical limitation when deploying an MLflow model that has custom Python dependencies not included in the standard Databricks Runtime?

Accepted Answer

The serving container will fail due to missing runtime libraries.. When using custom libraries, the inference environment must be able to install and manage these dependencies. MLflow handles this by utilizing environment specifications (like Conda or pip requirements). If these dependencies are not explicitly defined or cannot be resolved at deployment time, the serving container will fail to start. This highlights the importance of properly managing the environment specification to ensure the target serving infrastructure has the necessary software components available.

Answer

The model will automatically install the missing libraries.

Answer

The model will be rejected by the registry.

Answer

The model cannot be used with MLflow.

Question 4

A data scientist is using Databricks AutoML to train a classification model on a dataset with a binary target. They want to understand which features contributed most to the model's predictions and need a human-readable summary. Which AutoML output should they examine?

Accepted Answer

The AutoML-generated notebook that includes a section on model interpretability with SHAP values.. AutoML generates a notebook for each trial that includes model interpretability using SHAP. This notebook contains summary plots and feature importance rankings that are human-readable and explain the model's predictions. Examining this notebook is the correct way to understand feature contributions.

Answer

The MLflow run's artifact directory, specifically the 'feature_importance.json' file.

Answer

The Databricks Feature Store UI, which shows feature lineage and importance scores.

Answer

The Model Registry's version description, which is automatically populated with feature importance by AutoML.

Question 5

A machine learning engineer needs to track hyperparameter tuning runs and log artifacts using MLflow inside a Databricks Notebook. Which approach should be used to ensure runs are automatically nested under a parent run?

Accepted Answer

Utilize mlflow.start_run(nested=True) inside the hyperparameter optimization loop while a parent run is active.. Using `mlflow.start_run()` with a `nested=True` parameter ensures that child runs are correctly organized beneath an active parent run within the MLflow tracking server. This hierarchical structuring is essential for organizing complex hyperparameter optimization sweeps, enabling data scientists to easily compare child performance metrics against the overarching parent experiment trial in the Databricks UI.

Answer

Call mlflow.start_run() inside a loop without any arguments while an active run exists.

Answer

Set the MLFLOW_PARENT_RUN_ID environment variable manually before invoking mlflow.start_run().

Answer

Configure the MLflow client to use a hierarchical tracking URI scheme before logging parameters.

Question 6

Which of the following is a primary benefit of using a model serving endpoint versus a batch inference job?

Accepted Answer

Real-time, low-latency inference. Model serving endpoints provide low-latency, real-time responses to individual requests via REST APIs. This is essential for applications like fraud detection or recommendation engines, where an immediate prediction is required for a user interaction. Batch inference jobs, conversely, are designed for high-throughput, asynchronous processing of large datasets at scheduled intervals. Understanding these use cases is vital for selecting the correct deployment architecture to meet performance and latency requirements.

Answer

Lower cost for infrequent predictions

Answer

Ability to process billions of rows at once

Answer

Simplified tracking of data lineage

Question 7

What is the primary role of the 'Model Signature' in a Databricks ML lifecycle?

Accepted Answer

To enforce input schema validation at serving time.. The Model Signature defines the schema of the inputs and outputs, serving as a formal contract. This contract is used by the serving infrastructure to validate incoming requests, ensuring that they match the expected format. It helps catch errors early in the deployment lifecycle, protecting production endpoints from malformed data. By providing this metadata, developers ensure that their model is compatible with the standard Databricks serving interfaces, enabling seamless integration into production applications.

Answer

To identify which user trained the model for audit logs.

Answer

To increase the prediction accuracy by normalizing inputs.

Answer

To compress the serialized model file size for faster loading.

Question 8

A data scientist registers a model in the Databricks Model Registry and wants to record the model's intended input and output schema so that a serving endpoint can validate incoming requests. Which action accomplishes this when logging the model?

Accepted Answer

Log the model with an inferred or explicit signature using MLflow. A model signature is part of the logged MLflow model artifact and is what the serving runtime uses to validate request payloads against expected input and output types. Registry stages, endpoint tags, and external documentation are metadata that the runtime does not interpret as a schema, so only logging the model with a signature achieves request validation.

Answer

Add the schema to the endpoint's tags in the serving configuration

Answer

Store the schema as a separate Delta table and reference it in the model's README

Answer

Set the model version's stage to Production in the Model Registry

Question 9

When using MLflow to manage the lifecycle of a model in Databricks, why should you use the Model Registry instead of just saving model files to DBFS?

Accepted Answer

It allows for versioning and stage management of models.. The Model Registry provides versioning, stage transitions (e.g., Staging to Production), and centralized access control, which are essential for governed model deployment. Directly saving to DBFS ignores these enterprise features, making it impossible to track lineage or manage model lifecycle status effectively. Using the Registry creates an audit trail and standardizes the deployment workflow, which is critical for compliance and ensuring that only validated models move into production environments.

Answer

It automatically compresses the model files to save storage space.

Answer

It allows models to be trained directly on the registry.

Answer

It converts models into a proprietary format for faster inference.

Question 10

Which approach is most efficient for handling high-cardinality categorical features in a machine learning model while maintaining compatibility with standard Databricks model serving?

Accepted Answer

Using the Feature Store to store pre-computed embeddings.. Using Feature Store to pre-compute and transform high-cardinality features allows you to store them as embeddings or encoded vectors. This shift moves the expensive computation from the inference phase to an offline batch process, significantly reducing latency. This approach is compatible with standard model serving, as the model only receives the pre-calculated features, ensuring consistent and performant real-time inference within the Databricks ecosystem.

Answer

One-hot encoding the features inside the model inference function.

Answer

Converting features to strings and letting the model handle them natively.

Answer

Running a Spark job on every prediction request to re-encode the features.