Cloud Storage Lifecycle Management Age Conditions

Planning and implementing storage and data solutions.

You need to set up a policy so that videos stored in a specific Cloud Storage Regional bucket are moved to Coldline after 90 days, and then deleted after one year from their creation. How should you set up the policy?

  1. Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 275 days (365 ג€" 90)
  2. Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 365 days. Correct Answer
  3. Use gsutil rewrite and set the Delete action to 275 days (365-90).
  4. Use gsutil rewrite and set the Delete action to 365 days.
Answer Correct answer: B — Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 365 days.

Community Insight

The exam traps candidates into subtracting transition days from the total retention period; the key insight is that lifecycle actions do not alter the object's creation timestamp.

This question tests the configuration of Cloud Storage Object Lifecycle Management rules for automatic storage class transitions and deletion based on object age. It establishes that deletion is calculated from the original creation date, not reset by lifecycle transitions.

Candidates often choose Option A because they incorrectly assume that moving an object to a different storage class via lifecycle management resets its creation date or age counter, leading them to calculate the delete action as 365 minus 90 days.

Community Discussion (165 comments)

mazindere 👍 1 Selected: B
It means from the day the object was created (first uploaded or saved) to the bucket.In GCP Cloud Storage, the Age condition is always measured relative to the object's original creation date, regardless of how many times its storage class changed.How the Timeline Works in Option B:Day 0: The video is uploaded/saved to the bucket (Creation Date).Day 90: SetStorageClass triggers. Object moves to Coldline (90 days since creation).Day 365: Delete triggers. Object is permanently deleted (365 days since creation).⚠️ Common Exam TrapThe exam tries to trick you into thinking the timer "resets" when an object changes storage classes (which is why Option A tries to subtract $365 - 90 = 275$).Remember for the ACE exam: GCP lifecycle Age never resets. Age $X$ always means $X$ days after the file first entered the bucket
omunoz 👍 2 Selected: A
It should be A, it says after 365 days of creation, not after moved to Coldline.
0d2fdfa 👍 1 Selected: B
Create two lifecycle rules on the bucket: Transition to Coldline after 90 days Condition: Age = 90 Action: SetStorageClass → Coldline Delete after 365 days Condition: Age = 365 Action: Delete This ensures: Objects remain in the original Regional class for 90 days. After 90 days → automatically moved to Coldline. After 365 days from creation → permanently deleted.
kewgard 👍 1 Selected: B
B. Its basic operation of cloud storage object lifecycle management. Not A as actions are run from measures from object creation time - not time duration after another action happened.
vaclavbenes1 👍 2 Selected: B
age The age condition is satisfied when a resource reaches the specified age (in days). Age is measured from the resource's creation time. https://cloud.google.com/storage/docs/lifecycle#age
devanshgoyal12 👍 1 Selected: D
Why answer is not D
peddyua 👍 1 Selected: B
{ "rule": [ { "action": { "type": "SetStorageClass", "storageClass": "COLDLINE" }, "condition": { "age": 90 } }, { "action": { "type": "Delete" }, "condition": { "age": 365 } } ] }
narop 👍 1 Selected: A
Cloud Storage Object Lifecycle Management allows you to define conditions and actions for objects based on their age, creation time, or other attributes. To meet the requirements: Move to Coldline after 90 days: This is achieved by setting a SetStorageClass action with an Age condition of 90 days. Delete after 1 year (365 days): Since the object would have been moved to Coldline after 90 days, the remaining time for deletion is 365 - 90 = 275 days. Set a Delete action with an Age condition of 275 days.
user263263 👍 2 Selected: B
A is not correct. age is defined based on creation time. SetStorageClass only affects the modification time, not the creation time. So the 90 days are not relevant for the deletion rule.
nubelukita45852 👍 1 Selected: B
La gestión del ciclo de vida de objetos en Google Cloud Storage permite automatizar el cambio de la clase de almacenamiento y la eliminación de los objetos en función de su antigüedad. Para este caso: Después de 90 días, se debe cambiar la clase de almacenamiento a Coldline, lo que se hace usando la acción SetStorageClass. Luego, después de 365 días (1 año), los objetos deben ser eliminados usando la acción Delete. A es incorrecta porque sugiere eliminar los objetos a los 275 días, lo cual no coincide con el requisito de eliminar los videos después de un año. C y D son incorrectas porque gsutil rewrite no es la herramienta correcta para gestionar políticas de ciclo de vida.
JackSkeletonCoder 👍 3 Selected: B
option A can be misguiding but you don't have to specify 275 days since the rule would be implemented based on the creation of object not after the effect of the previous rule. Hence option B
sh00001 👍 1
Option A Cloud Storage Object Lifecycle Management allows you to define a set of rules that manage the lifecycle of your objects. The Age condition specifies the number of days since the object's creation. The SetStorageClass action changes the storage class of objects within the bucket. Setting it to 90 days means that 90 days after the object's creation, it will be moved to Coldline Storage. The Delete action specifies when the object should be deleted. Because the SetStorageClass action occurs at 90 days, you would set the Delete action at 275 days (365 total days from the creation - 90 days already passed until the class change), resulting in the object being deleted one year from its creation.
torresbytea 👍 1 Selected: B
A is wrong cause there is no need of re-calculating. B is the right choice
Rahaf99 👍 1
Answer is B
gsmasad 👍 2 Selected: B
Time of creation is the reference NOT the time of movement
Evan7557 👍 1
Answer B
YourCloudGuru 👍 9 Selected: B
The correct answer is B. Cloud Storage Object Lifecycle Management is a feature that allows you to automatically transition objects to different storage classes or delete them based on user-defined rules. To set up a lifecycle management policy to move videos to Coldline after 90 days and then delete them after one year, you would create a rule with the following conditions and actions: Condition: Age is greater than 90 days Action: Set storage class to Coldline Condition: Age is greater than 365 days Action: Delete This policy will ensure that your videos are automatically moved to Coldline after 90 days, where they will be stored at a lower cost. After one year, the videos will be automatically deleted. Here is an example of how to create a lifecycle management policy using the gcloud command-line tool: gcloud storage lifecycle management policies set my-bucket my-policy --action-set-storage-class coldline --condition-age-days 90 --action-delete --condition-age-days 365
CarlosMarin 👍 2 Selected: A
"... and then deleted after one year FROM THEIR CREATION". I vote for A.
ExamsFR 👍 1 Selected: B
Answer is B
rosh199 👍 1
Answer is B
KerolesKhalil 👍 1
Answer is B . Age condition : The age condition is satisfied when a resource reaches the specified age (in days). Age is measured from the resource's creation time. For objects, the creation time is the time when the object is successfully written to the bucket, such as when an upload completes. https://cloud.google.com/storage/docs/lifecycle#age
Ashish_Tayal 👍 2 Selected: B
In GCP Storage, any rule either life cycle management or retention policy applies based on the creation date and time of the object. Even in the question they mention " from their creation". So ans is B.
Jelly_Wang 👍 3
The answer is B. When using Age, it is calculated from when the object is written to the bucket. The age do not get affected when you change the storage class .https://cloud.google.com/storage/docs/lifecycle#age
Partha117 👍 3 Selected: B
NO need to recalculate as it is from object original creation date
lights4life 👍 3
Answer is B. There is term called AGE, always GCP refers AGE by default which is since creation of the object.
PB78 👍 1
Answer is A as The age condition is satisfied when a resource reaches the specified age (in days). Age is measured from the resource's creation time. For objects, the creation time is the time when the object is successfully written to the bucket, such as when an upload completes. The age of an object is unaffected by the object becoming a noncurrent version.
Buruguduystunstugudunstuy 👍 5 Selected: B
To set up the policy to move videos stored in a specific Cloud Storage Regional bucket to Coldline after 90 days, and then delete them after one year from their creation, you can use Cloud Storage Object Lifecycle Management. You can configure the lifecycle rule to move objects to Coldline storage class after 90 days by setting an Age condition of 90 days and a SetStorageClass action to Coldline. Then, you can configure the rule to delete objects after one year (365 days) from their creation by setting an Age condition of 365 days and a Delete action. Therefore, Answer B is the correct answer. https://cloud.google.com/storage/docs/lifecycle https://cloud.google.com/storage/docs/lifecycle#age https://cloud.google.com/storage/docs/lifecycle#actions
ElonGPT 👍 1
Thank you for your detailed explanation with desc and links
prasadbishnu09 👍 1
The Correct answer is A, because in question it is mentioned "A YEAR OF THE CREATION"
Pksen 👍 1
Straigntforward the answer is B, as we are using Life Cycle Management.
Bobbybash 👍 4 Selected: A
The correct answer is A. Lets assume the object was created January 1st 2022, after 90 days (March 31st,2022), its moved to coldline storage, and later deleted one year after creation (31st December,2022), which is April 1st to December 31st (275 days). I hope this clears the misunderstanding
lifelonglearning 👍 1 Selected: B
Correct answer is B. See the official docs: https://cloud.google.com/storage/docs/lifecycle-configurations#:~:text=To%20move%20objects,of%20365.
aramisrocha 👍 2
A is incorrect because after 90 days files will be moved not created, policy delete consider create not move.
kashishr 👍 1 Selected: B
Answer is B. Question states 365 days after object creation.
ankyt9 👍 1
Correct answer is option B
romega2 👍 1 Selected: B
Of course B
fragment137 👍 1 Selected: B
The answer would be B. Object lifecycle is relative to the Creation date. So, 90 days to move (not re-writing a new file), and 365 to DELETE (from date of creation)
shykot 👍 2
they have already said one year after creation of data, which is 275+90 days
KirtiMohanta 👍 1 Selected: B
There is no need to recalculate days. Ans is "B"
KirtiMohanta 👍 1
Correct Ans is "B". No need to recalculate
betaspetsnaz 👍 1 Selected: B
Answer is B
xaqanik 👍 2 Selected: A
i think A is correct. 90 days includes to 365 . rest 275 days for deleting period.
AllMaaya 👍 1
Refer the Age detail https://cloud.google.com/storage/docs/lifecycle#age Answer should be 'B"
Tx4free 👍 2
A is correct. Because the question states 1 year after creation which includes the initial 90 days.
Baba_Voss 👍 1 Selected: A
A is the correct Answer
leogor 👍 1
B, no need to minus 90 days
vijay456 👍 3
Age is counted from when an object was uploaded to the current bucket, even if it moved from another
mvk2022 👍 1
Excellent answer. A is the answer.
PKookNN 👍 4 Selected: B
The key part is "deleted after one year from their creation" - B is correct at 365 days. If A is chosen then the object would be deleted BEFORE 1 year.
darkroomie 👍 4 Selected: A
A is the correct answer. It clearly specifies that videos are moved to coldline after 90 days and deleted after "A YEAR OF THE CREATION" (that includes the 90 days that counts for moving to coldline. So, videos are created one day, then moved to coldline after 90 days (+90) and deleted after a year of creation (90+275=365) A IS CORRECT....!!!
kadc 👍 1 Selected: B
Some suggested that rewritten changes the creation date, but here it stated that "Unlike changing an object's storage class manually, using SetStorageClass does not rewrite an object. This gives Object Lifecycle Management certain pricing advantages:" https://cloud.google.com/storage/docs/lifecycle#setstorageclass-cost With other scenarios stated at lower section, it doesn't look like creation date would changes
shreykul 👍 3
Why not A, I mean question states 365 days from the date of creation, and the data will be in cold-line for 90 days, 365-90=275 -> which should be set in lifeline? Am I wrong? or is the 90 days(Cold line period) is inclusive in the 365 days when creating life cylce management?
gandor 👍 2 Selected: A
A is the answer. The first object version should still be there after 90 days even if it was moved to cold line storage.
SaiSaiA 👍 2
Answer B, the date counted is when the object is uploaded into the Cloud Storage. It doesn't matter if it changed to a different storage class, it is still in the same bucket.
jayaen 👍 4
A is correct
Karthik_SIDDE 👍 4 Selected: A
Answer is A. The videos are stored in GCS and moved to coldline after 90 days, then deleted after one year of their creation
RanjithK 👍 1
Answer is B
AzureDP900 👍 1
B is right , This is also in Tutorials Dojo with detailed explanations.
Denis_TKM 👍 2 Selected: B
B because the file should be deleted after one year of existence inside the bucket.
JLJD 👍 5
The correct answer is A as it's a trick Q... it's one year from creation so 90 days + 275 days = 365 days
Yolex 👍 2
Yes, days are counted from the object creation!
haroldbenites 👍 1
Go for B
Pawan_Reddy 👍 1
Answer is B :- Since Coldline Storage has a 90-day minimum storage duration, and the object existed for a total of 80 days.
lzjh2000 👍 1
Obviously B is the correct answer. Unlike changing an object's storage class manually, using SetStorageClass does not rewrite an object. Check below doc for reference. https://cloud.google.com/storage/docs/lifecycle#setstorageclass-cost
VivekSolutionArchitect 👍 4 Selected: B
The answer is clearly B. If you go to the option "Select an action" for a specific cloud storage bucket and hover on the question mark for age. It clearly says "Counted from the object's creation date(when the object was added to the current bucket)
Ram_krishna 👍 1 Selected: A
I checked all over the sites, but all shows answer is A.
ryzior 👍 2 Selected: B
there are 2 rules in result , one for coldline with its own timing and the other for deletion with its own timing , both cont the age of the object , since changing the class of the storage has nothing to do with rewriting the object itself -just metadata, the age of the object is counted from the time it's been uploaded (if no other modification to the object itself in the meantine) so answered B
ryzior 👍 1
when you upload the same file again then the creation time is changed to current, so the policy timer is reset ( for both rules/lifecycle policies of course)
BAPII 👍 1
correct answer is B
anusha_ASD 👍 3 Selected: B
are you kidding me? 275 days doesn't make a year. a year have 365 days
Raz0r 👍 1 Selected: B
B is the right one, look it up.
Rakesh_SAP 👍 5 Selected: B
Answer B. The catch is "then deleted after one year from their creation." https://cloud.google.com/storage/docs/lifecycle#age Age The Age condition is satisfied when an object reaches the specified age (in days). Age is measured from the object's creation time. For example, if an object's creation time is 2019/01/10 10:00 UTC and the Age condition is 10 days, then the condition is satisfied for the object on and after 2019/01/20 10:00 UTC. This is true even if the object becomes noncurrent through Object Versioning sometime after its creation.
Akash7 👍 1
Answer is B. Check the Age section here: https://cloud.google.com/storage/docs/lifecycle#age
uganeshku 👍 1
B is correct because lifecycle management is used to change storage class or delete objects after specified days from creation. A is incorrect because the videos will get deleted after 275 days instead of a year.
AltHexMax 👍 4 Selected: B
I was very confused at first (thought it was A) but then I saw this example on Google's Documentation: https://cloud.google.com/storage/docs/managing-lifecycles#change_an_objects_storage_class For the second condition it changes the storage class after 1095 days the object was created. If you see the instructions it does not recalculate the days, it takes the whole 1095 days.
srj86 👍 2
Correct answer seem to be A. Delete time calculated from time of creation but not from the change of storage Class. See below from GCP Docs. For example, say you upload an object as Nearline Storage, and 20 days later your lifecycle configuration changes the storage class of the object to Coldline Storage. This change incurs no retrieval or early deletion fees. If you then delete the object 60 days after the storage class change, there is only a 10-day early deletion charge, since Coldline Storage has a 90-day minimum storage duration, and the object existed for a total of 80 days. In comparison, say you upload an object as Nearline Storage, and 20 days later change the storage class using a rewrite (again to Coldline Storage). This change incurs both a retrieval fee and a 10-day early deletion charge. If you then delete the object 60 days after the rewrite, there is a 30-day early deletion charge.
onyb 👍 1
Answer is A - The object's time spent set at the original storage class counts towards any minimum storage duration that applies for the new storage class (https://cloud.google.com/storage/docs/lifecycle)
koxow74213 👍 1 Selected: B
B is correct
dxloader 👍 1 Selected: B
Answer is B. There should be no reason to recalculate the time needed to delete after a year.
jabrrJ68w02ond1 👍 2 Selected: B
You dont need to calculate,the creation date of objects does not change.
koxow74213 👍 1 Selected: B
B is right. Storage class or deletion is applied N days from the date of creation/updated. It doesn't take change of storage class into account.
MariGK 👍 1 Selected: B
B is the right answer
shawnkkk 👍 1
B. Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 365 days.
vishnukumartr 👍 1
B. Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 365 days.
Jaira1256 👍 1
B is correct
kenneth1998 👍 3
lol, is this a math question? the correct answer is B
jackwillis 👍 1
B is correct
Shruti_Pal 👍 1
B is right
beginnercloud 👍 1
Please modify, correct is B
YAS007 👍 1
B is correct from gcp : "The Age condition is satisfied when an object reaches the specified age (in days). Age is measured from the object's creation time. For example, if an object's creation time is 2019/01/10 10:00 UTC and the Age condition is 10 days, then the condition is satisfied for the object on and after 2019/01/20 10:00 UTC. This is true even if the object becomes noncurrent through Object Versioning sometime after its creation." https://cloud.google.com/storage/docs/lifecycle
akshayeonline 👍 1
Correct answer is B ( days calculated from initial date )
sidharthwader 👍 1
Answer must be A. It says it should be removed 365 days after the creation so 275+90 =365 days. Please correct me if am wrong !
sidharthwader 👍 1
sorry it should be B. As per age its from the day its created so B is the answer
tanito83 👍 2
Gentlemen, the answer is B. Please, modify it.
vmart 👍 1
B is the right choice
Umesh09 👍 1
Answer is B you calculated from day the data is initially written on the bucket not when it moves from one tier to other
Finger41 👍 1
The keyword is creation, which can be handled by a lifecycle policy.It will be deleted after 365 days. Answer B is correct.
mcaromit 👍 1
B is correct
ready2rock 👍 1
Thank you for digging into it and reposting/correcting your answer. I was trying to determine if changing storage class cause a rewrite (since this is the way to decide whether B or A is the right answer). Looks like you found it, making B the right answer
lxgywil 👍 3
"A" is correct since modifying the Storage Class creates a new version for the object. The "creation time" reflects the time when that last version was created. Therefore, you do need to subtract those 90 days. This is pretty easy to test in the GCP Console: 1. Upload an object to a GCS bucket and see its creation time. 2. Wait for a few minutes and run gsutil rewrite -s coldline gs://PATH_TO_OBJECT. 3. Note that the object's creation time changed. 4. Run gsutil ls -ahl gs://BUCKET_NAME and you will note that modifying the Storage Class has created a new version for your object (which creation time is, obviously, different).
lxgywil 👍 7
I was wrong - the answer is indeed "B". Changing Storage Class via Lifecycle Management doesn’t rewrite the object, thus its creation time stays the same.
mistryminded 👍 2
Answer should be B. as per this doc:https://cloud.google.com/storage/docs/lifecycle#age Age is measured from the object's creation time. Also,This is true even if the object becomes noncurrent through Object Versioning sometime after its creation. Hence, answer should be B not A
ApaMokus 👍 1
The correct answer is B. The Age condition is measured from the object's creation time. Unlike changing an object's storage class manually, using SetStorageClass does not rewrite an object. https://cloud.google.com/storage/docs/lifecycle
maddy5835 👍 1
A is the correct answere, Unlike changing an object's storage class manually, using SetStorageClass does not rewrite an object.
ozeross 👍 3
B is the correct answer no need to recalcuate
kopper2019 👍 1
B is the way to go
pradr 👍 1
Storage class change via life cycle management does not use the rewrite option similar to changing storage class of an object manually using gsutil where the create date would get changed since its a rewrite. So the create date would remain unchanged and hence the file can be set to be deleted on attaining an age of 365 days.
sasha0518 👍 1
B is the answer
EABDAJA 👍 1
B is correct
kipsnak 👍 1
I think the answer is A because SetStorageClass does not rewrite an object, so the creation date will remain the same. Since the question states 356 days from creation, the delete value should be set as 356 - 90 days. "Unlike changing an object's storage class manually, using SetStorageClass does not rewrite an object" Source: https://cloud.google.com/storage/docs/lifecycle#setstorageclass-cost
Vinod87 👍 2
Vote B
Nickkk 👍 2
Correct Ans : B For example, say you upload an object as Nearline Storage, and 20 days later your lifecycle configuration changes the storage class of the object to Coldline Storage. This change incurs no retrieval or early deletion fees. If you then delete the object 60 days after the storage class change, there is only a 10-day early deletion charge, since Coldline Storage has a 90-day minimum storage duration, and the object existed for a total of 80 days. https://cloud.google.com/storage/docs/lifecycle#setstorageclass-cost
victory108 👍 2
B - Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 365 days.
Gohs 👍 2
Ans: B Since they'll be deleted after one year. So it should be set to 365days.
DucSiu 👍 1
Answer is A => deleted after one year from their creation.
INASR 👍 2
Answer is sure B
Mutt1 👍 2
B. The question states to use the "Age" condition which is measured from the object's creation. Changing the storage class to coldline after 90 days does not change the age.
nherrerab 👍 1
B is correct.
Gentio 👍 4
First, the "Age" conditions are based on the Objects creation time (ref.:https://cloud.google.com/storage/docs/lifecycle#age). Afterward, the objects creation time property is established when the object is added to the bucket. In other words, if you make a change on the object inside a bucket, you don't change its creation time. A: Here, we consider the object moving among buckets, which is not mentioned in the question. B: Here, we consider that the object suffers a change inside the bucket, which matches the question's perspective. C & D: You can use gsutil to do the task. However, to be productive, it should use gsutil with the lifecycle parameter. (ref.: https://cloud.google.com/storage/docs/gsutil/commands/lifecycle) Answer: B
Gentio 👍 2
First, the "Age" conditions are based on the Objects creation time (ref.:https://cloud.google.com/storage/docs/lifecycle#age). Afterward, the objects creation time property is established when the object is added to the bucket. In other words, if you make a change on the object inside a bucket, you don't change its creation time. A: Here, we consider the object moving among buckets, which is not mentioned in the question. B: Here, we consider that the object suffers a change inside the bucket, which matches the question's perspective. C & D: You can use gsutil to do the task. However, to be productive, it should use gsutil with the lifecycle parameter. (ref.: https://cloud.google.com/storage/docs/gsutil/commands/lifecycle)
Conjoinix 👍 2
Answer is B. https://cloud.google.com/storage/docs/managing-lifecycles#deletion-example
mohdafiuddin 👍 3
Correct answer in this case is B. Refer - https://cloud.google.com/storage/docs/lifecycle#age and Explanation - There are two ways of changing the storage class of an object. 1. Rewriting 2. Using the Object Lifecycle Management (src - https://cloud.google.com/storage/docs/storage-classes#key-concepts) The age of the object does not change when it is moved to a different storage using the object lifecycle management. The age is calculated from the date of creation. Since we need to move it to a different storage after 90 days from creation and delete it one year after creation, we simply need to use the numbers 90 and 365 since the date of creation (and therefore age) remains the same.
andyhandles 👍 1
Should be B. Google docs clearly states "The Age condition is satisfied when an object reaches the specified age (in days). Age is measured from the object's creation time."
eche1984 👍 1
When should be the object's creation time? When the upload was completed or when the object's class turn to Coldline?
alpharomeo9 👍 1
So, for example, if you have one rule that deletes an object and another rule that changes the object's storage class, but both rules use the exact same condition, the delete action always occurs when the condition is met. If you have one rule that changes the object's class to Nearline Storage and another rule that changes the object's class to Coldline Storage, but both rules use the exact same condition, the object's class always changes to Coldline Storage when the condition is met. The Delete action takes precedence over any SetStorageClass action. These above statements are directly copied form the GCP docs. https://cloud.google.com/storage/docs/lifecycle in the above link go to lifecycle configuration and read the whole thing. So I will go with option B
amitkumardube 👍 1
A - Once an action occurs, the object is re-evaluated before any additional actions are taken. - https://cloud.google.com/storage/docs/lifecycle so after change of class is done, the object will be reevaluated for new condition from that time. so correct answer should be A
Faraz2 👍 1
B is correct Object Lifecycle Management does not rewrite an object when changing its storage class. When an object is transitioned to Nearline Storage, Coldline Storage, or Archive Storage using the SetStorageClass feature, any subsequent early deletion and associated charges are based on the original creation time of the object, regardless of when the storage class changed. Ref: https://cloud.google.com/storage/docs/lifecycle
Faraz2 👍 1
sorry option A
sadas159 👍 1
Hello Everyone , I read in he official page of GCP "An object lifecycle SetStorageClass action is not affected by the existence of object holds or retention policies." In this case the correct answer is B https://cloud.google.com/storage/docs/lifecycle Regards
yvinisiupacuando 👍 13
Right answer is clearly B, "A" does not make any sense.
cecocenov 👍 2
Correct answer is B as there are 2 actions needed. First archival after 90 days, which can be done by SetStorageClass action to Coldline. Second delete the data after a year, which can be done by delete action with Age 365 days. The Age condition is measured from the object's creation time.Refer GCP documentation - Cloud Storage Lifecycle ManagementAge: This condition is satisfied when an object reaches the specified age (in days). Age is measured from the object's creation time. For example, if an object's creation time is 2019/01/10 10:00 UTC and the Age condition is 10 days, then the condition is satisfied for the object on and after 2019/01/20 10:00 UTC. This is true even if the object becomes archived through object versioning sometime after its creation.Option A is wrong as the Age needs to be set to 365 as its relative to the object creation date and not changed date.Options C & D are wrong as gsutil rewrite can be used to change the storage class. However, it needs to be triggered and the solution does not handle archival of data.
swatititame 👍 1
• B. Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 365 days.
cuban123 👍 2
Did a lab confirming its A. Days are counted from creation of object. its the time since when the object was added to the current bucket
gh999l 👍 2
A is the correct answer
cuban123 👍 2
Can someone confirm why is B... (shouldn't be A?)? when creating google storage lifecycle rule it says: "Age is counted from when an object was uploaded to the current bucket, even if it moved from another"
nwk 👍 1
Vote B
JohnnyS20 👍 3
Just think of it this way: It's January 1, 2020 and you were asked to move a set of files to Coldline storage after the first quarter of the year. However, your team wants to store it until December 2020 in case it'll be needed. Now you plan to set the policy to move it to Coldline storage after 3 months. To keep it there until December, you must also set deletion to take effect after 1 year or 365 days. This means the files will be deleted on January 1,2021 next year. Now if you set policy to move it to Coldline after 3months and set the deletion to take effect after 275 days, the files will defniitely be moved after March to Coldline but won't reach December because it will already be deleted on Oct 1 - which is the 276th day. The countdown for the policy to move the files to Coldline and to delete it after a year STARTS AT THE SAME TIME. Correct answer: B
JKRowlings 👍 6
The correct ans is A.
Ravihonnagiri 👍 3
Answer is definitely B SetStorageClass cost advantages Unlike changing an object's storage class manually, Object Lifecycle Management does not rewrite an object when it changes the object's storage class. This gives Object Lifecycle Management certain pricing advantages: There are no retrieval fees or early deletion fees associated with the storage class change, even when the object is originally set to Nearline Storage or Coldline Storage. The object's time spent set at the original storage class counts towards any minimum storage duration that applies for the new storage class.
glam 👍 5
B. Use Cloud Storage Object Lifecycle Management using Age conditions with SetStorageClass and Delete actions. Set the SetStorageClass action to 90 days and the Delete action to 365 days.
JKRowlings 👍 1
A is correct. It is cost effective.
prasanu 👍 1
so A or B ? ,
prasanu 👍 2
I think A is the answer.
JJ_ME 👍 5
Answer is B. Age is measured from the object's creation time. Object Lifecycle Management does not rewrite an object when it changes the object's storage class. Therefore the object's creation time remains unchanged. https://cloud.google.com/storage/docs/lifecycle#age https://cloud.google.com/storage/docs/lifecycle#setstorageclass-cost
NKG1 👍 1
It would be B - when creating life cycle for delete for an object its asked abut the Age check box which is age from creation date - not from when it moved to Coldline or any other storage class.
adityatanak 👍 1
answer is def B. as it doesnt mention from what date it needs to be deleted. ideal conditions will be B unless it has been mentioned.
sourabhjagtap95 👍 1
Is the answer A then, or B?
itsmebharat 👍 1
Answer is B Age: Counted from the object’s creation date (when the object was added to the current bucket)
SSPC 👍 2
I dont sure between A or b
SSPC 👍 2
A is correct
jzh 👍 2
Here is I made LC rule with Age condition: Delete object: 365+ days since object was updated Set to Coldline: 90+ days since object was updated Set to Coldline action happens after 90 days and this counts as "object was update", then Delete object age should be 365 - 90 = 275. So answer would be A.
Bituz 👍 2
A please check the Google doc examples
sumanshu 👍 1
Option A is wrong as the Age needs to be set to 365 as its relative to the object creation date and not changed date
samvegas 👍 2
A - Because - When creating rule - Age = "Time elapsed since objects uploaded to current bucket." - which means first rule 1> 90 days to Nearline from object creation date 2> 365-90 days for delete action. You can also see creation date from gsutil stat gs://<>
Ozymandiax 👍 2
I think this is it. It states that the dele action should be referred to the creation date, not the date of the first transition in the lifecycle.
agrawaladi3 👍 5
Option A deleted after one year from their creation. Creation 365-90
babu789 👍 1
https://cloud.google.com/storage/docs/managing-lifecycles its B
professor 👍 2
and then deleted after one year from their creation.
cloudenthu01 👍 44
Correct is B. You only re-calculate expiry date when objects are re-written using re-write option to another storage class in which case creation date is rest. But in this case objects is moveed to Coldline class after 90 days and then we want to delete the object after 365 days.
T_T_M 👍 16
You can change the storage class of an existing object either by rewriting the object or by using Object Lifecycle Management...Since Object Life cycle management was used there was no need to recalculate the expiration date and delete action still remains 365 days. https://cloud.google.com/storage/docs/storage-classes
babu789 👍 1
How its A
manu202020 👍 4
Delete action need to be set on creation date, and doesn't change on changing storage class.
mlantonis 👍 6
It is defenitely B
saurabh1805 👍 7
B is correct answer as you dont need to calculate expiry date, that remain same irrespective of storage class.
Sammigbo 👍 60
Answer is B. There should be no reason to recalculate the time needed to delete after a year.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Option B is correct because Cloud Storage Object Lifecycle Management operates independently of object metadata updates like creation time. When a rule transitions an object to Coldline after 90 days, it does not rewrite the object in a way that changes its timeCreated attribute. Therefore, the deletion condition remains anchored to the original creation date, requiring a simple 365-day age condition for deletion.

Why the Other Options Are Wrong

Option A is incorrect because it assumes a recalculation of the remaining lifespan (365 - 90 = 275), which contradicts how lifecycle rules evaluate age against the creation timestamp. Options C and D are invalid because gsutil rewrite is a manual command-line tool used for immediate operations, not for setting up automated, persistent lifecycle policies on buckets.

Community Comment Notes

Community consensus strongly supports Option B, with many users noting that lifecycle transitions do not reset the creation date. As one commenter noted, "Changing Storage Class via Lifecycle Management doesn’t rewrite the object, thus its creation time stays the same." Another user clarified that you only recalculate if using specific re-write options that explicitly change metadata, which standard lifecycle rules do not.

Official Reference

https://cloud.google.com/storage/docs/lifecycle

Exam Strategy

When configuring lifecycle rules, always check if the action modifies the object's creation timestamp. For standard transitions (SetStorageClass), the age counter continues from the original creation date, so deletion timers should be absolute relative to creation, not relative to the transition.

Frequently Asked Questions

Does moving an object to Coldline reset its creation date?

No. Standard lifecycle management transitions do not update the object's timeCreated metadata. The age continues to count from the original creation.

Why is gsutil rewrite not suitable for this policy?

gsutil rewrite is a manual command for immediate execution. It cannot automate recurring rules like deleting objects after one year based on their age.

More ACE FAQ →

Related Analysis

You created an instance of SQL Server 2017 on Compute Engine

S-Grade

You want to send and consume Cloud Pub/Sub messages from you

S-Grade

You have one GCP account running in your default region and

S-Grade

Practice All ACE Questions

Access 84 questions with complete answers and detailed explanations.

View Full ACE Practice Test →

← Back to ACE Study Guide