Object versioning in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does enabling object versioning affect storage costs?

When you enable object versioning on a Google Cloud Storage bucket, what happens to your storage costs?

A Costs remain the same because only the latest version is billed.

B Costs increase because all versions of objects are stored and billed separately.

C Costs decrease because older versions are automatically deleted to save space.

D Costs increase only if you manually enable billing for versions.

💡 Hint

Think about how storing multiple copies affects space.

Enabling object versioning stores every version of an object separately. Each version consumes storage space and is billed, so costs increase.

❓ service_behavior

intermediate

What happens when you delete an object in a versioned bucket?

In a Google Cloud Storage bucket with object versioning enabled, what happens when you delete an object without specifying a version?

A A delete marker is added, hiding the current version but older versions remain accessible.

B All versions of the object are permanently deleted immediately.

C The latest version is permanently deleted and older versions are also deleted automatically.

D The object is moved to a trash folder for 30 days before permanent deletion.

💡 Hint

Consider how versioning preserves data after deletion.

Deleting an object without specifying a version adds a delete marker. This hides the current version but older versions remain and can be restored.

❓ Configuration

advanced

Identify the correct gsutil command to enable versioning

Which gsutil command correctly enables object versioning on a bucket named my-bucket?

A gsutil set versioning enabled gs://my-bucket

B gsutil enable versioning gs://my-bucket

C gsutil versioning set on gs://my-bucket

D gsutil bucket versioning enable gs://my-bucket

💡 Hint

Check the gsutil syntax for versioning commands.

The correct command is gsutil versioning set on gs://my-bucket. Other options are invalid commands.

❓ security

advanced

How does object versioning impact data recovery after accidental overwrite?

With object versioning enabled, what is the best way to recover data after an accidental overwrite of an object?

A Overwrite the object again with a backup copy stored outside the bucket.

B Use the trash folder to restore the deleted object within 7 days.

C Contact Google support to retrieve overwritten data.

D Restore the previous version by specifying its generation number to download or copy it.

💡 Hint

Think about how versioning stores multiple copies.

Each version has a unique generation number. You can specify this to access or restore previous versions after overwrite.

❓ Architecture

expert

Designing lifecycle rules with versioning to minimize costs

You have a bucket with object versioning enabled. You want to keep the latest version indefinitely but automatically delete noncurrent versions older than 30 days to reduce costs. Which lifecycle rule configuration achieves this?

A {"rule": [{"action": {"type": "Delete"}, "condition": {"daysSinceNoncurrentTime": 30}}]}

B {"rule": [{"action": {"type": "Delete"}, "condition": {"age": 30, "isLive": true}}]}

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

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

💡 Hint

Focus on conditions that target only noncurrent versions.

The condition daysSinceNoncurrentTime: 30 applies only to noncurrent versions, deleting those that have been noncurrent for 30 or more days. The current (live) version is unaffected and kept indefinitely.