Continuous Training and Automated Retraining Quiz

Answers and explanations appear as you take the quiz.

1. What distinguishes continuous training from automatic deployment?
   • Training can create and evaluate a candidate without promoting it
   • Every training run must replace production
   • Deployment occurs before any evaluation
   • Continuous training avoids new data
2. What should happen after a drift alert triggers retraining?
   • Publish the candidate immediately
   • Check data quality and schema before treating it as a model trigger
   • Assume every alert indicates real concept drift
   • Delete the previous model
3. Which operational benefit can a scheduled retraining cadence provide?
   • It guarantees the candidate is better
   • It always uses the newest labels immediately
   • It gives a predictable cadence and compute budget
   • It eliminates data validation
4. Why should a candidate be compared with the deployed model?
   • To make data lineage unnecessary
   • To avoid choosing metrics
   • To guarantee subgroup performance
   • To detect regressions relative to the current production baseline
5. What should block promotion if a critical subgroup regresses despite aggregate improvement?
   • An automatic release based only on the aggregate score
   • A predeclared subgroup gate or required review
   • A deletion of the subgroup from reporting
   • A replacement of the test set
6. Which lineage records help reproduce a trained candidate?
   • Only the GPU serial number
   • Only the model's public name
   • Data snapshot, source revision, dependencies and parameters
   • A screenshot of the final metric
7. Why retain the prior model after promoting a candidate?
   • It guarantees identical predictions
   • It makes the candidate more accurate
   • It removes the need for monitoring
   • It enables a rollback if live behavior degrades
8. What should a pipeline do if a required data or evaluation gate fails?
   • Stop promotion and retain diagnosable failure evidence
   • Publish the candidate but hide the report
   • Skip the failed check on every later run
   • Replace the baseline automatically