PDE Storing the Data Practice Question
A data engineer wants to store archived log files in Cloud Storage with a retention policy that prevents deletion for 5 years. Which feature should they use?
⚠ Common exam trap
Google often tests the distinction between lifecycle rules that delete objects and retention policies that prevent deletion, so the trap here is assuming that a lifecycle rule with a Delete action can enforce a retention period, when in fact it does the opposite.
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
✓
Retention Policy on the bucket set to 5 years
A retention policy on a Cloud Storage bucket enforces a minimum retention period for all objects in the bucket, preventing deletion or overwrite until the policy duration has elapsed. Setting it to 5 years ensures that archived log files cannot be deleted before that time, meeting the data engineer's requirement exactly. This is a bucket-level, immutable setting that applies to all objects, unlike object-level holds or lifecycle rules.
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 Lifecycle rule with Delete action after 5 years
Why it's wrong here
A lifecycle Delete action removes objects after five years rather than preventing deletion during that period; it enforces no immutability. Lifecycle rules suit cost management, such as transitioning or expiring data, whereas a bucket retention policy with Bucket Lock blocks deletion for the fixed term.
- ✓
Retention Policy on the bucket set to 5 years
Why this is correct
A bucket retention policy locks objects for a fixed period, preventing deletion or modification until it expires. Setting it to five years satisfies the stem's immutability requirement, unlike lifecycle rules, which delete or transition objects and therefore cannot enforce retention.
- ✗
Object Hold (temporal)
Why it's wrong here
Object Hold is a temporary, manually applied or event-based hold on individual objects, not a time-bound retention rule. It is tempting because it does prevent deletion, but a five-year fixed retention policy requires a Bucket Lock retention policy, which enforces the duration automatically and cannot be removed early.
- ✗
Versioning enabled
Why it's wrong here
Versioning preserves overwritten or deleted object generations but permits deletion of the live version at any time, so it enforces no retention period. It is intended for recovery from accidental overwrites, not for guaranteeing five-year immutability, which requires a Bucket Lock retention policy.
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.