PDE Storing the Data Practice Question
A data engineer wants to automatically move objects from Standard storage class to Nearline after 30 days, and then to Archive after 365 days. Which Cloud Storage feature should they configure?
⚠ Common exam trap
Google often tests the distinction between lifecycle management (which changes storage classes) and retention/versioning features (which protect data but do not automate class transitions), leading candidates to confuse Object Versioning or Retention Policy with lifecycle rules.
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
✓
Object Lifecycle rule with SetStorageClass actions
Object Lifecycle rules in Google Cloud Storage allow you to automatically transition objects between storage classes (e.g., from Standard to Nearline after 30 days, then to Archive after 365 days) using the SetStorageClass action. This feature is specifically designed for automated lifecycle management, including deletion and class transitions, based on object age or other conditions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Object Versioning
Why it's wrong here
Object Versioning retains noncurrent object generations; it never changes storage class, so no time-based transition occurs. It is tempting because both are bucket-level lifecycle-adjacent settings, and it would be correct for recovering overwritten or deleted objects, not for cost-driven class transitions.
- ✗
Retention Policy
Why it's wrong here
Retention policies lock objects against deletion or modification for a fixed period; they cannot transition storage classes. Object Lifecycle Management performs the timed Standard→Nearline→Archive moves described. Retention policies would be the right choice for regulatory immutability or WORM compliance, not cost-tiering automation.
- ✗
Bucket Lock
Why it's wrong here
Bucket Lock enforces retention and prevents deletion or modification of objects; it cannot transition storage classes on a schedule. It is tempting because both are bucket-level policies, and it would be correct for regulatory retention or WORM compliance rather than lifecycle class changes.
- ✓
Object Lifecycle rule with SetStorageClass actions
Why this is correct
An Object Lifecycle rule with SetStorageClass actions transitions objects automatically from Standard to Nearline at 30 days and to Archive at 365 days, satisfying both age-based tiering constraints. Lifecycle rules act on object age without manual intervention or application code.
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
Related to this question
About these practice questions
Courseiva writes every PDE question from scratch — 747 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PDE exam.