A housing authority finished sandbox evaluation of a fine-tuned eligibility explainer and is ready for residents. What lifecycle step should GenAIOps take next?

Managing promotion of the evaluated fine-tuned model into the production Foundry deployment path is the correct next lifecycle step when a housing authority finished sandbox evaluation of an eligibility explainer and is ready for residents. Sandbox success must be followed by governed promotion into the production serving path so residents receive the evaluated checkpoint under operational controls. That is the GenAIOps handoff from experiment to service.

Managing promotion of the base foundation model into the production Foundry deployment path puts an unevaluated base model into service rather than the evaluated fine-tuned checkpoint, discarding the eligibility tuning that sandbox validation just approved and leaving residents without the correct explainer. Managing configuration of production application monitoring for the Foundry deployment of the model establishes observability for production but does not itself promote the evaluated checkpoint into the production serving path, so it cannot replace the promotion step that gives residents access. Managing archiving of the sandbox evaluation run in the Foundry project for release traceability preserves evaluation evidence for audit but does not move the evaluated checkpoint into production serving, so residents would still lack the validated explainer.

Exam caveat: promotion implies registration, gates, and a defined deployment path—not informal file copy. Foundry/production path language on the exam points to lifecycle promotion after sandbox eval, not monitoring configuration alone.

Operational check: register the sandbox-winning checkpoint, confirm evaluation artifacts are retained, promote through the production Foundry deployment path with canary traffic, and verify eligibility answers still match sandbox groundedness scores under production retrieval and policy settings.