Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise stores millions of compliance audit logs and supporting evidence artifacts in a Cloud Storage bucket initialized with the Standard storage class. The data architecture team establishes the following data retention and cost optimization requirements:
SetStorageClass would exceed any monthly storage cost savings.Which Object Lifecycle Management configuration should the security engineer deploy on the bucket?
This approach uses a lifecycle Delete rule to purge Standard objects at 365 days while relying on an event-driven Cloud Function executing Cloud Storage rewrite API calls (objects.rewrite / storage.objects.copy) to migrate objects to Coldline.
Delete actions remove live object generations or convert them to noncurrent versions if Object Versioning is enabled.The business objective was absolute data destruction after 365 days with no ongoing retention or cold archival requirement.
Object Lifecycle Management (OLM) in Google Cloud Storage automates object transition and deletion policies. The SetStorageClass lifecycle action alters the storage tier of an object asynchronously without rewriting data bytes or triggering data movement pipelines.
age condition to 365 and matchesStorageClass to STANDARD ensures that only active objects that have resided in Standard storage for a full year transition to the COLDLINE tier.sizeAboveBytes: 5242880 (5 MiB) filters out small index files and thumbnails. Because executing SetStorageClass is billed as a Class A operation against the destination class, small objects can incur transition API charges that dwarf ongoing capacity savings.SetStorageClass do not rewrite the underlying object data. Consequently, they incur zero retrieval fees and zero inter-region network charges.age, matchesStorageClass, and sizeAboveBytes within a single rule condition block.This declarative lifecycle approach eliminates manual batch scripts, avoids unneeded operation expenses on small files, and safeguards against unexpected egress and retrieval billing.
The daysSinceNoncurrentTime condition evaluates the elapsed time since an object version was superseded and transitioned from live status to a noncurrent (historical) state within an Object Versioning-enabled bucket.
daysSinceNoncurrentTime condition.The goal was to archive historical, superseded versions of objects into Coldline storage 365 days after they were replaced by newer versions.
The sizeBelowBytes condition restricts lifecycle actions exclusively to objects whose data payload is smaller than the specified byte threshold.
sizeBelowBytes: 5242880 transitions only files smaller than 5 MiB into Coldline storage, while leaving files larger than 5 MiB in the expensive Standard class.The workload requirement demanded moving lightweight summary objects into lower-cost classes while preserving large raw data blobs in high-performance 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 Validated