Object versioning in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable versioning on a Google Cloud Storage bucket.

GCP

gsutil versioning set [1] gs://my-bucket

Drag options to blanks, or click blank then click option'

Aenabled

Bon

Cactivate

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'enabled' or 'true' instead of 'on'

Using 'activate' which is not a valid option

To enable versioning on a GCS bucket, the command uses versioning set on.

2fill in blank

medium

Complete the command to list all versions of objects in a bucket.

GCP

gsutil ls -[1] gs://my-bucket

Drag options to blanks, or click blank then click option'

Ar

Ba

Cl

Dv

Attempts:

3 left

💡 Hint

Common Mistakes

Using '-a' which lists all buckets, not versions

Using '-r' which lists recursively but not versions

The -v flag lists all versions of objects in the bucket.

3fill in blank

hard

Fix the error in the command to disable versioning on a bucket.

GCP

gsutil versioning set [1] gs://my-bucket

Drag options to blanks, or click blank then click option'

Aoff

Bdisabled

Cdisable

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disable' or 'disabled' instead of 'off'

Using 'false' which is invalid

The correct keyword to disable versioning is off.

4fill in blank

hard

Fill both blanks to create a lifecycle rule that deletes noncurrent object versions when there are 30 newer versions.

GCP

{
  "rule": {
    "action": {"type": "[1]"},
    "condition": {"numNewerVersions": [2]
  }
}

Drag options to blanks, or click blank then click option'

ADelete

B30

CArchive

D7

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Archive' instead of 'Delete' for action

Using 7 instead of 30 for the number of newer versions

The action to remove old versions is Delete, and the condition specifies to delete when there are 30 newer versions.

5fill in blank

hard

Fill all three blanks to create a lifecycle rule that deletes object versions older than 365 days.

GCP

{
  "rule": {
    "action": {"type": "[1]"},
    "condition": {
      "age": [2],
      "isLive": [3]
    }
  }
}

Drag options to blanks, or click blank then click option'

ADelete

B365

Cfalse

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Setting isLive to true which targets current versions

Using age less than 365 days

Using 'Archive' instead of 'Delete' for action

The action is Delete. The age condition is 365 days. isLive is false to target noncurrent versions.

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