A smart manufacturing company collects and stores operational data in a single Amazon S3 b… — AWS Certified Solutions Architect - Associate

A smart manufacturing company collects and stores operational data in a single Amazon S3 bucket. The data consists of two categories:

* IoT Sensor Telemetry: Average file size is $8\text{ KB}$ . These files are generated continuously and analyzed in real-time. They are rarely accessed after $10\text{ days}$ but must be retained for a total of $25\text{ days}$ for compliance audits, after which they can be deleted.
* Machinery Firmware Images: Average file size is $20\text{ MB}$ . These files are accessed frequently during the first $30\text{ days}$ after release and rarely thereafter. They must be retained for $365\text{ days}$ for rollback purposes, after which they can be deleted.

Which lifecycle configuration is the most cost-effective to meet these requirements?

For telemetry data, create a lifecycle rule to expire objects after $25\text{ days}$ . For firmware images, create a lifecycle rule to transition objects to S3 Standard-Infrequent Access (S3 Standard-IA) after $30\text{ days}$ and expire them after $365\text{ days}$ .Answer
B
For telemetry data, create a lifecycle rule to transition objects to S3 Standard-IA after $10\text{ days}$ and expire them after $25\text{ days}$ . For firmware images, create a lifecycle rule to transition objects to S3 Standard-IA after $30\text{ days}$ and expire them after $365\text{ days}$ .
C
For telemetry data, create a lifecycle rule to expire objects after $25\text{ days}$ . For firmware images, create a lifecycle rule to transition objects to S3 Standard-IA after $10\text{ days}$ and expire them after $365\text{ days}$ .
D
For telemetry data, create a lifecycle rule to transition objects to S3 Standard-IA after $20\text{ days}$ and expire them after $25\text{ days}$ . For firmware images, create a lifecycle rule to transition objects to S3 Standard-IA after $30\text{ days}$ and expire them after $365\text{ days}$ .

Answer

For telemetry data, configure a lifecycle rule to expire objects after

25\text{ days}

without transitioning them. For firmware images, configure a lifecycle rule to transition them to S3 Standard-IA after

30\text{ days}

and expire them after

365\text{ days}

The correct configuration leaves telemetry files in S3 Standard for the duration of their lifecycle (

25\text{ days}

) and expires them directly. This avoids both the

128\text{ KB}

minimum billing size penalty (since their actual size is

8\text{ KB}

) and the

30\text{-day}

minimum storage duration penalty of S3 Standard-IA. The firmware images are large (

20\text{ MB}

) and reside in S3 Standard-IA for

335\text{ days}

after the initial

30\text{ days}

of frequent access, maximizing storage savings with zero penalties.

Step-by-Step Solution

Analyze the telemetry data properties and constraints.

The telemetry files are very small (

8\text{ KB}

) and are kept for only

25\text{ days}

before deletion.

We must evaluate if transitioning them to S3 Standard-IA is cost-effective. Since the files are less than the

128\text{ KB}

minimum storage size limit of S3 Standard-IA and are kept in that tier for only

15\text{ days}

(violating the

30\text{-day}

minimum storage duration), they should remain in S3 Standard.

Analyze the firmware images properties and constraints.

The firmware files are large (

20\text{ MB}

) and are kept for

365\text{ days}

. They are frequently accessed only during the first

30\text{ days}

of release.

Transitioning them to S3 Standard-IA after

30\text{ days}

is highly cost-effective because the file size exceeds

128\text{ KB}

, and the remaining storage duration (

335\text{ days}

) comfortably exceeds the

30\text{-day}

minimum requirement.

Combine the rules into a single lifecycle configuration.

Prefix-based rules: `telemetry/` expires after

25\text{ days}

; `firmware/` transitions to S3 Standard-IA after

30\text{ days}

and expires after

365\text{ days}

Using prefix-based rules allows separate lifecycle paths for different types of data in the same bucket.

Key Concept

S3 Lifecycle Management Cost Constraints

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics