Question 22
Domain 4: Assembling and Deploying ApplicationsIn MLflow 3, what registry URI is used by default for model registry operations in Unity Catalog-enabled workflows?
Correct answer: B
Explanation
MLflow 3 uses the Unity Catalog registry for model registry operations when Unity Catalog is enabled, and the default registry URI for that workflow is "databricks-uc". This URI tells MLflow to route model registration and lookup to Databricks Unity Catalog instead of the workspace model registry.
Why each option is right or wrong
A. workspace-registry
`workspace-registry` implies a workspace-scoped registry, not the Unity Catalog default.
B. databricks-uc
MLflow 3 resolves model registry calls to the Unity Catalog-backed registry when the workspace is UC-enabled, and the registry URI that selects that backend is `databricks-uc`. In Databricks MLflow integration, setting or defaulting the registry URI to this value directs model registration, versioning, and lookup to Unity Catalog rather than the legacy workspace registry, which is the expected behavior in UC workflows.
C. unity://registry
`unity://registry` looks plausible as a URI pattern, but it is not the default MLflow registry URI.
D. mlflow-registry-v3
`mlflow-registry-v3` suggests a version-labeled endpoint name, not the standard Unity Catalog registry identifier.