A bank compares a champion model with a challenger on a frozen batch of past applications before any promotion. After release, it compares those models on live application decisions. Which statement names the two checks?
Select an answer to reveal the explanation.
Short Explanation
A dress rehearsal on a saved tape is not opening night. You call the frozen-batch comparison offline validation and the live-decision comparison online validation. The trap is labeling every champion-versus-challenger check as online.
Full Explanation
Offline validation scores models on a frozen set before promotion, so the champion-versus-challenger comparison on past applications is offline. That batch does not change while it is scored. Online validation watches live decisions after release, so the comparison on current applications is online and cannot start until the models are deciding real applications. Calling both checks online treats a frozen batch as live traffic and erases the distinction the bank's two stages were built to keep. A second copy of the application store would be replication, and adding scoring copies would be orchestration, neither of which names a validation stage. Packaging training code off a notebook is isolation of the job, and restarting a failed scoring copy is an operations response, not the name of the live comparison. Exam caveat: online validation still needs a limit on how much traffic a weak challenger can take while it is being watched. Operational check: confirm the pre-promotion report used only the frozen batch and the post-release report is computed on live decisions.