AI-103 Practice Question 96: Draft Version Promotion
Microsoft Azure AI Apps and Agents Developer Associate (AI-103) · Test 10 · question 6 of 10
A team runs a Hosted agent in production; version 3 currently serves 100% of the endpoint's traffic. They want to test version 4, a new container image with an updated tool, through real interactive testing before any production traffic reaches it, without disrupting version 3's traffic and without advancing the release version number that client code or documentation might already reference.
How should they proceed?
Show answer and explanation
Answer:
A draft version is built for exactly this: "an experimental version that you can create and test without affecting how your agent serves production traffic." It's assigned a draft-{timestamp} identifier instead of an auto-incremented number, so "it never advances your release version numbering," and it's "excluded from implicit routing" and "can't be a traffic-routing target," so it can't leak into production by accident. Once satisfied, you "promote it by creating a new version with the same image and configuration but with draft omitted... The new version receives a regular auto-incremented version number and becomes eligible for traffic routing."
- A is wrong because traffic splitting between agent versions isn't supported; an endpoint's version selector must configure one FixedRatio rule at 100%, so a 50/50 split isn't a configuration the platform allows. - C is wrong because it works but adds unforced overhead: a new agent means a new identity, a new endpoint, and a client change, all to get isolation the built-in draft mechanism already provides without touching version 3. - D is wrong because it takes version 3 fully offline for the duration of testing, exactly the production disruption the team is trying to avoid.
Reference: Manage hosted agents