professional-cloud-data-engineer
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 ingests millions of analytical audit files daily into a Google Cloud Storage Standard bucket. Strict compliance regulations mandate that audit files must be retained immutably for exactly 7 years (2,555 days), preventing any user—including bucket and project administrators—from deleting or modifying them before the retention period expires.
To optimize storage costs, the team identified the following operational requirements:
Which combination of Cloud Storage configurations satisfies all compliance and cost-optimization requirements?
Apply an unlocked bucket retention policy of 2,555 days. Define an Object Lifecycle Management rule with the SetStorageClass action set to COLDLINE with conditions age: 30 and sizeBelowBytes: 10485760, and configure an external cron job on Cloud Run to delete expired objects.
Configure an Object Hold on all incoming objects. Apply an Object Lifecycle Management rule with the SetStorageClass action set to COLDLINE with conditions age: 30 and matchesStorageClass: STANDARD, and configure an Organization Policy constraint to enforce bucket deletion after 2,555 days.
Enable Object Versioning on the bucket. Configure an Object Lifecycle Management rule with the SetStorageClass action set to COLDLINE at age: 30, and a second rule with the Delete action and daysSinceNoncurrentTime: 2555.
Configure a bucket retention policy of 2,555 days and lock it using Bucket Lock. Define an Object Lifecycle Management rule with the SetStorageClass action set to COLDLINE with conditions age: 30, matchesStorageClass: STANDARD, and sizeAboveBytes: 10485760, and a second rule with the Delete action and condition age: 2555.
Apply an unlocked bucket retention policy of 2,555 days. Define an Object Lifecycle Management rule with the SetStorageClass action set to COLDLINE with conditions age: 30 and sizeBelowBytes: 10485760, and configure an external cron job on Cloud Run to delete expired objects.
Configure an Object Hold on all incoming objects. Apply an Object Lifecycle Management rule with the SetStorageClass action set to COLDLINE with conditions age: 30 and matchesStorageClass: STANDARD, and configure an Organization Policy constraint to enforce bucket deletion after 2,555 days.
Enable Object Versioning on the bucket. Configure an Object Lifecycle Management rule with the SetStorageClass action set to COLDLINE at age: 30, and a second rule with the Delete action and daysSinceNoncurrentTime: 2555.
Configure a bucket retention policy of 2,555 days and lock it using Bucket Lock. Define an Object Lifecycle Management rule with the SetStorageClass action set to COLDLINE with conditions age: 30, matchesStorageClass: STANDARD, and sizeAboveBytes: 10485760, and a second rule with the Delete action and condition age: 2555.
This configuration pairs Cloud Storage Bucket Lock with Object Lifecycle Management (OLM) to enforce regulatory compliance (WORM - Write Once, Read Many) while automating storage class transitions and end-of-life object deletion.
StudyCerts
StudyCertsSetStorageClass to COLDLINE executes once an object reaches age: 30 in the STANDARD storage class. Adding sizeAboveBytes: 10485760 (10 MiB) ensures that smaller objects are not transitioned, preventing Class A operation charges from outweighing the cost savings of the Coldline class.Delete action and age: 2555 automatically purges objects once their retention requirement is satisfied, without requiring manual administrative intervention.SetStorageClass do not rewrite data, so object age continues accumulating uninterrupted towards the retention and deletion threshold.This architecture directly satisfies compliance and financial constraints by leveraging native, fully managed storage governance controls without custom automation scripts or external scheduling services.