A utility is ready to release a Microsoft Foundry agent to production, and the release path has no evaluation gate. What should the architect add?
Select an answer to reveal the explanation.
Short Explanation
You do not find out the valve sticks by opening it on the live main. You add an evaluation gate that must pass before this Foundry agent is released to production. A week of live traffic is an outage report, not a gate.
Full Explanation
A Foundry agent release without an evaluation gate ships whatever was last edited. The architect adds a gate that runs the agent against agreed cases and blocks production until those cases pass. Agree those cases with the utility before the gate is wired, and store the pass or fail with the build identifier, because a date on a calendar does not record a result. Releasing on the calendar date and reviewing a sample the following week moves the check to after customers are already on the path. Skipping the gate because a senior engineer edited the agent in the production project trusts a person and a live edit instead of a result, and it also edits in the wrong project. Publishing to production and treating the first week of live traffic as the evaluation uses real utility transactions as the test suite. Exam caveat: the gate checks the build you intend to promote. A passing run on an older definition does not clear a newer edit. Operational check: point the release at a definition that fails a known case and confirm production does not update, then point it at a definition that passes and confirm that is the one production receives.