引導式測驗 · 中等 等級
模型回滾與回退策略測驗
區分回滾到先前模型與回退到替代行為,並確定相容性和觸發要求。
問題 1 的 8
How does rollback differ from fallback?
預覽每個問題8 問題
當您參加測驗時,就會出現答案和解釋。
- How does rollback differ from fallback?
- Rollback restores a prior release; fallback uses an alternate behavior
- Rollback changes model outputs while fallback restores Git
- They are identical strategies in all systems
- Fallback always retrains the model
- Which signal can trigger an operational rollback?
- A model's training accuracy only
- A sustained increase in serving errors or timeouts
- A color change in a dashboard
- An unreviewed comment in source code
- Why retain an immutable previous artifact?
- It contains every request log
- It guarantees no future data drift
- It identifies the known-good bytes to restore
- It replaces health monitoring
- What can prevent an old model from working after a rollback?
- A signed artifact digest
- A lower training loss in the candidate
- An alert dashboard
- An incompatible feature or data schema change
- Why test fallback behavior independently?
- Fallbacks cannot affect user decisions
- A fallback can have its own failure modes and safety tradeoffs
- A simpler model is always safer
- Testing would disable rollback
- Why use a measurement window and hysteresis for automated rollback?
- To hide real errors
- To delay every response indefinitely
- To reduce reactions to transient noise and repeated switching
- To guarantee the model passes evaluation
- What can rollback not reverse automatically?
- A model version reference
- Future traffic routing
- The artifact selected by the deployment controller
- Irreversible side effects already caused by prior predictions
- What should a release runbook include?
- Triggers, owner, recovery steps and fallback limitations
- Only the model's parameter count
- A guarantee of zero user impact
- The training set's class names