GCP Professional Data Engineer Practice Question

You have enabled object versioning on a Cloud Storage bucket that ingests hundreds of daily CSV files. Governance rules mandate that every live object must be removed 365 days after its creation, while any non-current (non-live) object version may remain only 30 days after it became non-current. You need a lifecycle configuration that enforces these requirements without deleting objects prematurely. Which set of lifecycle rules should you apply to the bucket?

Two Delete rules: one with age: 365; a second with numNewerVersions: 30.
Two Delete rules using fixed calendar dates: createdBefore set to 365 days ago and noncurrentTimeBefore set to 30 days ago.
A single Delete rule with age: 365 and no isLive condition.
Two Delete rules: one with age: 365, isLive: true; a second with daysSinceNoncurrentTime: 30, isLive: false.

Report Issue

Answer Description

To meet both retention windows you need two independent Delete actions:

A rule that targets only live objects (isLive: true) and deletes them when their age reaches 365 days. This satisfies the one-year retention of the current revision.
A second rule that targets only non-live objects (isLive: false) and deletes them when daysSinceNoncurrentTime equals 30. This timer starts when a newer revision is made current, so it precisely controls the lifetime of previous versions. Using only an age condition without the isLive filter would treat live and non-live objects the same, violating the 30-day requirement. A rule that relies on numNewerVersions or fixed calendar dates would not guarantee rolling compliance as new objects arrive each day. Therefore the configuration that combines age: 365, isLive: true with daysSinceNoncurrentTime: 30, isLive: false is the only option that fulfills both policies safely.

Ask Bash

Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.