Lifecycle management rules in GCP - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are lifecycle management rules in Google Cloud Storage?

Lifecycle management rules automatically manage objects in a storage bucket based on conditions like age or storage class, helping save costs and organize data.

beginner

Name two common actions you can set in lifecycle management rules.

You can set actions like Delete to remove objects or Set Storage Class to change how data is stored (e.g., from standard to coldline storage).

beginner

Why use lifecycle management rules instead of manual cleanup?

They save time by automating data cleanup and storage optimization, reduce human errors, and help control costs by moving or deleting data automatically.

intermediate

What condition can trigger a lifecycle rule in GCP Storage?

Conditions include object age (e.g., older than 30 days), creation date, or storage class, which help decide when to apply actions like deletion or storage class change.

intermediate

How do lifecycle rules help with data compliance?

They ensure data is retained or deleted according to policies automatically, helping meet legal or company rules without manual tracking.

Which action is NOT supported by GCP lifecycle management rules?

A Encrypt objects

B Change storage class

C Delete objects

D Abort incomplete uploads

Lifecycle rules do not encrypt objects; encryption is managed separately.

What condition can trigger a lifecycle rule in GCP Storage?

A User access frequency

B File size

C Object age

D Network location

Object age is a common condition; access frequency and network location are not used.

What is a benefit of using lifecycle management rules?

A Automated data cleanup

B Increased storage capacity

C Faster network speed

D Manual data backup

Lifecycle rules automate cleanup and storage optimization.

Which storage class can objects be moved to using lifecycle rules?

A Standard

B Nearline

C Coldline

D All of the above

Lifecycle rules can move objects between Standard, Nearline, Coldline, and Archive classes.

How do lifecycle rules help with cost management?

A By increasing storage speed

B By automatically deleting or moving data to cheaper storage

C By charging more for data access

D By backing up data more frequently

They reduce costs by moving data to cheaper storage or deleting it when no longer needed.

Explain how lifecycle management rules work in Google Cloud Storage and why they are useful.

Think about how rules help manage data without manual work.

Describe some common conditions and actions you can set in lifecycle management rules.

Focus on what triggers the rule and what happens after.

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