Databricks-ML-Assoc Model Deployment Practice Question
A machine learning engineer is deploying a model to a Databricks Model Serving endpoint and needs to send feature values that are computed by a separate upstream pipeline. The engineer wants the endpoint to accept a JSON payload describing a single record with named fields. Which approach correctly describes how the client should format the request?
⚠ Common exam trap
The trap here is assuming any JSON structure works, when the endpoint expects the specific dataframe_records or dataframe_split format for DataFrame-signature models.
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
✓
Send a JSON body with a dataframe_records or dataframe_split field containing the named columns matching the model signature.
For models logged with a pandas DataFrame signature, Databricks Model Serving accepts JSON using dataframe_records or dataframe_split, where each record is an object of column names to values. This preserves the named-column contract and allows signature validation. Positional array formats and non-JSON encodings do not match the DataFrame interface and would either fail validation or misalign features.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Send a JSON body containing a base64-encoded serialized pandas DataFrame along with a pickle content type.
Why it's wrong here
Serialized or pickled payloads are not part of the Model Serving request contract and introduce security and compatibility concerns. The endpoint expects plain JSON that it converts to the model's expected input type. Base64-encoded pickles would not be recognized and would cause the request to fail validation before scoring.
- ✗
Send the record as form-encoded key-value pairs in the request body with a content type of application/x-www-form-urlencoded.
Why it's wrong here
Model Serving expects JSON payloads, not form-encoded bodies. Sending urlencoded data would not be parsed into the expected DataFrame structure, and the endpoint would reject or misinterpret the request. The documented interface is JSON with either dataframe or tensor formatting depending on the model signature.
- ✓
Send a JSON body with a dataframe_records or dataframe_split field containing the named columns matching the model signature.
Why this is correct
Databricks Model Serving accepts pandas DataFrame inputs in JSON using the dataframe_records or dataframe_split format, where each record maps column names to values. This aligns with the signature logged for a scikit-learn or similar model and lets the endpoint validate and score the record without custom parsing.
- ✗
Send a JSON body with an inputs field containing a nested array of numeric values in the exact column order of training.
Why it's wrong here
The inputs field with positional arrays is the tensor-oriented format used for frameworks expecting arrays, not for pandas DataFrame signatures with named columns. For a model logged with named columns, positional arrays lose the column-name mapping and may fail signature validation or produce incorrect feature alignment.
About these practice questions
Courseiva writes every Databricks-ML-Assoc question from scratch — 319 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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-Assoc 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-Assoc exam.