引導式測驗 · 中等 等級

ML 工程師雲端技能測驗

在儲存、運算、容器、權限、部署、監控、可重複性和成本控制方面建立雲端機器學習基礎。

相關引導路徑ML 工程師雲端技能
問題 1 的 8

Which cloud concept controls what a service identity is allowed to access?

預覽每個問題8 問題

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

  1. Which cloud concept controls what a service identity is allowed to access?
    • Network route tables
    • Object-storage lifecycle rules
    • Identity and access management
    • Container registry settings
  2. Why package ML inference code in a container?
    • Standardize permissions across cloud accounts
    • Make runtime dependencies and environments more reproducible
    • Guarantee package versions never need security updates
    • Guarantee numerically identical training across CPU and GPU
  3. What does least privilege mean for a training or serving identity?
    • Give every service administrator access
    • Reuse a personal root credential
    • Disable all access logging
    • Grant only the permissions needed for its task
  4. Before a large training run, which action controls cloud cost?
    • Check current pricing and set budget controls where available
    • Assume every provider's free tier is identical
    • Leave temporary compute running indefinitely
    • Store duplicate artifacts in every region
  5. Which information supports reproducible retraining?
    • Cloud region alone
    • Run timestamp without code or data details
    • Code, data version, configuration and model artifact
    • Model name without configuration
  6. Which monitoring set is most relevant for an inference service?
    • Only training loss
    • Latency, errors, resource use and suitable input or output shifts
    • Container image tag alone
    • Build completion time alone
  7. How should teams treat cloud provider free tiers and prices?
    • Assume a tutorial's old prices still apply
    • Treat free tiers as unlimited
    • Ignore accelerator charges
    • Verify current official pricing for account, region and workload
  8. Which learning project best develops transferable cloud ML skills?
    • Build a small end-to-end project with guarded resources
    • Learn every service before writing a model
    • Start with a large distributed training run
    • Skip access policies until production