引導式測驗 · 中等 等級
選擇正確的模型尺寸測驗
使用特定於任務的品質、延遲、成本、安全性和版本檢查來選擇模型,而不是假設一種模型大小適合每個請求。
問題 1 的 8
How should a team select a model tier for a production task?
預覽每個問題8 問題
當您參加測驗時,就會出現答案和解釋。
- How should a team select a model tier for a production task?
- Evaluate candidate models against the task’s quality, latency, cost, and safety requirements
- Always choose the largest model
- Always choose the cheapest model
- Use model size as the only metric
- Why can a smaller model be a good choice for a simple task?
- It is guaranteed to outperform larger models
- It never makes errors
- It may meet the needed quality with lower cost or latency
- It removes the need for evaluation
- How can a team compare candidate models fairly?
- 僅比較行銷描述
- Use representative held-out examples and measure quality, errors, latency, and cost
- 運行一個提示一次
- Compare parameter names only
- What risk applies to routing based on model confidence?
- Confidence always equals correctness probability
- Routing removes all errors
- Confidence prevents model updates
- Confidence may not be calibrated, so escalation thresholds need testing
- What information should a production team record about a chosen model?
- Exact model identifier or version and the evaluation date
- Only the display name
- Only the API hostname
- 部署後什麼都沒有
- When might a request be escalated to a more capable model?
- Whenever it has fewer than ten words
- When the model is cheaper
- Only after every request is already complete
- When it meets tested criteria for complexity or uncertainty
- What should be monitored after changing model versions?
- Only token count
- Only the deployment timestamp
- Task quality, error types, latency, cost, and failures
- Only model name length
- Does a larger model automatically perform better for every request?
- Yes, for every task
- No; task fit and evaluation results determine whether added capability helps
- Yes, if its context window is longer
- No, because larger models cannot follow instructions