Home / ML Associate practice test / Databricks Machine Learning / Question

Databricks Machine Learning Associate · free practice question

A recommender model needs customer and product features stored in Unity Catalog feature tables. The training dataset already contains customer_id, product_id…

Exam-style question on Databricks Machine Learning from the free ML Associate practice test, with the answer and a full explanation below.

Updated November 10, 2026

Databricks Machine Learning

A recommender model needs customer and product features stored in Unity Catalog feature tables. The training dataset already contains customer_id, product_id, and rating. Which sequence correctly uses Databricks Feature Engineering for model training?

  1. ARead both feature tables manually, join them with SQL, drop the lookup keys, and call mlflow.register_model before fitting to register the feature metadata for the training DataFrame
  2. BCreate an online store first, publish both feature tables, train directly against the online copies, and log the model with mlflow.sklearn.log_model once the real-time serving setup is in place
  3. CUse FeatureEngineeringClient.read_table on each feature table, write the rating labels into those tables, train on the combined table, and log the model with FeatureEngineeringClient.log_model
  4. DDefine FeatureLookup objects, call FeatureEngineeringClient.score_batch on the rating DataFrame to materialize the training set, train on that output, and log the model with mlflow.sklearn.log_model
  5. EDefine FeatureLookup objects, build a training set with FeatureEngineeringClient.create_training_set, load its DataFrame, train on that DataFrame, and log the model with FeatureEngineeringClient.log_model
Answer & explanation

Correct answer: E

WHY E: The documented training flow is FeatureLookup -> create_training_set -> load_df -> fit the model -> log it with FeatureEngineeringClient.log_model so feature metadata is preserved.

WHY NOT A: Manual SQL joins lose the built-in feature metadata workflow, and mlflow.register_model does not register feature lookups before fitting.

WHY NOT B: Offline training does not require online publishing; online stores are for real-time serving, and a plain MLflow flavor log drops the feature metadata.

WHY NOT C: Labels do not need to live inside the feature tables; they stay in the training DataFrame and are joined through the lookups.

WHY NOT D: score_batch is for inference with an already logged model, not for creating training data.

Take the full ML Associate practice test free →

Would you pass today?

This question is one of 45 in the free, timed Databricks Machine Learning Associate practice test. Take it and get a section-by-section score.

Start the free test →