AI-103 Practice Question 75: Provisioned Deployment Retirement
Microsoft Azure AI Apps and Agents Developer Associate (AI-103) · Test 8 · question 5 of 10
A team runs a customer-facing chatbot on a Global Provisioned (PTU) deployment of a specific GPT model version. Six weeks ago they received the model's retirement-date notice by email and in Azure Service Health, but the backlog got deprioritized and no one migrated the deployment. The retirement date has now passed.
What is the state of the chatbot's deployment today?
Show answer and explanation
Answer:
Microsoft's lifecycle policy is explicit that provisioned deployments are not auto-upgraded: "provisioned customers must manually migrate to the replacement model." That is precisely why active notification exists: a GA model's retirement notice goes out at least 60 days ahead so a provisioned customer has time to run an in-place or side-by-side migration before the cutover. Missing that window doesn't pause the clock; once retired, a model version returns error responses for every inference call, and retirement dates aren't extendable.
- A is wrong because automatic upgrade behavior (OnceNewDefaultVersionAvailable / OnceCurrentVersionExpired) applies to Standard deployment types, not Provisioned. The team cannot rely on Standard's safety net here. - B is wrong because spillover is a feature you configure in advance on a provisioned deployment to redirect traffic when PTUs are *saturated* by load; it isn't triggered by the model version itself being retired, and it requires the standard target to be named ahead of time. - C is wrong because Microsoft states plainly that retirement dates aren't extendable; missed notices don't earn a grace period.
Reference: Foundry Models lifecycle and support policy