Question

Difficulty: HardCost-Optimized Storage Tiering and Lifecycle Management

A media analytics company collects two types of data from client web applications:

1. Video rendering assets stored under the `/assets/` prefix, which average 85 MB85\text{ MB} in size. These files are accessed frequently for the first 15 days15\text{ days}, rarely accessed after that, and must be retained for 45 days45\text{ days} before being deleted.
2. User clickstream telemetry logs stored under the `/telemetry/` prefix, which average 12 KB12\text{ KB} in size. These logs are analyzed intensively for 10 days10\text{ days}, are rarely accessed afterward, and must be retained for 120 days120\text{ days} before being deleted.

Which combination of actions should the Solutions Architect implement to achieve the most cost-effective storage solution? (Select TWO.)

  1. For the `/assets/` prefix, configure an S3 Lifecycle rule to transition objects to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after 15 days15\text{ days}.Answer
  2. For the `/telemetry/` prefix, aggregate the clickstream logs into larger archive files (greater than 128 KB128\text{ KB}) before uploading them to Amazon S3, and configure an S3 Lifecycle rule to transition the archives to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after 10 days10\text{ days}.Answer
  3. C
    For the `/assets/` prefix, configure an S3 Lifecycle rule to transition objects to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after 25 days25\text{ days}, and delete them after 45 days45\text{ days}.
  4. D
    For the `/telemetry/` prefix, configure an S3 Lifecycle rule to transition the individual clickstream logs to Amazon S3 Standard-Infrequent Access (S3 Standard-IA) after 10 days10\text{ days}.
  5. E
    For the `/telemetry/` prefix, configure an S3 Lifecycle rule to transition the individual clickstream logs to Amazon S3 One Zone-Infrequent Access (S3 One Zone-IA) after 10 days10\text{ days}.

Answer

The correct architecture requires transitioning the video assets prefix to Amazon S3 Standard-IA after 15 days, and aggregating the telemetry logs into larger archive files (greater than 128 KB) before uploading them to Amazon S3 and transitioning them to Amazon S3 Standard-IA after 10 days.
The correct strategy uses S3 Standard-IA for large objects (video assets) with a transition window that satisfies the 30-day minimum storage duration (transition at day 15, delete at day 45). For small files (telemetry logs), aggregating them prior to upload avoids the 128 KB minimum capacity charge penalty when they are transitioned to S3 Standard-IA after 10 days.

Step-by-Step Solution

1
Analyze the lifecycle constraints for the video assets under the `/assets/` prefix.
The files average 85 MB85\text{ MB} (greater than the 128 KB128\text{ KB} S3 Standard-IA limit). If transitioned after 15 days15\text{ days} and deleted at 45 days45\text{ days}, the total time spent in S3 Standard-IA is 4515=30 days45 - 15 = 30\text{ days}. This matches the 30-day minimum duration requirement exactly.
Ensures that transitioning to S3 Standard-IA maximizes cost savings without incurring early transition/deletion fees.
2
Evaluate the storage tiering limitations for the telemetry logs under the `/telemetry/` prefix.
The files are very small (12 KB12\text{ KB}). Transitioning individual 12 KB12\text{ KB} files to S3 Standard-IA or S3 One Zone-IA causes them to be billed at the 128 KB128\text{ KB} minimum storage size, which increases the billing volume by more than 10 times.
Avoids the S3 Standard-IA and S3 One Zone-IA minimum storage charge size penalty.
3
Determine the optimal architectural pattern for handling high volumes of small files in S3.
Aggregating the telemetry logs into archives larger than 128 KB128\text{ KB} before upload avoids the size penalty. Once aggregated and uploaded, transitioning them after 10 days10\text{ days} to S3 Standard-IA for the remaining 110 days110\text{ days} (out of 120 days120\text{ days}) is highly cost-effective and avoids early deletion penalties.
Allows small-file data sets to benefit from lower-tier storage rates by consolidating them into larger objects, reducing both storage penalties and request fees.

Key Concept

Cost-Optimized Storage Tiering and Lifecycle Management
Rate this question