Databricks-ML-Assoc ML Workflows Practice Question
An ML engineer registers a model in Unity Catalog and needs a stable pointer that always resolves to the version currently approved for production, without modifying calling code each time a new version is promoted. Which Model Registry feature should the engineer configure to provide this stable reference?
⚠ Common exam trap
The trap here is assuming that tags or descriptions can be used programmatically to select a version, when only aliases (or stages in older registries) act as resolvable pointers.
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
✓
A model version alias such as 'champion' assigned to the approved version
Model version aliases provide exactly the stable, reassignable pointer described: consumers load by alias, and promotion is performed by moving the alias to the newly approved version. Tags, descriptions, and permission grants are metadata or access controls and cannot redirect consumers to a chosen version at load time.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A model version tag recording the approval date
Why it's wrong here
Tags attach arbitrary key-value metadata to a model version for documentation and search, but they are descriptive labels only. They do not act as pointers that resolve to a version at load time, so changing a tag does not redirect consumers and cannot provide a stable production reference without code updates.
- ✗
A registered model description summarizing the production candidate
Why it's wrong here
The description field holds free-text documentation on a registered model and is useful for human readers browsing the registry. It is not machine-resolvable, so load and serving calls cannot use it to select a version, meaning it cannot serve as the stable pointer the engineer needs for production consumers.
- ✓
A model version alias such as 'champion' assigned to the approved version
Why this is correct
Aliases are named references that can be reassigned to any model version within a registered model. Serving code can target the alias instead of a version number, so promoting a newly approved version is a matter of moving the alias, and consumers automatically resolve to the newly approved version without any code change or redeployment of callers.
- ✗
A workspace-level permission grant on the registered model
Why it's wrong here
Permissions control which principals can read, execute, or manage the registered model and its versions. They govern access rather than version selection, so granting permissions does not create a stable reference that always resolves to the currently approved production version for downstream consumers.
Visual reference
About these practice questions
This Databricks-ML-Assoc question is part of Courseiva's 319-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.