Google ACE Practice Question: Your organization uses Cloud Storage for storing…

Your organization uses Cloud Storage for storing backups. You want to automatically delete backup objects that are older than 30 days to control costs. You also want objects between 7 and 30 days old to use Nearline storage class for lower cost. Which Cloud Storage feature manages both requirements in a single configuration?

⚠ Common exam trap

Google Cloud often tests the misconception that custom code or external schedulers are required for automated object management, when in fact Cloud Storage's built-in lifecycle management can handle both storage class transitions and deletions in a single, cost-effective configuration.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Configure Object Lifecycle Management rules on the bucket with `SetStorageClass` and `Delete` actions.

Object Lifecycle Management rules in Cloud Storage allow you to define conditions (e.g., object age) and actions (e.g., SetStorageClass to Nearline, Delete) in a single configuration. This automates both the transition of objects aged 7–30 days to Nearline storage and the deletion of objects older than 30 days, without custom code or manual intervention.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Write a Cloud Function that runs daily, lists objects, and deletes or moves old ones.
Why it's wrong here
A Cloud Function that runs daily, lists objects, and deletes or moves them would work, but it requires writing and maintaining custom code, configuring a trigger (e.g., Cloud Scheduler), and handling permissions for the function to access the bucket. You also have to manage retries, logging, and potential concurrent execution issues. Object Lifecycle Management is the purpose-built, fully managed feature that makes this logic declarative and free of operational overhead.
✓
Configure Object Lifecycle Management rules on the bucket with `SetStorageClass` and `Delete` actions.
Why this is correct
Object Lifecycle Management (OLM) is the native, serverless solution for this exact scenario. You can define a rule with a `SetStorageClass` action to transition objects to Nearline 7 days after creation, and a separate `Delete` action to permanently remove them after 30 days. Both actions live in the same bucket's lifecycle configuration, so no custom code, scheduler, or manual intervention is needed, and Google Cloud executes the rules automatically.
✗
Set a bucket-level retention policy of 30 days and manually change storage classes.
Why it's wrong here
A bucket retention policy enforces a minimum retention period by blocking deletion of objects before the specified time elapses, which is the exact opposite of deleting 30-day-old objects. It also has no mechanism to change storage classes automatically, so you'd still need to manually move objects to Nearline yourself. This option fails on both counts: it prevents deletion rather than enabling it, and it does not automate the storage class transition.
✗
Use Cloud Scheduler to trigger `gsutil` commands that move and delete old objects.
Why it's wrong here
Using Cloud Scheduler to invoke a `gsutil` command that moves and deletes objects is a valid workaround, but it requires you to provision and maintain a compute environment (e.g., a VM or Cloud Shell) where `gsutil` runs, authenticate it, and schedule and monitor jobs. This adds operational complexity and potential failure points compared to a declarative OLM rule. For a simple time-based transition and deletion, OLM is the recommended, zero-maintenance approach.

Quick reference

AWS S3 Storage Class Comparison

Storage Class	Min Duration	Retrieval	Use Case
S3 Standard	None	Immediate	Frequently accessed data
S3 Standard-IA	30 days	Immediate	Infrequent access, rapid retrieval
S3 One Zone-IA	30 days	Immediate	Non-critical infrequent data
S3 Intelligent-Tiering	None	Immediate–hours	Unknown or changing access patterns
S3 Glacier Instant	90 days	Milliseconds	Archive with instant retrieval
S3 Glacier Flexible	90 days	Minutes–hours	Archive, flexible retrieval
S3 Glacier Deep Archive	180 days	Hours	Long-term compliance archive

Go deeper

Google ACE Practice Question: Your organization uses Cloud Storage for storing…

Why each option matters

Option-by-option breakdown

AWS S3 Storage Class Comparison

Related to this question