Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An administrator manages a Google Cloud Storage bucket that has Object Versioning enabled. Due to frequent file updates, objects accumulate multiple noncurrent versions, which rapidly increases storage costs.
The administrator wants to automatically delete older noncurrent versions so that only the current live version and the two most recent noncurrent versions of each object are retained.
Which Object Lifecycle Management rule configuration should the administrator apply?
This configuration uses the SetStorageClass action to transition objects to Archive storage class when two days have elapsed since a user-defined date specified in the object's Custom-Time metadata field.
SetStorageClass merely alters the tier of stored data rather than removing it.DaysSinceCustomTime condition requires applications to explicitly set a custom timestamp on every uploaded object, creating administrative overhead.SetStorageClass helps lower at-rest storage costs by migrating data to colder tiers like Nearline, Coldline, or Archive.The organization wanted to archive older versions into long-term cold storage after a specific user-defined milestone date instead of permanently deleting them.
Object Lifecycle Management in Google Cloud Storage allows administrators to define automated rules that evaluate object metadata and perform actions like deletion or storage class downgrades. The NumNewerVersions condition evaluates the number of newer generations that exist for a given object, while the IsLive (or withState) condition filters between live (current) and noncurrent (archived) object versions.
IsLive: false parameter restricts the lifecycle rule to noncurrent versions only, guaranteeing that the active, current version is never accidentally targeted for deletion.NumNewerVersions to 2 ensures that an object version must have at least two newer versions in existence before the condition evaluates to true. As a result, the two most recently superseded noncurrent versions remain untouched.Delete action automatically.Combining NumNewerVersions with IsLive: false is the native, Google-recommended pattern for version pruning. It evaluates the relative generation count of objects rather than arbitrary calendar time, ensuring that active files always maintain exactly two historical backup copies regardless of how frequently or infrequently they are modified.
This configuration applies a Delete action based solely on the Age condition (measuring days since object creation) applied specifically to live objects (IsLive: true).
IsLive: true causes the active, current versions of files to be deleted after two days, which breaks ongoing access to current application data.Age condition evaluates elapsed time rather than the number of newer object versions, so it cannot ensure that exactly two historical versions remain preserved.IsLive: true, all superseded noncurrent versions are excluded from the rule, leaving historical storage accumulation unaddressed.Age is measured in integer days starting from the object's initial upload timestamp.IsLive: true targets only the single active version currently returned by default read operations.The goal was to implement a strict Time to Live (TTL) policy on temporary scratch files where live data should expire and transition out 48 hours after upload.
The AbortIncompleteMultipartUpload lifecycle action is designed to clean up leftover, uncommitted parts of failed or abandoned multipart upload operations.
AbortIncompleteMultipartUpload is paired with the Age condition (measuring how long a multipart upload has remained incomplete), not with version-based conditions like NumNewerVersions.AbortIncompleteMultipartUpload frees storage occupied exclusively by orphaned upload segments.The scenario involved cleaning up billing charges caused by large file uploads that failed to complete midway through transmission.
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