Lifecycle management rules in GCP - Step-by-Step Execution

Process Flow - Lifecycle management rules

Define lifecycle rule

↓

Rule conditions checked

↓

If conditions met?

No→Wait for next check

Yes↓

Perform action (e.g., delete, archive)

↓

Update object state

↓

Repeat for all objects

Lifecycle management rules check objects regularly and perform actions like deleting or archiving when conditions are met.

Execution Sample

GCP

lifecycle_rule = {
  "condition": {"age": 30},
  "action": {"type": "Delete"}
}

object_age = 35

if object_age >= lifecycle_rule["condition"]["age"]:
  perform_action = lifecycle_rule["action"]["type"]

This code checks if an object is older than 30 days and deletes it if true.

Process Table

Step	Object Age	Condition (age >= 30)	Action Taken	Result
1	35	True	Delete	Object deleted
2	25	False	None	Object kept
3	30	True	Delete	Object deleted
4	29	False	None	Object kept
Exit	-	No more objects to check	-	Lifecycle process ends

💡 All objects checked, lifecycle rules applied where conditions met

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
object_age	varies	35	25	30	29	-
condition_met	False	True	False	True	False	-
action	None	Delete	None	Delete	None	-

Key Moments - 2 Insights

Why does the action only happen when the object age is equal or greater than 30?

Because the lifecycle rule condition checks if the object age is at least 30 days (see execution_table steps 1 and 3 where condition is True and action is Delete).

What happens if the object age is less than 30?

No action is taken and the object is kept (see execution_table steps 2 and 4 where condition is False and action is None).

Visual Quiz - 3 Questions

Look at the execution table, what is the action taken when object age is 25?

A Delete

B Archive

C None

D Update metadata

💡 Hint

Check execution_table row 2 under 'Object Age' 25 and 'Action Taken'

At which step does the lifecycle rule delete the object?

A Step 1

B Step 2

C Step 4

D Exit

💡 Hint

Look at execution_table rows where 'Action Taken' is Delete

If the condition changed to age >= 40, what would happen at step 1 with object age 35?

A Delete

B None

C Archive

D Error

💡 Hint

Refer to variable_tracker and execution_table condition logic

Concept Snapshot

Lifecycle management rules:
- Define conditions (e.g., age >= 30 days)
- Check objects regularly
- If condition met, perform action (Delete, Archive)
- Helps automate storage management
- Saves cost by removing old data

Full Transcript

Lifecycle management rules in cloud storage work by defining conditions such as object age. The system checks each object regularly. If an object meets the condition, like being older than 30 days, an action such as deletion is performed. Otherwise, the object is kept. This process repeats for all objects to automate storage cleanup and cost savings.

Practice

1. What is the main purpose of lifecycle management rules in Google Cloud Storage?

easy

A. To encrypt files before uploading

B. To manually upload files to the cloud storage

C. To create backups of files every hour

D. To automatically delete or move files based on conditions like age or storage class

Solution

1. Step 1: Understand lifecycle rules function

   Lifecycle rules automate file management by applying actions like deletion or moving files based on set conditions.

2. Step 2: Compare options with lifecycle purpose

   Only To automatically delete or move files based on conditions like age or storage class describes automatic file management based on age or storage class, which matches lifecycle rules.

3. Final Answer:

   To automatically delete or move files based on conditions like age or storage class -> Option D

4. Quick Check:

   Lifecycle rules automate file management = A [OK]

Hint: Lifecycle rules automate file cleanup and movement [OK]

Common Mistakes:

• Confusing lifecycle rules with manual file upload
• Thinking lifecycle rules create backups
• Assuming lifecycle rules handle encryption

2. Which of the following is the correct syntax snippet to define a lifecycle rule that deletes objects older than 30 days in a GCP bucket JSON configuration?

easy

A. {"rules": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]}

B. {"rule": [{"action": {"type": "Remove"}, "condition": {"age": 30}}]}

C. {"rule": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]}

D. {"rule": [{"action": {"type": "Delete"}, "condition": {"days": 30}}]}

Solution

1. Step 1: Identify correct key names in lifecycle JSON

   The lifecycle configuration uses the key "rules" (plural) for the list of rules, not "rule".

2. Step 2: Check action type and condition keys

   Action type must be "Delete" and condition uses "age" in days. {"rules": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]} correctly uses "rules", "Delete", and "age".

3. Final Answer:

   {"rules": [{"action": {"type": "Delete"}, "condition": {"age": 30}}]} -> Option A

4. Quick Check:

   Correct lifecycle JSON uses "rules" and "age" = C [OK]

Hint: Use "rules" key and "age" condition for lifecycle JSON [OK]

Common Mistakes:

• Using singular "rule" instead of "rules"
• Using "Remove" instead of "Delete" for action
• Using "days" instead of "age" in condition

3. Given this lifecycle rule JSON snippet for a GCP bucket:

{"rules": [{"action": {"type": "SetStorageClass", "storageClass": "NEARLINE"}, "condition": {"age": 60}}]}

What happens to objects older than 60 days?

medium

A. They remain in the current storage class

B. They are deleted immediately

C. They are moved to the NEARLINE storage class

D. They are archived to Coldline storage

Solution

1. Step 1: Understand action type in lifecycle rule

   The action type "SetStorageClass" changes the storage class of objects matching the condition.

2. Step 2: Analyze condition and effect

   The condition "age": 60 means objects older than 60 days will be moved to the "NEARLINE" storage class.

3. Final Answer:

   They are moved to the NEARLINE storage class -> Option C

4. Quick Check:

   SetStorageClass action moves objects = A [OK]

Hint: SetStorageClass moves files; Delete removes them [OK]

Common Mistakes:

• Confusing SetStorageClass with Delete action
• Assuming objects are deleted instead of moved
• Thinking NEARLINE means Coldline storage

4. You wrote this lifecycle rule JSON to delete objects older than 90 days:

{"rule": [{"action": {"type": "Delete"}, "condition": {"age": 90}}]}

Why does this rule not work as expected?

medium

A. The key should be "rules" not "rule"

B. The action type "Delete" is invalid

C. The condition "age" must be a string, not a number

D. The age value must be less than 30

Solution

1. Step 1: Check lifecycle JSON key names

   The lifecycle configuration requires the key "rules" (plural) for the list of rules, not "rule".

2. Step 2: Validate action and condition correctness

   "Delete" is a valid action type, and "age" is correctly a number. Age can be any positive number.

3. Final Answer:

   The key should be "rules" not "rule" -> Option A

4. Quick Check:

   Correct key is "rules" = B [OK]

Hint: Use "rules" key for lifecycle rules array [OK]

Common Mistakes:

• Using singular "rule" instead of "rules"
• Thinking "Delete" is invalid action
• Believing age must be string or less than 30

5. You want to create a lifecycle rule that moves objects to Coldline storage after 30 days and deletes them after 365 days. Which JSON configuration correctly implements this?

hard

A. {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 365}}, {"action": {"type": "Delete"}, "condition": {"age": 30}}]}

B. {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 30}}, {"action": {"type": "Delete"}, "condition": {"age": 365}}]}

C. {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "NEARLINE"}, "condition": {"age": 30}}, {"action": {"type": "Delete"}, "condition": {"age": 365}}]}

D. {"rules": [{"action": {"type": "Delete"}, "condition": {"age": 30}}, {"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 365}}]}

Solution

1. Step 1: Identify correct order of lifecycle actions

   Objects should first move to Coldline after 30 days, then be deleted after 365 days. The order matters for correct lifecycle behavior.

2. Step 2: Check storage class and age conditions

   {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 30}}, {"action": {"type": "Delete"}, "condition": {"age": 365}}]} correctly sets "SetStorageClass" to "COLDLINE" at age 30, then "Delete" at age 365.

3. Final Answer:

   {"rules": [{"action": {"type": "SetStorageClass", "storageClass": "COLDLINE"}, "condition": {"age": 30}}, {"action": {"type": "Delete"}, "condition": {"age": 365}}]} -> Option B

4. Quick Check:

   Move to Coldline at 30 days, delete at 365 days = D [OK]

Hint: Order rules: move storage first, then delete later [OK]

Common Mistakes:

• Reversing delete and move actions order
• Using wrong storage class name
• Setting wrong age values for actions