Object versioning in GCP - Mini Project: Build & Apply

Enable Object Versioning on a Google Cloud Storage Bucket

📖 Scenario: You are managing files in a Google Cloud Storage bucket for a small company. To protect against accidental deletion or overwriting of files, you want to enable object versioning on the bucket. This way, older versions of files are kept automatically.

🎯 Goal: Enable object versioning on an existing Google Cloud Storage bucket using the Google Cloud SDK (gcloud) commands and configuration.

📋 What You'll Learn

Use the exact bucket name my-company-data

Enable object versioning on the bucket

Verify the versioning status in the bucket configuration

Use gcloud commands and configuration files

💡 Why This Matters

🌍 Real World

Object versioning helps protect important files from accidental deletion or overwrites by keeping older versions automatically.

💼 Career

Cloud engineers and administrators often enable versioning on storage buckets to ensure data durability and recovery options.

1

Create a Google Cloud Storage bucket named my-company-data

Use the gcloud command to create a new storage bucket called my-company-data in the us-central1 region.

GCP

# Use gcloud to create the bucket
# Your code here

Hint

Use gcloud storage buckets create with the bucket name and location flags.

2

Set a variable for the bucket name

Create a shell variable called BUCKET_NAME and assign it the value my-company-data.

GCP

gcloud storage buckets create my-company-data --location=us-central1
# Set BUCKET_NAME variable
# Your code here

Hint

Use BUCKET_NAME=my-company-data to set the variable.

3

Enable object versioning on the bucket

Use the gcloud command to enable object versioning on the bucket using the variable BUCKET_NAME.

GCP

gcloud storage buckets create my-company-data --location=us-central1
BUCKET_NAME=my-company-data
# Enable versioning on the bucket
# Your code here

Hint

Use gcloud storage buckets update $BUCKET_NAME --versioning=enabled to enable versioning.

4

Verify that object versioning is enabled

Use the gcloud command to describe the bucket $BUCKET_NAME and confirm that versioning is enabled by checking the output for versioning.enabled: true.

GCP

gcloud storage buckets create my-company-data --location=us-central1
BUCKET_NAME=my-company-data
gcloud storage buckets update $BUCKET_NAME --versioning=enabled
# Describe the bucket to verify versioning
# Your code here

Hint

Use gcloud storage buckets describe $BUCKET_NAME and look for versioning.enabled: true in the output.

Practice

1. What is the main purpose of enabling Object Versioning in a Google Cloud Storage bucket?

easy

A. To keep multiple versions of an object to recover from accidental deletion or overwrite

B. To increase the storage capacity of the bucket automatically

C. To encrypt objects with a stronger encryption key

D. To restrict access to objects based on user roles

Solution

1. Step 1: Understand Object Versioning concept

   Object Versioning allows storing multiple versions of the same object in a bucket.

2. Step 2: Identify the main benefit

   This helps recover previous versions if an object is deleted or overwritten by mistake.

3. Final Answer:

   To keep multiple versions of an object to recover from accidental deletion or overwrite -> Option A

4. Quick Check:

   Object Versioning = Data recovery [OK]

Hint: Versioning means saving old copies to recover later [OK]

Common Mistakes:

• Confusing versioning with encryption
• Thinking versioning increases storage automatically
• Assuming versioning controls access permissions

2. Which of the following commands correctly enables Object Versioning on a Google Cloud Storage bucket named my-bucket?

easy

A. gsutil versioning set on my-bucket

B. gsutil versioning enable gs://my-bucket

C. gsutil versioning set enabled gs://my-bucket

D. gsutil versioning set on gs://my-bucket

Solution

1. Step 1: Recall gsutil syntax for enabling versioning

   The correct command is gsutil versioning set on gs://bucket-name.

2. Step 2: Match the command to the bucket name

   gsutil versioning set on gs://my-bucket matches the correct syntax and bucket name format.

3. Final Answer:

   gsutil versioning set on gs://my-bucket -> Option D

4. Quick Check:

   Enable versioning = gsutil versioning set on [OK]

Hint: Use 'gsutil versioning set on gs://bucket' to enable [OK]

Common Mistakes:

• Omitting 'gs://' prefix
• Using 'enable' instead of 'set on'
• Adding extra words like 'enabled'

3. Consider a bucket with Object Versioning enabled. If you upload a file named report.txt three times with different content, how many versions of report.txt will exist in the bucket?

medium

A. 3

B. 1

C. 2

D. 4

Solution

1. Step 1: Understand versioning behavior on multiple uploads

   Each upload creates a new version if versioning is enabled.

2. Step 2: Count versions after three uploads

   Uploading three times creates three distinct versions of the same object.

3. Final Answer:

   3 -> Option A

4. Quick Check:

   Uploads = Versions when versioning on [OK]

Hint: Each upload creates a new version if versioning is enabled [OK]

Common Mistakes:

• Assuming only one version exists
• Counting versions as uploads minus one
• Confusing versions with copies

4. You enabled Object Versioning on a bucket but notice that old versions are not visible when listing objects. What is the most likely cause?

medium

A. Old versions are automatically deleted after 24 hours

B. Versioning was not actually enabled on the bucket

C. You used gsutil ls which only shows live versions by default

D. You need to enable versioning on each object separately

Solution

1. Step 1: Understand default listing behavior

   By default, gsutil ls shows only the current live versions, not older ones.

2. Step 2: How to list all versions

   Use gsutil ls -a to see all versions including old ones.

3. Final Answer:

   You used gsutil ls which only shows live versions by default -> Option C

4. Quick Check:

   Default list hides old versions [OK]

Hint: Use 'gsutil ls -a' to see all versions [OK]

Common Mistakes:

• Assuming versioning not enabled without checking
• Believing old versions auto-delete quickly
• Thinking versioning applies per object

5. You want to keep only the latest 5 versions of objects in a bucket with Object Versioning enabled to save storage costs. Which approach should you use?

hard

A. Disable Object Versioning and re-enable it every month

B. Set a lifecycle rule to delete noncurrent versions older than a certain age

C. Manually delete old versions using the Cloud Console every week

D. Rename objects to avoid creating new versions

Solution

1. Step 1: Understand lifecycle management for versioned objects

   Lifecycle rules can automatically delete old versions based on age or count.

2. Step 2: Choose the best automated approach

   Setting a lifecycle rule to delete noncurrent versions older than a set time saves costs without manual work.

3. Final Answer:

   Set a lifecycle rule to delete noncurrent versions older than a certain age -> Option B

4. Quick Check:

   Use lifecycle rules to manage old versions [OK]

Hint: Use lifecycle rules to auto-delete old versions [OK]

Common Mistakes:

• Relying on manual deletion which is error-prone
• Disabling versioning loses all version history
• Renaming objects does not control version count