Plan and manage an Azure AI solution 1.2 Set up AI solutions in Foundry
A production app uses a Standard deployment of an Azure OpenAI model.
Study guide skill: Configure model and agent deployments
Question B3-002
A production app uses a Standard deployment of an Azure OpenAI model. The team wants to validate each new model version before adopting it, but if they miss the current version's retirement date, the deployment must keep working instead of failing. Which version upgrade option should the deployment use?
Select one answer.
Answer: B
OnceCurrentVersionExpired keeps the pinned version until its retirement date and then upgrades the deployment to the current default version, so nothing changes before the team validates it and the app doesn't break at retirement. OnceNewDefaultVersionAvailable upgrades soon after Microsoft designates a new default, before the team has validated it. NoAutoUpgrade never upgrades, so the deployment stops working at retirement, and provisioned deployments aren't auto-upgraded at all.
Deep dive
How it works
A Standard deployment pinned to a model version has a version upgrade option (versionUpgradeOption) that decides what happens as new versions arrive and the current one retires. There are three values:
- OnceNewDefaultVersionAvailable: when Microsoft designates a new default version, the deployment upgrades to it within two weeks.
- OnceCurrentVersionExpired: the deployment keeps its version until the retirement date, then upgrades automatically to the current default version.
- NoAutoUpgrade: the deployment never upgrades. At the retirement date it stops working, and you must point your code at a deployment that hasn't expired.
The team wants control first and safety second. OnceCurrentVersionExpired gives both: nothing changes while they test the new version, and if they miss the date, the deployment upgrades instead of failing. A null value means the same thing as OnceCurrentVersionExpired.
The working-with-models page describes the intended workflow for a specific version: test and validate that your app behaves consistently, then upgrade. Pair this with the retirement schedule, and upgrade manually once validation passes.
The other options, and when you'd use them
- Move to a provisioned deployment: Provisioned deployments are NOT auto-upgraded. You must migrate them manually, so this removes the safety net instead of adding one.
- OnceNewDefaultVersionAvailable: It upgrades within two weeks of a new default being designated, which can be before the team has validated that version.
- NoAutoUpgrade: The deployment never upgrades, and once the retirement date is reached it stops working.
Exam tip
"Validate first, but never break at retirement" = OnceCurrentVersionExpired. "Always newest" = OnceNewDefaultVersionAvailable. "Never" = NoAutoUpgrade, which stops at retirement.
References
Last reviewed: