Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
A financial services organization stores transaction audit files in a Cloud Storage bucket with Object Versioning enabled. The files are written under the prefix audit-logs/ and follow specific access patterns:
StudyCerts
StudyCertsaudit-logs/ prefix should be permanently removed 14 days after becoming noncurrent.Which Object Lifecycle Management (OLM) configuration meets these requirements with the least operational overhead?
Enable bucket-level Autoclass with a 365-day Bucket Lock retention policy, and schedule a daily Cloud Run job to identify and delete noncurrent object versions.
Configure Object Lifecycle Management rules to transition objects directly to Archive storage at age 30, and apply an IAM Deny policy on the bucket to prevent access to noncurrent versions older than 14 days.
Configure Object Lifecycle Management rules with prefix condition audit-logs/ to transition storage to Nearline at age 30, transition to Coldline at age 90, delete live objects at age 365, and delete noncurrent versions using daysSinceNoncurrentTime: 14.
Deploy a Cloud Function triggered by Cloud Storage Pub/Sub notifications on object creation that calculates retention timestamps and invokes the Cloud Storage API to rewrite storage classes and delete noncurrent versions.
Enable bucket-level Autoclass with a 365-day Bucket Lock retention policy, and schedule a daily Cloud Run job to identify and delete noncurrent object versions.
Configure Object Lifecycle Management rules to transition objects directly to Archive storage at age 30, and apply an IAM Deny policy on the bucket to prevent access to noncurrent versions older than 14 days.
Configure Object Lifecycle Management rules with prefix condition audit-logs/ to transition storage to Nearline at age 30, transition to Coldline at age 90, delete live objects at age 365, and delete noncurrent versions using daysSinceNoncurrentTime: 14.
Cloud Storage Object Lifecycle Management (OLM) allows administrators to define declarative rules consisting of actions (such as SetStorageClass and Delete) coupled with specific conditions (such as Age, MatchesPrefix, IsLive, and DaysSinceNoncurrentTime). Cloud Storage automatically inspects objects within the bucket and executes the configured actions asynchronously without requiring external compute infrastructure.
SetStorageClass with target Nearline at Age: 30 aligns with monthly access patterns.SetStorageClass with target Coldline at Age: 90 matches quarterly access requirements.MatchesPrefix: audit-logs/ condition ensures that only audit log objects are affected by these policies.Delete action with Age: 365 purges live logs after one year.DaysSinceNoncurrentTime: 14 (or IsLive: false with noncurrent age) ensures that superseded or deleted log versions are permanently removed 14 days after becoming noncurrent, preventing unbounded storage accumulation in version-enabled buckets.Native lifecycle policies execute directly within the storage control plane, providing predictable lifecycle transitions and deletions while strictly honoring prefix constraints and version states.
Deploy a Cloud Function triggered by Cloud Storage Pub/Sub notifications on object creation that calculates retention timestamps and invokes the Cloud Storage API to rewrite storage classes and delete noncurrent versions.