Lifecycle management rules in GCP - Mini Project: Build & Apply

GCP Storage Bucket Lifecycle Management Rules

📖 Scenario: You are managing a Google Cloud Storage bucket that stores logs and backups. To save costs and keep the bucket organized, you want to automatically delete old files and move some files to cheaper storage classes after a certain time.

🎯 Goal: Create a lifecycle management rule for a GCP Storage bucket that deletes objects older than 30 days and changes the storage class to Nearline for objects older than 7 days.

📋 What You'll Learn

Create a dictionary called lifecycle_rule with a rule to delete objects older than 30 days

Add a second rule to change storage class to NEARLINE for objects older than 7 days

Combine these rules into a lifecycle configuration dictionary called lifecycle_config

Add the lifecycle configuration to a bucket configuration dictionary called bucket_config

💡 Why This Matters

🌍 Real World

Lifecycle management rules help automate storage cost savings and data retention policies by automatically deleting or moving files based on age or other conditions.

💼 Career

Cloud engineers and administrators use lifecycle rules to optimize storage costs and maintain compliance with data retention requirements.

1

Create the first lifecycle rule to delete old objects

Create a dictionary called lifecycle_rule with a key action set to {'type': 'Delete'} and a key condition set to {'age': 30} to delete objects older than 30 days.

GCP

# Create lifecycle_rule dictionary with delete action and age condition
# Your code here

Hint

Use a dictionary with keys action and condition. The action type should be Delete. The condition should specify age as 30.

2

Create the second lifecycle rule to change storage class to NEARLINE

Create a dictionary called storage_class_rule with action set to {'type': 'SetStorageClass', 'storageClass': 'NEARLINE'} and condition set to {'age': 7} to change storage class for objects older than 7 days.

GCP

lifecycle_rule = {
    'action': {'type': 'Delete'},
    'condition': {'age': 30}
}
# Create storage_class_rule dictionary with SetStorageClass action and age condition
# Your code here

Hint

Use a dictionary with action key having type as SetStorageClass and storageClass as NEARLINE. The condition should have age 7.

3

Combine both rules into a lifecycle configuration

Create a dictionary called lifecycle_config with a key rule set to a list containing lifecycle_rule and storage_class_rule.

GCP

lifecycle_rule = {
    'action': {'type': 'Delete'},
    'condition': {'age': 30}
}
storage_class_rule = {
    'action': {'type': 'SetStorageClass', 'storageClass': 'NEARLINE'},
    'condition': {'age': 7}
}
# Create lifecycle_config dictionary with rule list
# Your code here

Hint

Put both rules inside a list assigned to the rule key in lifecycle_config.

4

Add lifecycle configuration to the bucket configuration

Create a dictionary called bucket_config with a key lifecycle set to lifecycle_config.

GCP

lifecycle_rule = {
    'action': {'type': 'Delete'},
    'condition': {'age': 30}
}
storage_class_rule = {
    'action': {'type': 'SetStorageClass', 'storageClass': 'NEARLINE'},
    'condition': {'age': 7}
}
lifecycle_config = {
    'rule': [lifecycle_rule, storage_class_rule]
}
# Create bucket_config dictionary with lifecycle key
# Your code here

Hint

Assign lifecycle_config to the lifecycle key in bucket_config.

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