Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A financial services organization ingests large volumes of transaction audit records into Google Cloud Storage. The data lifecycle requirements and access patterns are defined as follows:
You need to design an automated, cost-optimized storage lifecycle strategy for the bucket.
Which configuration should you implement?
SetStorageClass action to transition objects to Archive at age 365 days and a Delete action at age 2,555 daysAutoclass is a Cloud Storage feature that automatically shifts an object's storage class between Standard, Nearline, Coldline, and Archive based on each individual object's observed access patterns over time.
Cloud Storage explicitly prohibits combining Autoclass with Object Lifecycle Management rules that use the SetStorageClass action or the matchesStorageClass condition. Attempting to apply a lifecycle configuration with SetStorageClass on an Autoclass-enabled bucket results in an immediate configuration error.
SetStorageClass.The workload had entirely unpredictable, erratic access patterns across millions of individual objects where access timelines could not be predetermined by rule.
Deploying a Cloud Run function scheduled via Cloud Scheduler involves writing custom code to scan bucket metadata, issue rewrite API calls to change storage classes, and send delete requests for expired records.
While functional, this approach introduces unnecessary architectural complexity, compute execution costs, API rate-limiting challenges, and maintenance overhead when native, free platform capabilities exist.
Transitions required complex, dynamic business logic based on external database state or third-party metadata that native Cloud Storage lifecycle conditions cannot evaluate.
Setting the default storage class to Archive means all newly uploaded objects immediately inherit the Archive tier upon creation.
The data was generated solely as a deep regulatory archive that would not be touched or queried immediately after ingest.
SetStorageClass to Coldline at age 30 days, SetStorageClass to Archive at age 365 days, and Delete at age 2,555 daysObject Lifecycle Management (OLM) in Google Cloud Storage allows you to define declarative rules that automatically manage the lifecycle of objects within a bucket. By defining condition-action pairs, Cloud Storage inspects objects and automatically executes operations like changing storage classes (SetStorageClass) or permanently removing data (Delete) without operational intervention.
Delete lifecycle rule automatically removes objects older than 2,555 days, ensuring compliance with data privacy mandates.
This solution matches each lifecycle phase to its most cost-effective storage class while avoiding early deletion or retrieval penalties. It delivers a fully managed, declarative solution directly within Cloud Storage.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated