A project lead turning a proof of concept into a governed service is told that connecting governance tooling to the development environment is unnecessary once the model is in production. Why is that advice wrong?
Select an answer to reveal the explanation.
Short Explanation
Models don't stop being developed just because a version shipped. Retraining and updates keep happening, and governance needs to see that evidence even after production release.
Full Explanation
The correct answer is the ongoing development work option: retraining, tuning, or building a new version typically continues after initial release, and disconnecting governance from that environment means those changes go unrecorded. The claim that development environments cannot technically be connected to governance tooling once a model is in production is incorrect because there's no technical barrier preventing a development environment from staying connected after production release. The claim that production deployments never receive updates once released is incorrect because production models are commonly retrained or updated, contrary to that premise. The claim that governance tooling can only monitor one environment at a time is incorrect because governance tooling is designed to connect to multiple environments concurrently. For the exam, keep the development connection live for the model's whole life, not just before its first release.