S3 Advanced: Lifecycle Rules u0026 Versioning Quiz Quiz

Explore the essentials of S3 bucket lifecycle rules and versioning with this focused quiz. Understand how to manage object transitions, expiration, version deletion, and key settings for effective storage optimization and data protection.

1. Lifecycle Rules Application

   Which option best describes when a lifecycle rule applies to an object in a storage bucket?

   1. When the object's key matches the rule's filter or prefix
   2. Only when the object is uploaded manually
   3. Only for objects larger than 1GB
   4. Whenever any object is read from the bucket

   Explanation: Lifecycle rules act based on filters or prefixes set for objects. If an object’s key matches this filter, the rule will apply. Manual uploads do not directly affect rule application. Reads and object size are not criteria for applying lifecycle rules.

2. Effect of Enabling Versioning

   What is the primary effect of enabling versioning on a bucket?

   1. Objects are automatically archived to cold storage
   2. Object names must be unique across all buckets
   3. Write access is disabled for non-admin users
   4. Multiple versions of each object can be stored

   Explanation: Enabling versioning allows storing and managing several versions of the same object. It does not trigger automatic archiving nor require global uniqueness for object names. Access controls are not changed by enabling versioning.

3. Noncurrent Version Expiration

   If a lifecycle rule specifies 'expire noncurrent versions after 30 days,' what happens to these versions?

   1. All objects are transitioned to another storage class after 30 days
   2. Noncurrent versions are deleted 30 days after they become noncurrent
   3. Objects larger than 30MB are deleted
   4. Current versions of all objects are deleted after 30 days

   Explanation: Noncurrent version expiration rules remove older object versions after they have been noncurrent for the specified period. The current version is not removed, and transitions are a separate lifecycle action. Deletion does not depend on object size.

4. Transition Actions in Lifecycle Policy

   Which lifecycle policy action moves objects to a different storage class after a specific number of days?

   1. Replication
   2. Retention
   3. Restoration
   4. Transition

   Explanation: A transition action automatically moves objects to another storage class based on the conditions set. Retention refers to keeping objects unchanged, replication copies objects elsewhere, and restoration is about restoring objects from archive.

5. Deleting a Marker Object

   What does deleting a delete marker in a versioned bucket do?

   1. It makes the most recent object version accessible again
   2. It transitions all objects to cold storage
   3. It turns off versioning for the bucket
   4. It removes all versions permanently

   Explanation: Deleting a delete marker exposes the previous object version, making it accessible as the current version. All versions are not removed, and versioning status remains unchanged. Transitioning objects to cold storage is unrelated to delete markers.

6. Lifecycle Rule Scope

   If no prefix or filter is set in a lifecycle rule, to which objects does the rule apply?

   1. All objects in the bucket
   2. No objects in the bucket
   3. Only objects with a specific tag
   4. Only objects uploaded in the last 24 hours

   Explanation: A rule without filters or prefixes applies to every object in the bucket by default. Tag-based or recency-based targeting requires explicit configuration. With no filter, the scope is the entire bucket, not a subset.

7. Current vs. Noncurrent Object Version

   After uploading a new version of an object in a versioned bucket, what is the status of the previous version?

   1. It is deleted automatically
   2. It gets moved to another bucket
   3. It turns into a public object
   4. It becomes a noncurrent version

   Explanation: Uploading a new version creates a noncurrent (previous) version in the bucket. Versions are not automatically deleted or moved. Changing to a public object does not result from versioning actions.

8. Lifecycle Rule for Transition to Archive Class

   A lifecycle rule transitions objects to an archive class after 60 days. Which scenario best fits this rule?

   1. Objects larger than 60MB are archived
   2. Objects not modified for 60 days are moved to archive storage
   3. Only encrypted objects are archived after 60 days
   4. All objects are deleted after 60 days

   Explanation: Objects that remain unmodified for the specified time can be transitioned to archive class via a lifecycle rule. The rule is about age, not size, and does not delete or depend on object encryption.

9. Suspending Versioning Impact

   What happens if versioning on a bucket is suspended after being enabled?

   1. All existing versions are deleted
   2. New uploads do not get version IDs but existing versions remain
   3. Objects cannot be uploaded to the bucket
   4. Previous versions become public

   Explanation: When versioning is suspended, new objects no longer receive unique version IDs, but all prior versions are retained. Suspension does not remove versions, prevent uploads, or impact object permissions.

10. Lifecycle Rule for Deleting Expired Objects

    Which lifecycle configuration removes an object after a fixed period, such as 365 days?

    1. Replication
    2. Retention
    3. Transition
    4. Expiration

    Explanation: The expiration action in a lifecycle rule deletes objects after they reach the age set in the policy. Replication copies objects, transition moves them to other classes, and retention prevents deletion.