引導式測驗 · 中等 等級

金絲雀與影子部署測驗

比較金絲雀和影子版本、流量處理、監控、工作負載成本、隱私控制和安全部署準備。

相關引導路徑金絲雀與影子部署
問題 1 的 8

金絲雀部署的定義是什麼?

預覽每個問題8 問題

當您參加測驗時,就會出現答案和解釋。

  1. 金絲雀部署的定義是什麼?
    • 在監控的同時將一小部分即時流量路由到新版本
    • 立即將所有流量傳送至新版本
    • 僅在周末運行新版本
    • 無需任何監控即可部署
  2. 影子部署的關鍵特徵是什麼?
    • 它的響應服務於一半的用戶
    • 它接收鏡像流量,但其回應被丟棄,不會向使用者顯示
    • 僅在開發環境中執行
    • 它立即取代了生產模型
  3. What does a shadow deployment protect users from, and what can it still cost?
    • It uses no extra resources and cannot access user data
    • Its predictions are returned to every user
    • Candidate responses are withheld, but mirrored inference still consumes compute and needs side-effect controls
    • It guarantees the candidate has no production impact of any kind
  4. How does user-facing traffic differ between a canary and a shadow?
    • Both always send candidate output to every user
    • A shadow deployment never uses production inputs
    • A canary is only an offline test
    • A canary serves candidate responses to a defined live-traffic segment; a shadow typically does not
  5. What should a team define before starting a canary or shadow rollout?
    • Traffic rules, monitoring thresholds, rollout duration, and a rollback owner
    • A promise that the candidate will outperform production
    • A fixed traffic percentage that must never change
    • A requirement to expose every user to the candidate
  6. 金絲雀部署和影子部署如何相輔相成?
    • 它們是相同的東西,但名稱不同
    • Shadow 驗證即時流量的行為,無需用戶承擔風險;金絲雀驗證一小部分的真實用戶影響
    • 金絲雀丟棄回應,而影子為它們提供服務
    • 都不涉及生產流量
  7. What should an operator do before mirroring production requests to a shadow model?
    • Allow the shadow model to execute writes twice
    • Assume copied requests contain no sensitive data
    • Isolate side effects and protect the handling of copied request data
    • Disable all monitoring of the candidate
  8. What does a canary reveal that a shadow deployment does not directly measure?
    • Whether candidate inference consumes compute
    • How its predictions compare offline
    • Whether a model can load in the serving stack
    • How the candidate affects users who are actually served by it