A bank team edits a Microsoft Foundry agent directly in the production project. What should the architect require instead?
Select an answer to reveal the explanation.
Short Explanation
Tuning the engine while the bus is on the route is how a small tweak becomes a roadside stop. You promote the Foundry agent definition from a non-production project only after evaluation passes. A screenshot of the production edit is not a version you can evaluate.
Full Explanation
A Microsoft Foundry agent definition belongs in a non-production project until evaluation says it is fit to promote. Editing it in the production project makes production the workshop, so there is no evaluated build to roll forward or back. The architect requires the change in a non-production project, an evaluation of that definition, and a promotion of the definition that passed. Keeping the production edits and storing a screenshot records a picture, not a promotable definition. Copying the production agent into a document and retyping the next change makes a document the source of truth and still starts from the live project. Editing production during the day and skipping evaluation when the edit looks small keeps the live edit and drops the gate that would have caught it. Exam caveat: evaluation of the agent definition is not a substitute for monitoring after promotion. The gate decides what may be promoted, and production telemetry watches what was promoted. Operational check: confirm the production project has no direct edit since the last promotion, and that the running definition matches the build that passed evaluation.