A team's Foundry-hosted assistant has run on a specific model version for a year. Microsoft announces that version will be retired in three months, with a newer version available in the catalog. Before switching, what should the team do?
Select an answer to reveal the explanation.
Short Explanation
When a model version you depend on is scheduled to be retired, the smart move is not to wait it out or panic-rebuild, it is to stand the replacement up next to what you already have and run your usual test questions through both, side by side, so you can see exactly where the new one behaves differently before anyone's real conversations depend on it. Waiting until the old version is actually gone just turns this into a fire drill with no time to catch problems. Tearing down the working deployment and starting over throws away a known-good setup and still skips the comparison step that actually matters. And turning up a capacity setting like throughput has nothing to do with how long a model version stays available, so that will not buy any extra time at all.
Full Explanation
The correct answer is D. Deploying the new model version alongside the existing one and running the team's established evaluation set against both lets them compare quality, safety, and behavior differences before any production traffic depends on the new version, catching regressions while the old version is still available as a fallback. Option A is incorrect because waiting until the old version is actually removed forces an unplanned, reactive cutover with no chance to compare behavior beforehand, risking an outage or a quality drop discovered only after users are already affected. Option B is incorrect because deleting the current deployment and rebuilding from scratch discards a working, tested configuration and skips any side-by-side comparison, so problems in the new version would only surface after the old one is already gone. Option C is incorrect because provisioned throughput controls capacity and latency guarantees for a deployment; it has no bearing on a model version's retirement timeline, so increasing it does nothing to delay the deprecation deadline Microsoft has already announced.