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: Active, current (live) objects must never be automatically deleted by lifecycle rules. To prevent storage sprawl, retain a maximum of 3 noncurrent versions; any older noncurrent version beyond the 3 newest must be permanently deleted immediately. Any noncurrent version that has been superseded for more than 90 days must be permanently deleted, even if fewer than 3 noncurrent versions exist. Which lifecycle configuration should the security engineer implement to satisfy these requirements?

Create two separate Delete action rules: Rule 1 with conditions `isLive: false` and `numNewerVersions: 3`; Rule 2 with conditions `isLive: false` and `daysSinceNoncurrentTime: 90`.: ### What This Lifecycle Configuration Is 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. ### How It Meets Each Requirement - **Protects live objects:** Both rules explicitly set `isLive: false`, ensuring that active/current versions of objects are completely exempt from automated lifecycle deletion actions. - **Limits noncurrent versions to 3:** Setting `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). - **Enforces the 90-day maximum age for noncurrent versions:** Setting `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. ### Key Advantages and Capabilities - **Disjunctive (OR) rule evaluation:** Cloud Storage evaluates multiple lifecycle rules independently. An object version meeting the criteria of *either* Rule 1 or Rule 2 is deleted, properly implementing the dual compliance criteria. - **Accurate time tracking:** The `daysSinceNoncurrentTime` condition tracks time elapsed since an object version was superseded or soft-deleted, rather than its initial creation date (`age`). - **Granular version control:** Pairing `isLive: false` with `numNewerVersions` avoids unintended data loss on live datasets while preventing version explosion during frequent object overwrites. ### Why This Is Optimal 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.

Cloud Storage Versioning Lifecycle Rules | Professional Cloud Security Engineer

Cloud Storage Versioning Lifecycle Rules

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:

Active, current (live) objects must never be automatically deleted by lifecycle rules.
To prevent storage sprawl, retain a maximum of 3 noncurrent versions; any older noncurrent version beyond the 3 newest must be permanently deleted immediately.
Any noncurrent version that has been superseded for more than 90 days must be permanently deleted, even if fewer than 3 noncurrent versions exist.

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 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.

Create a single Delete action rule with conditions numNewerVersions: 3 and age: 90 without specifying isLive.

Professional Cloud Security Engineer

Cloud Storage Versioning Lifecycle Rules

Related questions