1.16: Promote a challenger model to a champion model using aliases
1.The `champion` alias on `ml.prod.churn` was just moved from version 5 to version 7, but the Mosaic AI Model Serving endpoint for the model still answers with version 5 behavior. The endpoint's served entity was configured with an explicit version number. Which TWO actions make the endpoint serve the new champion? (Select all that apply.)(Select 2)
- A.Resolve the version with `get_model_version_by_alias("ml.prod.churn", "champion")` and update the endpoint's served entity to that `entity_version`
- B.Add the endpoint-update step to the promotion job right after the alias assignment, so serving follows `champion` each time it is moved
- C.Wait for the alias change to propagate, because serving endpoints re-read alias assignments automatically once a day without any update
- D.Rename the registered model so the endpoint must re-resolve its served entity from the three-level Unity Catalog name on the next request
- E.Call `transition_model_version_stage` on version 7 with the Production stage, which causes the endpoint to switch its served version
Show answer & explanation
Correct answers: A, B — Resolve the version with `get_model_version_by_alias("ml.prod.churn", "champion")` and update the endpoint's served entity to that `entity_version`; Add the endpoint-update step to the promotion job right after the alias assignment, so serving follows `champion` each time it is moved
- A. Correct. The endpoint serves the version recorded in its configuration, so the promotion process looks up the version behind the alias and updates the served entity accordingly.
- B. Correct. Chaining the endpoint update directly after the alias change keeps serving and the alias in step, so a promotion does not leave the endpoint on the old version.
- C. Incorrect. A served entity pinned to a version number does not follow later alias moves on a timer, so waiting never changes what the endpoint serves.
- D. Incorrect. Renaming a registered model breaks references and downstream consumers, and does not make an endpoint with a pinned version adopt the champion.
- E. Incorrect. Unity Catalog models do not support stages, so there is no stage transition to call, and it would not alter the endpoint's configured version anyway.