A digital marketing agency runs intermittent batch processing jobs to render promotional video clips for ad campaigns. Once rendered, the video files are accessed frequently during the first 30 days, but are rarely accessed after that point. The agency is required to retain these files for 3 years for contract compliance. The agency wants to minimize compute and storage costs while avoiding unnecessary operational management. Which TWO architectural decisions should the agency make to meet these requirements?
- Execute the intermittent batch rendering tasks using Cloud Run jobs.Cevap
- Configure an Object Lifecycle Management policy on Cloud Storage to transition video objects to Coldline Storage after 30 days.Cevap
- CProvision a dedicated, always-running Google Kubernetes Engine (GKE) cluster to handle the video rendering tasks.
- DStore the rendered video files as BLOB data inside Cloud Spanner for long-term archiving and compliance.
Cevap
The correct decisions are to execute batch rendering tasks using Cloud Run jobs and to configure Object Lifecycle Management on Cloud Storage to transition video objects to Coldline Storage after 30 days.
Executing intermittent processing using serverless Cloud Run jobs ensures compute costs are incurred only during active rendering runs. Implementing Object Lifecycle Management on Cloud Storage automates moving older video files to Coldline Storage, significantly cutting storage expenses for data accessed rarely after 30 days.
Adım Adım Çözüm
Anahtar Kavram
Serverless batch compute right-sizing combined with automated storage lifecycle management to minimize total cost of ownership.