Question

A data science team has registered several versions of a fraud-detection model to Unity Catalog. They want their batch scoring job to always load the currently approved production version without hardcoding a version number, and they want the ability to promote a newer version to production instantly by reassigning a pointer. Using Models in Unity Catalog, what is the recommended approach to reference the production model in the scoring code?

Accepted Answer

Assign a model alias (e.g., 'champion') to the approved version and load the model using the alias in the scoring code

Answer

Transition the model version to the 'Production' stage and load it using the stage name

Answer

Load the model version with the highest version number, since the latest version is always the production model

Answer

Copy the approved version's run ID into the scoring job configuration and update it manually after each promotion