Bài kiểm tra có liên kết hướng dẫn · Trung bình Cấp độ

Tối ưu hóa chi phí đám mây cho bài kiểm tra khối lượng công việc ML

Giảm chi tiêu cho đám mây ML thông qua việc phân quyền, lên lịch, tự động thay đổi quy mô, chính sách lưu trữ và đo lường theo từng tác vụ mà không làm giảm chất lượng.

Đường dẫn hướng dẫn liên quanTối ưu hóa chi phí đám mây cho ML
Câu hỏi 1 của 8

Why compare GPU choices using time-to-quality rather than hourly price alone?

Xem trước mọi câu hỏi8 câu hỏi

Câu trả lời và giải thích xuất hiện khi bạn làm bài kiểm tra.

  1. Why compare GPU choices using time-to-quality rather than hourly price alone?
    • Compute hours alone determine whether the model met the required quality
    • A higher hourly rate always means a higher completed-job cost
    • A faster, more expensive device may finish the useful job sooner
    • Training duration has no effect on compute charges
  2. What can still incur cost after a cloud VM is stopped?
    • Stopping a VM always bills GPU compute at the same running rate
    • Persistent disks, snapshots, or other attached resources
    • Deleting a VM automatically removes every attached snapshot
    • A terminated training process continues using GPU memory
  3. When can scaling to zero be a poor fit for an inference endpoint?
    • When requests are sparse and users can tolerate startup delay
    • When batch predictions can wait for capacity to start
    • When asynchronous jobs can be queued without interactive latency requirements
    • When startup delay conflicts with strict latency objectives
  4. Why tag resources by project and owner?
    • To attribute spend and find resources that outlive experiments
    • To apply automatic discounts to every untagged resource
    • To enforce a hard spending cap without budgets or permissions
    • To allocate GPU quota based only on a model label
  5. How should interruptible compute be evaluated for training?
    • Assume interruptions never affect training results
    • Use it for every online endpoint regardless of availability
    • Include checkpoints, restart overhead, and lost work in total cost
    • Ignore quality when restoring after an interruption
  6. Which outcome can make optimization based only on the bill risky?
    • A lower bill always means the model has improved
    • Model quality, latency, or reliability may fall below requirements
    • Optimization removes data-transfer charges automatically
    • The same model output is guaranteed after changing capacity
  7. Which inference cost metric is most actionable?
    • Only the GPU list price
    • Total model parameter count by itself
    • The number of resource tags
    • Cost per successful request under stated latency and availability goals
  8. What should be done before estimating cloud cost?
    • Check current region, resource configuration, and provider billing rules
    • Reuse a price from an old tutorial
    • Assume stopped compute means all attached resources are free
    • Ignore storage, networking, and data-transfer charges