S3 versioning in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable versioning on an S3 bucket using AWS CLI.

AWS

aws s3api put-bucket-versioning --bucket my-bucket --versioning-configuration Status=[1]

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

AActive

BDisabled

CSuspended

DEnabled

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Disabled' instead of 'Enabled'

Using 'Suspended' which pauses versioning but does not enable it

To enable versioning on an S3 bucket, the Status must be set to Enabled.

2fill in blank

medium

Complete the AWS CLI command to check the versioning status of a bucket.

AWS

aws s3api get-bucket-versioning --bucket [1]

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

Amy-bucket

Bexample-bucket

Ctest-bucket

Dbucket-name

Attempts:

3 left

💡 Hint

Common Mistakes

Using a bucket name that was not created or does not exist

Leaving the bucket name blank

The bucket name must be specified to check its versioning status. Here, my-bucket is used as the example bucket.

3fill in blank

hard

Fix the error in the JSON configuration to enable versioning in a CloudFormation template.

AWS

"VersioningConfiguration": {"Status": "[1]"}

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

ASuspended

BActive

CEnabled

DDisabled

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Active' which is not a valid status

Using 'Suspended' which pauses versioning

The correct value to enable versioning in CloudFormation is Enabled. Other values either disable or suspend versioning.

4fill in blank

hard

Fill both blanks to create a Python boto3 snippet that enables versioning on a bucket.

AWS

s3 = boto3.client('s3')
s3.put_bucket_versioning(Bucket='my-bucket', VersioningConfiguration={'[1]': '[2]'})

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

AStatus

BVersioning

CEnabled

DActive

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Versioning' as the key instead of 'Status'

Using 'Active' instead of 'Enabled' as the value

The key must be Status and the value to enable versioning is Enabled.

5fill in blank

hard

Fill all three blanks to write a Terraform resource block that enables versioning on an S3 bucket.

AWS

resource "aws_s3_bucket" "my_bucket" {
  bucket = "my-bucket"

  versioning {
    [1] = [2]
    [3] = false
  }
}

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

Aenabled

Btrue

Cmfa_delete

Dversioning

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'versioning' as an attribute inside the versioning block

Setting 'enabled' to false

Confusing 'mfa_delete' with 'enabled'

In Terraform, to enable versioning you set enabled = true. The mfa_delete option controls multi-factor authentication delete and is often set to false.

Practice

1. What is the main purpose of enabling S3 versioning on a bucket?

easy

A. To keep multiple copies of files automatically for recovery and tracking

B. To increase the storage capacity of the bucket

C. To encrypt files stored in the bucket

D. To restrict access to the bucket

Solution

1. Step 1: Understand what S3 versioning does

   S3 versioning keeps multiple versions of the same file automatically.

2. Step 2: Identify the main benefit

   This helps recover from mistakes and track changes over time.

3. Final Answer:

   To keep multiple copies of files automatically for recovery and tracking -> Option A

4. Quick Check:

   S3 versioning = multiple copies for recovery [OK]

Hint: Versioning means saving file copies automatically [OK]

Common Mistakes:

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

2. Which of the following is the correct way to enable versioning in an AWS S3 bucket configuration?

easy

A. versioning = true

B. versioning { enabled = true }

C. enable_versioning = yes

D. versioning: active

Solution

1. Step 1: Recall the syntax for enabling versioning

   Versioning is enabled by setting a block with enabled = true.

2. Step 2: Match the correct syntax

   Only versioning { enabled = true } matches the correct structure.

3. Final Answer:

   versioning { enabled = true } -> Option B

4. Quick Check:

   Enable versioning with block and enabled=true [OK]

Hint: Look for block with enabled = true syntax [OK]

Common Mistakes:

• Using assignment without block braces
• Using yes/no instead of true/false
• Using colon instead of equals sign

3. Given the following Terraform snippet for an S3 bucket, what will be the versioning state of the bucket after deployment?

resource "aws_s3_bucket" "example" {
  bucket = "my-versioned-bucket"

  versioning {
    enabled = false
  }
}

medium

A. Versioning will be enabled and keep all versions

B. Versioning will be enabled but only for new files

C. Versioning will be suspended, no new versions saved

D. Versioning will be enabled with MFA delete

Solution

1. Step 1: Check the versioning block value

   The snippet sets enabled = false, which means versioning is suspended.

2. Step 2: Understand suspended versioning behavior

   Suspended versioning means no new versions are saved, but existing versions remain.

3. Final Answer:

   Versioning will be suspended, no new versions saved -> Option C

4. Quick Check:

   enabled = false means versioning suspended [OK]

Hint: enabled = false means versioning suspended, not enabled [OK]

Common Mistakes:

• Assuming false means versioning enabled
• Confusing suspended with disabled (deleted)
• Thinking MFA delete is enabled by default

4. You wrote this Terraform code to enable versioning but it does not work as expected:

resource "aws_s3_bucket" "mybucket" {
  bucket = "mybucket"
  versioning = {
    enabled = true
  }
}

What is the error and how to fix it?

medium

A. enabled must be a string "true", not boolean true

B. Versioning cannot be enabled during bucket creation

C. Bucket name must be unique globally

D. versioning should be a block, not an assignment; remove '='

Solution

1. Step 1: Identify syntax error in versioning block

   The code uses versioning = { ... } which is incorrect syntax for a block.

2. Step 2: Correct syntax for versioning block

   Versioning must be declared as a block without '=' like versioning { enabled = true }.

3. Final Answer:

   versioning should be a block, not an assignment; remove '=' -> Option D

4. Quick Check:

   Blocks use braces without '=' [OK]

Hint: Blocks use braces without '=' sign [OK]

Common Mistakes:

• Using '=' with blocks
• Using string instead of boolean for enabled
• Ignoring bucket name uniqueness errors

5. You want to protect important files in your S3 bucket from accidental deletion but still allow updates. How does enabling versioning help achieve this, and what additional step should you take for stronger protection?

hard

A. Versioning keeps old file copies; enable MFA delete to require extra confirmation for deletions

B. Versioning encrypts files; enable bucket policies to restrict access

C. Versioning compresses files; enable lifecycle rules to archive old versions

D. Versioning increases storage; enable logging to track deletions

Solution

1. Step 1: Understand versioning's role in protection

   Versioning keeps all versions of files, so deleted files can be recovered.

2. Step 2: Identify additional protection for deletions

   Enabling MFA delete adds a requirement for multi-factor authentication to delete versions, preventing accidental or unauthorized deletions.

3. Final Answer:

   Versioning keeps old file copies; enable MFA delete to require extra confirmation for deletions -> Option A

4. Quick Check:

   Versioning + MFA delete = strong deletion protection [OK]

Hint: Use MFA delete with versioning for deletion safety [OK]

Common Mistakes:

• Confusing encryption with versioning
• Thinking lifecycle rules prevent deletions
• Assuming logging stops accidental deletes