quiz bu lëkkale ak tegtal · Diggante Niveau

Rollback ak pexe Fallback

Wuutale dellusi ci xeetu njëkk ak daanu ci beneen jeffin, te ràññee deggoo ak li ñuy laaj ci trigger.

Yooni njiit yu jëm ciModel Rollback Ak Pexe Fallback
Laaj 1 de 8

How does rollback differ from fallback?

Xoolaatal laaj bu nekk8 laaj

Sooy def quiz bi, tontu yi ak leeral yi dañuy feeñ.

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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