SnowPro Advanced: MLOps Engineer free question 5 / 10 · Domain 3: Model Serving and Deployment Operations
A model uses the alias scheme: v1 has the alias production and v2 has the alias beta. Production code calls MODEL(my_model, production)!predict. v2 has passed its checks. Which statements match the promotion shown in the docs?
- UNSET ALIAS on v1 and on v2, then SET ALIAS = production on v2
- ALTER MODEL my_model SET TAG live_version = 'v2'; and nothing else
- ALTER MODEL my_model VERSION v2 SET ALIAS = production; on its own
- ALTER MODEL my_model VERSION v1 UNSET ALIAS; then drop version v1
Show the answer and explanation
Answer: A
Why this is correct
The section "Promoting subsequent versions of the model" under "Using aliases" says that when a new version has passed muster, you remove the production alias from the current production version and apply it to the new version. Its SQL runs ALTER MODEL my_model VERSION v1 UNSET ALIAS, then VERSION v2 UNSET ALIAS to clear beta, then VERSION v2 SET ALIAS = production. The Model Registry overview explains why the order matters: a given alias can be assigned to only one model version at a time. Production code that calls MODEL(my_model, production) then runs v2 without being edited.
Why the other options are wrong
"ALTER MODEL my_model VERSION v2 SET ALIAS = production; on its own" … A given alias can be assigned to only one model version at a time, and v1 still holds production. The page removes it from v1, and clears the beta alias from v2, before setting it on v2.
"ALTER MODEL my_model SET TAG live_version = 'v2'; and nothing else" … A live_version tag belongs to the tag scheme, where production code reads the tag with SYSTEM$GET_TAG before calling the version. This code calls the model through the production alias, so a tag would not change what it runs.
"ALTER MODEL my_model VERSION v1 UNSET ALIAS; then drop version v1" … Unsetting the alias on v1 is the first step, but dropping v1 does not move production to v2; the alias would point at no version and the production call would have nothing to run. The page also keeps old versions so that a rollback stays possible.
Move the label, not the code
Aliases let you name every stage, such as alpha, beta and production, and promote by moving labels. Script the three statements together so that the gap between unsetting and setting the production alias is as short as possible, and so the same script can move it back if v2 misbehaves.