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 configures an Object Lifecycle Management policy on a Cloud Storage bucket with a rule set to delete all log files once their age exceeds 30 days.
Shortly after an object reaches 31 days of age, an engineer notices that the file is still listed in the bucket and remains downloadable.
What explains this behavior, and how does Cloud Storage handle lifecycle policy actions?
Object Versioning is a Cloud Storage feature that maintains multiple historical variants of an object whenever it is overwritten or deleted, creating live and noncurrent object generations.
age condition and a Delete action simply purges the live object directly once executed.numNewerVersions, isLive: false, or daysSinceNoncurrentTime depend on versioning.Delete and SetStorageClass operate across all standard bucket configurations.The lifecycle policy specifically relied on conditions such as numNewerVersions or daysSinceNoncurrentTime, which are only satisfied when versioning creates noncurrent generations.
Basic lifecycle policies (such as deleting files older than a specified number of days) are commonly used on non-versioned buckets for ephemeral log storage and temporary data pipelines.
This option suggests that Object Lifecycle Management acts merely as a template or dry-run definition that requires scheduled external invocation through the Google Cloud CLI (gcloud storage) or API calls.
The scenario involved a custom script running on Compute Engine or Cloud Run using the gcloud storage rm command on a scheduled Cloud Scheduler trigger rather than native bucket lifecycle management.
A common misconception is assuming Cloud Storage operates like an external batch script. In reality, native lifecycle management is fully automated once enabled on the target bucket.
Some archival or enterprise content management systems move flagged records into a visible quarantine partition or pending-purge holding area for administrative review before permanent deletion occurs.
The bucket had a custom legal hold or retention policy configuration requiring manual administrative approval queues prior to object disposition.
Do not confuse operational processing lag (which is a matter of hours during asynchronous background scans) with structured retention policies or quarantine holds.
Object Lifecycle Management in Google Cloud Storage provides automated background evaluation of bucket contents against defined condition rules, such as object age, storage class, and version status.

Understanding that lifecycle policies execute asynchronously helps engineers design resilient architectures that do not depend on real-time synchronous execution for data deletion or tier transitions.
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