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.
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?
numNewerVersions: 3 and age: 90 without specifying isLive.This configuration creates a single lifecycle deletion rule with numNewerVersions: 3 and age: 90, omitting the isLive condition.
numNewerVersions: 3 and age: 90 in one rule requires both conditions to be met before deletion occurs, failing to prune excess versions prior to day 90 or delete single old noncurrent versions.age parameter tracks days since initial upload, which does not reflect the 90-day window following supersession.numNewerVersions: 3 can only be satisfied by noncurrent versions in practice, omitting isLive: false creates ambiguity in policy auditing and fails to explicitly define protections for live data.The bucket did not use Object Versioning and only needed simple object deletion based purely on total object creation age.
Explicitly specifying isLive: false is a cloud security best practice for version management rules to prevent accidental configuration errors from impacting current production objects.
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.
isLive: 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.
isLive: true and numNewerVersions: 3; Rule 2 with conditions isLive: false and age: 90.This option sets up two deletion rules using a combination of isLive: true with numNewerVersions: 3, and isLive: false with the standard age: 90 condition.
isLive: true with numNewerVersions: 3 will never match any object.age condition measures time elapsed since an object version was initially created (written to the bucket), not the time since it became noncurrent (daysSinceNoncurrentTime).age: 90 combined with isLive: false would delete the older version immediately today rather than retaining it for 90 days after becoming noncurrent.numNewerVersions is only meaningful when applied to noncurrent object versions (isLive: false).age does not reset when an object is overwritten or superseded by a newer generation.The retention mandate measured the total elapsed lifetime from initial creation date rather than supersession date, and isLive: false was properly paired with numNewerVersions.
When managing versioned buckets, daysSinceNoncurrentTime and noncurrentTime are the appropriate lifecycle conditions to evaluate the lifecycle state of superseded generations.
isLive: false, numNewerVersions: 3, and daysSinceNoncurrentTime: 90 combined in the rule.This option places all three conditions (isLive: false, numNewerVersions: 3, and daysSinceNoncurrentTime: 90) into a single Object Lifecycle Management rule with a Delete action.
numNewerVersions: 3 but fail daysSinceNoncurrentTime: 90, meaning excess versions would not be deleted until 90 days have elapsed.The organization required that an object version must both have at least 3 newer versions and have been noncurrent for at least 90 days before becoming eligible for deletion.
To implement logical OR behavior across multiple conditions (such as deleting when version count exceeds a limit OR when elapsed noncurrent time exceeds a limit), administrators must define separate lifecycle rules.
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