Google Cloud Professional Cloud Architect · Free practice question 7 of 12
Autoclass for unpredictable object access
Kirkby Studios stores 900 TB of production assets in Cloud Storage. Some objects are read heavily for weeks and then never again, while others are reopened unpredictably years later. The deciding constraint is lower storage cost without writing or maintaining lifecycle rules. What should the architect recommend?
- A.Set every object to Archive storage class at upload
- B.Lifecycle rules that move every object to Coldline after 30 days and to Archive after one year
- C.Autoclass on the bucket, moving objects between classes based on access
- D.Use a multi-region bucket in Standard storage class for everything
Show answer and explanation
Correct answer: C. Autoclass on the bucket, moving objects between classes based on access
Why: Autoclass automatically transitions each object to colder classes when it is not accessed and back to Standard when it is read, which suits unpredictable access without lifecycle rules to maintain. Uploading everything as Archive penalizes the heavily read assets with retrieval costs. Lifecycle rules contradict the constraint, and keeping all data in Standard does not reduce cost.
More free Google Cloud Professional Cloud Architect questions
- Config Sync GitOps across a cluster fleet
- Chirp speech model for call transcription
- AlloyDB read pools for read scaling
- VM Manager OS patch management
- BigQuery long-term storage pricing
- Feature Store against training-serving skew
- Workflows orchestrating serverless steps
- Managed Service for Apache Airflow for complex DAGs
- Cloud DNS failover routing policy
- Datastream change data capture into BigQuery
- Cloud Asset Inventory IAM policy analysis