Bitzu

SAA-C03 ยท Cost-optimized storage and data transfer

S3 Lifecycle and Requester Pays

Lifecycle transition and expiration rules, cleaning up old versions and incomplete multipart uploads, and Requester Pays buckets for shared datasets.

Key points

  • Lifecycle: filter by prefix, tags, size.
  • Transition: downward only (Standard, IA, Glacier, Deep Archive); <128 KB skipped.
  • Expiration: deletes current objects (versioned: delete marker only).
  • NoncurrentVersionExpiration/Transition: old versions (NewerNoncurrentVersions keeps N).
  • AbortIncompleteMultipartUpload: not with tag filters.
  • Requester Pays: requester pays requests and downloads, owner storage; no anonymous; --request-payer.

Source: https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html

Practice questions

Single choice

Which lifecycle action removes the leftover parts of multipart uploads that were never completed?

  1. Expiration
  2. NoncurrentVersionExpiration
  3. ExpiredObjectDeleteMarker
  4. AbortIncompleteMultipartUpload
Show answer

Answer: D. AbortIncompleteMultipartUpload

AbortIncompleteMultipartUpload stops uploads that are not finished within the set number of days, so their stored parts stop costing money. Expiration and NoncurrentVersionExpiration act on objects and versions, not on incomplete uploads.

Select all that apply

A versioning-enabled bucket keeps growing because every overwrite leaves an old version behind. Which lifecycle settings directly reduce that cost?

  1. NoncurrentVersionExpiration after a number of days
  2. NewerNoncurrentVersions to keep only the latest few
  3. An Expiration action on the current version
  4. NoncurrentVersionTransition to a colder class
  5. Suspending versioning on the bucket
Show answer

Answer: A. NoncurrentVersionExpiration after a number of days, B. NewerNoncurrentVersions to keep only the latest few, D. NoncurrentVersionTransition to a colder class

NoncurrentVersionExpiration permanently deletes old versions after a set number of days, and NewerNoncurrentVersions lets you keep the latest few. NoncurrentVersionTransition moves old versions to a cheaper class. Expiration only adds a delete marker to the current version, and suspending versioning keeps the existing old versions.

True or false

In a versioning-enabled bucket, a lifecycle Expiration action permanently deletes the current version of each matching object.

Show answer

Answer: False

False. In a versioned bucket Expiration adds a delete marker, and the former current version is kept as a noncurrent version that still costs money. To really delete it you need NoncurrentVersionExpiration.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More SAA-C03 topics in this module