A financial services organization ingests large volumes of transaction audit records into Google Cloud Storage. The data lifecycle requirements and access patterns are defined as follows: First 30 days: Records are actively analyzed and queried on a daily basis. Day 31 to 365: Records are accessed at most once per quarter during periodic compliance reviews. Day 366 to Year 7 (2,555 days): Records are kept strictly for legal compliance, accessed less than once a year, and must be retrievable within milliseconds when requested. After 7 years: Records must be permanently purged to comply with data privacy policies. You need to design an automated, cost-optimized storage lifecycle strategy for the bucket. Which configuration should you implement?

Set the default bucket storage class to Standard, and configure Object Lifecycle Management rules with `SetStorageClass` to Coldline at age 30 days, `SetStorageClass` to Archive at age 365 days, and `Delete` at age 2,555 days: What Object Lifecycle Management and Storage Classes Are Object Lifecycle Management (OLM) in Google Cloud Storage allows you to define declarative rules that automatically manage the lifecycle of objects within a bucket. By defining condition-action pairs, Cloud Storage inspects objects and automatically executes operations like changing storage classes (SetStorageClass) or permanently removing data (Delete) without operational intervention. How It Meets Each Requirement Active Daily Analytics (First 30 Days): Using Standard storage as the initial class avoids retrieval fees and provides low-latency access for high-frequency daily queries. Quarterly Compliance Reviews (Day 31 to 365): Transitioning to Coldline storage at age 30 days significantly reduces at-rest storage costs while matching the access pattern of at most once per quarter (Coldline requires a 90-day minimum duration). Long-Term Legal Retention (Day 366 to 7 Years): Transitioning to Archive storage at age 365 days lowers storage costs to the lowest available tier for data accessed less than once a year, while preserving millisecond retrieval latency. Automated Purging (After 7 Years / 2,555 Days): The Delete lifecycle rule automatically removes objects older than 2,555 days, ensuring compliance with data privacy mandates. Key Advantages Automated cost reduction: Storage tiers automatically degrade over time as access frequency drops. No offline retrieval delays: Unlike tape or cold archive tiers from other cloud providers, Archive storage objects are available in milliseconds. Zero operational overhead: OLM executes asynchronously without maintaining external cron jobs or custom microservices. Predictable compliance: Automatically enforces strict 7-year data retention and disposal limits. Why This Is Optimal This solution matches each lifecycle phase to its most cost-effective storage class while avoiding early deletion or retrieval penalties. It delivers a fully managed, declarative solution directly within Cloud Storage.

StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Cloud Storage Lifecycle Storage Class Optimization

Section: Cost optimization

A financial services organization ingests large volumes of transaction audit records into Google Cloud Storage. The data lifecycle requirements and access patterns are defined as follows:

First 30 days: Records are actively analyzed and queried on a daily basis.
Day 31 to 365: Records are accessed at most once per quarter during periodic compliance reviews.
Day 366 to Year 7 (2,555 days): Records are kept strictly for legal compliance, accessed less than once a year, and must be retrievable within milliseconds when requested.
After 7 years: Records must be permanently purged to comply with data privacy policies.

You need to design an automated, cost-optimized storage lifecycle strategy for the bucket.

Which configuration should you implement?

Set the default bucket storage class to Archive, and configure an Object Lifecycle Management rule to transition objects to Standard for the first 30 days and delete them after 2,555 days

Set the default bucket storage class to Standard, and deploy a Cloud Run function triggered by Cloud Scheduler to rewrite objects to Coldline and Archive and delete expired records

Enable Autoclass on the bucket, and configure an Object Lifecycle Management rule with a SetStorageClass action to transition objects to Archive at age 365 days and a Delete action at age 2,555 days

Set the default bucket storage class to Standard, and configure Object Lifecycle Management rules with SetStorageClass to Coldline at age 30 days, SetStorageClass to Archive at age 365 days, and Delete at age 2,555 days

Professional Cloud Architect

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Cloud Storage Lifecycle Storage Class Optimization

Section: Cost optimization

A financial services organization ingests large volumes of transaction audit records into Google Cloud Storage. The data lifecycle requirements and access patterns are defined as follows:

First 30 days: Records are actively analyzed and queried on a daily basis.
Day 31 to 365: Records are accessed at most once per quarter during periodic compliance reviews.
Day 366 to Year 7 (2,555 days): Records are kept strictly for legal compliance, accessed less than once a year, and must be retrievable within milliseconds when requested.
After 7 years: Records must be permanently purged to comply with data privacy policies.

You need to design an automated, cost-optimized storage lifecycle strategy for the bucket.

Which configuration should you implement?

Set the default bucket storage class to Archive, and configure an Object Lifecycle Management rule to transition objects to Standard for the first 30 days and delete them after 2,555 days

Set the default bucket storage class to Standard, and deploy a Cloud Run function triggered by Cloud Scheduler to rewrite objects to Coldline and Archive and delete expired records

Explanations

What Object Lifecycle Management and Storage Classes Are

Object Lifecycle Management (OLM) in Google Cloud Storage allows you to define declarative rules that automatically manage the lifecycle of objects within a bucket. By defining condition-action pairs, Cloud Storage inspects objects and automatically executes operations like changing storage classes (SetStorageClass) or permanently removing data (Delete) without operational intervention.

How It Meets Each Requirement

Active Daily Analytics (First 30 Days): Using Standard storage as the initial class avoids retrieval fees and provides low-latency access for high-frequency daily queries.
Quarterly Compliance Reviews (Day 31 to 365): Transitioning to Coldline storage at age 30 days significantly reduces at-rest storage costs while matching the access pattern of at most once per quarter (Coldline requires a 90-day minimum duration).
Long-Term Legal Retention (Day 366 to 7 Years): Transitioning to Archive storage at age 365 days lowers storage costs to the lowest available tier for data accessed less than once a year, while preserving millisecond retrieval latency.
Automated Purging (After 7 Years / 2,555 Days): The Delete lifecycle rule automatically removes objects older than 2,555 days, ensuring compliance with data privacy mandates.

Key Advantages

Automated cost reduction: Storage tiers automatically degrade over time as access frequency drops.
No offline retrieval delays: Unlike tape or cold archive tiers from other cloud providers, Archive storage objects are available in milliseconds.
Zero operational overhead: OLM executes asynchronously without maintaining external cron jobs or custom microservices.
Predictable compliance: Automatically enforces strict 7-year data retention and disposal limits.

Why This Is Optimal

This solution matches each lifecycle phase to its most cost-effective storage class while avoiding early deletion or retrieval penalties. It delivers a fully managed, declarative solution directly within Cloud Storage.

View source documentation

Professional Cloud Architect

Cloud Storage Lifecycle Storage Class Optimization

Professional Cloud Architect

Cloud Storage Lifecycle Storage Class Optimization

What Object Lifecycle Management and Storage Classes Are

How It Meets Each Requirement

Key Advantages

Why This Is Optimal

Related questions