An enterprise stores millions of compliance audit logs and supporting evidence artifacts in a Cloud Storage bucket initialized with the Standard storage class. The data architecture team establishes the following data retention and cost optimization requirements: All active objects older than 365 days must transition from Standard storage to Coldline storage to lower at-rest storage expenses for regulatory archival. Transitioning millions of small index and thumbnail files under 5 MiB must be avoided, as the Class A operation fees for SetStorageClass would exceed any monthly storage cost savings. The storage transition mechanism must not incur retrieval charges or inter-region replication fees during the storage class migration. Which Object Lifecycle Management configuration should the security engineer deploy on the bucket?

Configure a lifecycle rule with a SetStorageClass action targeting COLDLINE, specifying conditions for age of 365 days, matchesStorageClass set to STANDARD, and sizeAboveBytes set to 5242880.: ### What Object Lifecycle Management with Size Filtering Is **Object Lifecycle Management (OLM)** in Google Cloud Storage automates object transition and deletion policies. The `SetStorageClass` lifecycle action alters the storage tier of an object asynchronously without rewriting data bytes or triggering data movement pipelines. ### How It Meets the Requirements - **Regulatory Archival at 365 Days**: Setting the `age` condition to `365` and `matchesStorageClass` to `STANDARD` ensures that only active objects that have resided in Standard storage for a full year transition to the `COLDLINE` tier. - **Preventing Inefficient Class A Operation Fees**: Applying `sizeAboveBytes: 5242880` (5 MiB) filters out small index files and thumbnails. Because executing `SetStorageClass` is billed as a **Class A operation** against the destination class, small objects can incur transition API charges that dwarf ongoing capacity savings. - **Avoiding Retrieval and Inter-Region Fees**: Unlike manual copy or rewrite routines, Cloud Storage lifecycle transitions using `SetStorageClass` do not rewrite the underlying object data. Consequently, they incur zero retrieval fees and zero inter-region network charges. ### Key Advantages - **Automated Policy Enforcement**: Evaluates object metadata asynchronously without client-side compute overhead. - **Granular Filter Combinations**: Combines **`age`**, **`matchesStorageClass`**, and **`sizeAboveBytes`** within a single rule condition block. - **Cumulative Duration Credit**: Time spent in the original storage class counts toward the minimum retention duration of subsequent storage tiers. ### Why This Is Optimal This declarative lifecycle approach eliminates manual batch scripts, avoids unneeded operation expenses on small files, and safeguards against unexpected egress and retrieval billing.

Cloud Storage Lifecycle Coldline Size Transition | Professional Cloud Security Engineer

Cloud Storage Lifecycle Coldline Size Transition

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise stores millions of compliance audit logs and supporting evidence artifacts in a Cloud Storage bucket initialized with the Standard storage class. The data architecture team establishes the following data retention and cost optimization requirements:

All active objects older than 365 days must transition from Standard storage to Coldline storage to lower at-rest storage expenses for regulatory archival.
Transitioning millions of small index and thumbnail files under 5 MiB must be avoided, as the Class A operation fees for SetStorageClass would exceed any monthly storage cost savings.
The storage transition mechanism must not incur retrieval charges or inter-region replication fees during the storage class migration.

Which Object Lifecycle Management configuration should the security engineer deploy on the bucket?

Configure a lifecycle rule with a Delete action conditioned on an age of 365 days and matchesStorageClass set to STANDARD, paired with an automated Cloud Function to rewrite surviving objects into Coldline.

Configure a lifecycle rule with a SetStorageClass action targeting COLDLINE, specifying conditions for age of 365 days, matchesStorageClass set to STANDARD, and sizeAboveBytes set to 5242880.

Configure a lifecycle rule with a SetStorageClass action targeting COLDLINE, specifying conditions for age of 365 days, matchesStorageClass set to STANDARD, and sizeBelowBytes set to 5242880.

Configure a lifecycle rule with a SetStorageClass action targeting COLDLINE, specifying conditions for daysSinceNoncurrentTime of 365 days and matchesStorageClass set to STANDARD.

Professional Cloud Security Engineer

Cloud Storage Lifecycle Coldline Size Transition

Related questions