A manufacturer trains its weld-defect model in the production project, using live line photos while inspectors still rely on the current model during the shift. How should the architect change that lifecycle?
Select an answer to reveal the explanation.
Short Explanation
You do not rewire the factory floor while the shift is still running the line. You train the weld model in a non-production project and promote only the approved version. Overwriting production from the newest photo makes the line the lab.
Full Explanation
Custom-model application lifecycle management keeps training off the deployment that workers already trust. The weld model should be trained in a non-production project, evaluated there, and promoted only after that version is approved, so the shift keeps the current model until the new one is ready. Training on the live line and overwriting production as each photo arrives changes the inspector's model in the middle of a shift and leaves no approved version to roll back to. Copying photos to a personal laptop removes the work from any shared lifecycle, and skipping promotion means the line's model is unchanged or updated by hand. Turning the model off until an outside paper reviews the photos stops the inspection the line depends on and is not a training environment. Exam caveat: promotion is not the same as copying the live photos onto a personal laptop and skipping the line. The approved version has to be the one the line calls. Operational check: confirm the training job runs in the non-production project, and confirm production still serves the previous version until someone records the promotion.