Databricks Certified Machine Learning Associate Flashcards¶
76 cards from this guide's fact sheet and notes. Click a question to reveal the answer.
To study with spaced repetition, download flashcards.csv and import it into Anki or Quizlet (comma separated, first row is the header). Back to the study guide.
Exam logistics¶
How long is the Databricks Certified Machine Learning Associate exam?
90 minutes
How many questions are on the Databricks Certified Machine Learning Associate exam?
48 scored multiple-choice and multiple-selection (up to 10 more unscored)
What is the passing score for Databricks Certified Machine Learning Associate?
Not published by Databricks
What does the Databricks Certified Machine Learning Associate exam cost?
$200 USD plus applicable taxes (stated by Databricks, checked 2026-11-07)
How is the Databricks Certified Machine Learning Associate exam delivered?
Online proctored or test center
How long is Databricks Certified Machine Learning Associate valid for?
2 years
Databricks machine learning¶
ML runtime (databricks machine learning)
a Databricks Runtime variant that comes with machine learning and deep learning libraries pre-installed and tested together, so a team does not build the environment itself.
Dedicated access mode (databricks machine learning)
the cluster access mode that is set automatically when you pick the machine learning runtime, and that Unity Catalog data access from ML compute requires.
AutoML (databricks machine learning)
a Databricks capability that prepares data, trains and tunes models across several algorithms, picks the best, and generates editable notebooks for the trials.
Trial notebook (databricks machine learning)
the generated source code for a single AutoML trial, which you can review, reproduce and modify.
Feature table (databricks machine learning)
a Delta table with a primary key (and optionally a time series column) that stores computed features for reuse in training and inference.
FeatureEngineeringClient (databricks machine learning)
the Python client in databricks.feature_engineering used to create, write, read and tag feature tables and to build training sets.
FeatureLookup (databricks machine learning)
the object that tells a training set which table, which features and which lookup key to join in.
Offline feature table (databricks machine learning)
the governed Delta table used for training and batch scoring, queried in bulk.
Online feature store (databricks machine learning)
a low-latency store holding the latest feature values so a real-time endpoint can look features up by key.
MLflow run (databricks machine learning)
one execution of model training code, which records parameters, metrics, tags and artifacts.
MLflow experiment (databricks machine learning)
a named group of related runs that you can compare and filter.
search_runs (databricks machine learning)
the MLflow client call that queries runs, with order_by such as metrics.rmse ASC, and returns them (as a pandas DataFrame from mlflow.search_runs).
Autologging (databricks machine learning)
MLflow's automatic capture of parameters, metrics and the model for supported libraries, the easiest way to start tracking.
Unity Catalog model registry (databricks machine learning)
the registry that stores models as three-level named, versioned Unity Catalog objects with centralized access control, auditing, lineage and cross-workspace discovery.
Model alias (databricks machine learning)
a mutable, named reference (such as champion) to one version of a registered model, set with set_registered_model_alias.
Model tag (databricks machine learning)
a key-value label on a registered model or model version, set with set_model_version_tag and removed with delete_model_version_tag.
Champion and challenger (databricks machine learning)
the convention of giving the serving version the champion alias and the candidate the challenger alias, and promoting by moving champion to the winner.
Promote code versus promote models (databricks machine learning)
the two promotion strategies; code promotion is the usual recommendation, and model promotion fits cases where retraining in production is not possible.
Data processing¶
summary() (data processing)
a Spark DataFrame method that returns count, mean, stddev, min, quartiles and max for the columns it is called on, or the statistics you ask for.
dbutils.data.summarize (data processing)
the Databricks notebook utility that displays summary statistics and charts for a Spark or pandas DataFrame, with approximate results unless precise=True.
Standard deviation rule (data processing)
an outlier rule that removes values more than a chosen number of standard deviations from the mean; it assumes roughly normal data and is distorted by the outliers it seeks.
IQR rule (data processing)
an outlier rule that removes values below Q1 minus 1.5 times the IQR or above Q3 plus 1.5 times the IQR; it is based on percentiles and is robust to skew.
Mean imputation (data processing)
filling missing numeric values with the column mean; suited to symmetric distributions and sensitive to outliers.
Median imputation (data processing)
filling missing numeric values with the column median; preferred for skewed data or data with outliers.
Mode imputation (data processing)
filling missing values with the most frequent value; the standard choice for categorical features.
One-hot encoding (data processing)
turning a categorical feature into one binary column per category, so a numeric model does not read a false order into the values.
StringIndexer (data processing)
a Spark ML estimator that maps string labels to numeric indices (most frequent label first by default).
OneHotEncoder (data processing)
a Spark ML estimator that turns category indices into binary vectors, usually applied after StringIndexer.
Log transformation (data processing)
applying a logarithm to a right-skewed, strictly positive variable to compress large values and make its distribution closer to symmetric.
log1p (data processing)
the natural log of one plus the value, a common way to log-transform data that contains zeros.
Model development¶
Cost-sensitive learning (model development)
give the minority class a higher misclassification weight (class_weight in scikit-learn, a weight column in Spark ML). This is the direct answer to "mitigate the bias toward the majority" in the guide's sample question.
Resampling (model development)
oversample the minority class (including synthetic samples such as SMOTE) or undersample the majority.
Better metrics and thresholds (model development)
judge by precision, recall, F1 or area under the precision-recall curve, and move the threshold.
Stratified splits (model development)
keep the class ratio in every training and validation split.
Class imbalance (model development)
a training set where one class is far more common than another, so a model can score high accuracy while missing the minority class.
Stratified split (model development)
a train/validation split that preserves the class proportions in every part.
Transformer (model development)
a Spark ML component with a transform() method that turns one DataFrame into another, usually by adding columns.
Estimator (model development)
a Spark ML component with a fit() method that learns from a DataFrame and returns a Model, which is a Transformer.
Pipeline (model development)
an ordered chain of transformers and estimators that is itself an estimator; fitting it returns a PipelineModel.
Hyperopt (model development)
a Python library for hyperparameter search; fmin minimizes an objective over a search space (not maintained upstream, and not in Databricks Runtime ML after 16.4 LTS ML).
fmin (model development)
the Hyperopt function that runs a search, taking an objective function, a search space, an algorithm, max_evals and a trials object.
SparkTrials (model development)
the Hyperopt trials class that runs single-machine model trials in parallel as Spark tasks; do not use it with distributed algorithms such as MLlib.
Random search (model development)
tuning by sampling hyperparameter combinations at random from the allowed ranges.
Bayesian search (model development)
tuning that uses the results of earlier trials to choose the next hyperparameters, as TPE does.
Cross-validation (model development)
estimating performance by training k times, each time validating on a different fold, and averaging the scores.
Train-validation split (model development)
estimating performance from one split of the data; cheaper than cross-validation but noisier on small data.
ParamGridBuilder (model development)
the Spark ML utility that builds the grid of hyperparameter combinations (a list of param maps) for a tuner.
Accuracy (model development)
share of correct predictions. Misleading on imbalanced data (above: 0.901 with recall 0.25).
Precision (model development)
of the rows predicted positive, how many are positive. Recall: of the actual positives, how many were found.
F1 (model development)
scikit-learn describes the F-measure as "a weighted harmonic mean of the precision and recall"; F1 weights them equally and is best at 1 and worst at 0. Use it when both false positives and false negatives matter and the classes are imbalanced.
ROC AUC (model development)
area under the ROC curve, which plots true positive rate against false positive rate across all thresholds. It measures ranking quality independent of any threshold: 0.5 is chance, 1.0 is perfect.
Log loss (model development)
scikit-learn: "also called logistic regression loss or cross-entropy loss, is defined on probability estimates". It punishes confident wrong predictions heavily, so it is the metric when you care about calibrated probabilities. Lower is better.
R-squared (model development)
the share of variance in the target the model explains; unit-free, 1 is perfect. scikit-learn notes R-squared gives the same ranking as squared error.
Exponentiate (model development)
apply the inverse of a log transform (exp) so predictions and metrics are in original units.
Bias (model development)
error from a model that is too simple, which shows as high error on training and validation data (underfitting).
Variance (model development)
error from a model that is too sensitive to the training data, which shows as low training error and high validation error (overfitting).
Regularization (model development)
a penalty that constrains model complexity to reduce overfitting.
Model deployment¶
Batch inference (model deployment)
scoring a whole dataset on a schedule and storing the predictions, which is the simplest and cheapest pattern when no per-request latency is required.
Real-time inference (model deployment)
scoring individual requests through a low-latency REST endpoint such as a Model Serving endpoint.
Streaming inference (model deployment)
scoring records continuously as they arrive in a streaming pipeline.
mlflow.pyfunc.load_model (model deployment)
the MLflow call that loads any logged model as a generic Python function with a predict method.
mlflow.pyfunc.spark_udf (model deployment)
the MLflow call that wraps a logged model as a Spark UDF so it can score a Spark DataFrame on a cluster, in batch or streaming.
Delta Live Tables (model deployment)
the Databricks declarative pipeline framework (now Lakeflow Spark Declarative Pipelines) for managed batch and streaming data pipelines, including model inference through a Spark UDF.
Structured Streaming (model deployment)
Spark's streaming engine, which scores arriving records with the same DataFrame operations and UDFs as batch.
Served entity (model deployment)
the model (a Unity Catalog model name and version) that a Model Serving endpoint serves, with its compute settings.
Scale to zero (model deployment)
an endpoint setting that releases compute when idle; not recommended for production because capacity is not guaranteed and the first request is slow.
dataframe_split (model deployment)
the recommended JSON input format for tabular models, a pandas DataFrame in split orientation with columns and data.
ai_query (model deployment)
a Databricks SQL function that calls a Model Serving endpoint from a query, used for batch scoring and in pipelines.
traffic_config (model deployment)
the endpoint setting that lists routes, each pairing a served model name with a traffic percentage.
Traffic split (model deployment)
sending a chosen share of requests to each model behind one endpoint, used for A/B tests and gradual rollouts.