A production registered model in Unity Catalog already has version 3 marked as Challenger after validation. Version 2 currently serves as Champion. The new version is approved for deployment, and the team wants downstream jobs that reference Champion to pick up the new version without changing their code. What should they do?
Answer & explanation
Correct answer: E
WHY E: Databricks recommends using aliases such as Champion and Challenger; reassigning Champion updates alias-based consumers without changing their model reference. WHY NOT A: Renaming the model is unnecessary and more disruptive. WHY NOT B: A second model is not required. WHY NOT C: The old version does not need to be deleted first. WHY NOT D: Experiments do not define deployment aliases.