Professional Cloud Security 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.
A security engineer is configuring lifecycle management for an enterprise Google Cloud Storage bucket containing regulatory audit records. Object Versioning is enabled on the bucket.
The organization mandates the following retention and cleanup requirements:
Which lifecycle configuration should the security engineer implement to satisfy these requirements?
Create two separate Delete action rules: Rule 1 with conditions isLive: true and numNewerVersions: 3; Rule 2 with conditions isLive: false and age: 90.
Create a single Delete action rule with conditions numNewerVersions: 3 and age: 90 without specifying isLive.
Create a single Delete action rule with conditions isLive: false, numNewerVersions: 3, and daysSinceNoncurrentTime: 90 combined in the rule.
Create two separate Delete action rules: Rule 1 with conditions isLive: false and numNewerVersions: 3; Rule 2 with conditions isLive: false and daysSinceNoncurrentTime: 90.
This configuration defines two independent Object Lifecycle Management rules executing the Delete action on noncurrent object versions based on specific versioning conditions in Google Cloud Storage.
StudyCerts
StudyCertsisLive: false, ensuring that active/current versions of objects are completely exempt from automated lifecycle deletion actions.numNewerVersions: 3 in Rule 1 instructs Cloud Storage to satisfy the rule condition whenever a noncurrent version is superseded by at least 3 newer versions (meaning versions 4, 5, and older are deleted, leaving the 3 most recent noncurrent versions).daysSinceNoncurrentTime: 90 in Rule 2 ensures any object version that has been noncurrent for over 90 days is purged, regardless of whether 3 newer versions exist.daysSinceNoncurrentTime condition tracks time elapsed since an object version was superseded or soft-deleted, rather than its initial creation date (age).isLive: false with numNewerVersions avoids unintended data loss on live datasets while preventing version explosion during frequent object overwrites.Defining two separate lifecycle rules allows the storage system to independently evaluate the noncurrent version count threshold and the maximum noncurrent time window. Combining these conditions within a single rule would mistakenly enforce a logical AND condition, failing to delete stale records or excess versions when only one condition was met.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Still curious? Scout, our AI tutor, can explain this concept further and answer your follow-up questions.