# Storage Tiering

Storage tiering places data in storage classes with different costs and access characteristics to match how frequently and how quickly the data must be retrieved.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/storage-tiering

> Storage tiering balances storage cost against access latency, retrieval charges, and retention requirements. Cloud platforms implement it through explicit storage-class selection, lifecycle policies, or automatic movement based on access patterns, helping engineers avoid paying premium storage rates for rarely used data.

Practice exams covering Storage Tiering: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Storage Tiering

Effective storage tiering combines workload-aware placement, appropriate automation, total-cost analysis, and tested retrieval and retention behavior.

1. **Workload-aligned placement**: Select storage tiers using access frequency, retrieval deadlines, and retention requirements. Keep operational data readily accessible and reserve delayed-retrieval tiers for workloads that can tolerate waiting.
2. **Policy-driven transitions**: Lifecycle policies move eligible data between supported tiers using defined conditions. Scope rules carefully so that a policy intended for old logs does not also archive active application assets.
3. **Age-based versus access-based automation**: Age-based rules follow a schedule, while access-based tiering responds to observed usage. A recently read object can still transition under an age-based rule.
4. **Total-cost evaluation**: Compare storage savings with transition, retrieval, monitoring, and minimum-duration charges. Model realistic object sizes and retrieval volumes before applying a policy broadly.
5. **Retrieval readiness**: Confirm whether a tier supports immediate reads or requires restoration. Include restoration time and procedures in recovery plans and application expectations.
6. **Separate transition and retention decisions**: Moving data to a cheaper class preserves it; expiration removes it according to the service's deletion semantics. Coordinate lifecycle policies with versioning, legal holds, and mandatory retention controls.

## Cloud services for Storage Tiering

Amazon S3 applies tiering to objects, Amazon EFS applies it to files, and AWS Backup applies lifecycle controls to supported recovery points. These services address different storage workloads rather than forming a required pipeline. An application might store shared files in EFS, export logs to S3 with age-based transitions, and protect supported resources through AWS Backup. Configure policies independently for each dataset: operational files may need rapid access, historical logs may tolerate archival retrieval, and backups must remain usable within recovery and retention requirements. Validate costs and restoration behavior separately for each service.

- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: S3 Lifecycle can transition eligible objects to supported storage classes and expire data using configured rules. S3 Intelligent-Tiering provides access-based automatic tiering for changing or unknown access patterns, with optional archive tiers that have different retrieval behavior.
- **[AWS Backup](https://blowstack.com/tools/cloud-services-hub/aws-backup)**: AWS Backup lifecycle settings can transition supported backup types to cold storage and delete recovery points after their configured retention period. Cold-storage eligibility depends on the protected resource type, and minimum retention requirements and restore costs must be included in the design.

## Storage Tiering exam questions

Real practice exam questions on Storage Tiering, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

An engineering company stores active project files and completed project files in the same Amazon S3 bucket. Completed files have a project-status=closed object tag and must be retained for seven years. They are rarely accessed, and a restore process taking several hours is acceptable. Active files must remain in their current storage class. Which solution automatically reduces storage costs for completed files without deleting them or changing the application?

**Correct answer:** Configure an S3 Lifecycle rule filtered by the project-status=closed tag to transition eligible objects to S3 Glacier Flexible Retrieval.

**Explanation:** A tag-filtered lifecycle transition moves only the completed files to a lower-cost archive storage class. The files remain stored, and the allowed restore delay makes S3 Glacier Flexible Retrieval suitable.

### Question 2 (MLA-C02 (beta))

**Question:**

An ML team stores 200 TB of training-data objects in Amazon S3. Each object is at least 64 MB. Different experiments repeatedly access different subsets of the data, and objects that have not been read for several months can suddenly become active again. Object age does not reliably predict access frequency.

The team wants to automatically reduce storage costs for inactive objects while keeping every object accessible with millisecond latency without a restore operation. The solution must not incur per-GB retrieval charges and must retain resilience to an Availability Zone failure.

Which storage configuration meets these requirements?

**Correct answer:** Store the objects in S3 Intelligent-Tiering and leave the optional Archive Access and Deep Archive Access tiers disabled.

**Explanation:** S3 Intelligent-Tiering automatically moves eligible objects among its Frequent Access, Infrequent Access, and Archive Instant Access tiers based on access patterns. These tiers provide millisecond access without restore operations or per-GB retrieval charges and store data across multiple Availability Zones. A per-object monitoring and automation fee applies.

### Question 3 (SAP-C03)

**Question:**

A company aggregates application logs from 90 AWS accounts through CloudWatch Logs cross-account subscriptions and Amazon Data Firehose into an Amazon S3 bucket in a central logging account. Firehose writes compressed objects between 16 MB and 64 MB in size to S3 Standard. The company retains these objects for 5 years.

Investigators frequently read recent logs. Historical datasets can remain unread for several months, but an investigation can make any historical dataset heavily accessed again without advance notice. Every object must remain available through millisecond-latency GET requests without a restore operation. The company wants storage placement to adapt automatically as access patterns change. It must not incur S3 per-GB data retrieval charges when investigators read historical datasets.

Which configuration meets these requirements with the LEAST operational overhead?

**Correct answer:** Keep Firehose delivery to S3 Standard. Configure an S3 Lifecycle rule covering existing and future archive objects to transition them to S3 Intelligent-Tiering at the earliest eligible object age. Leave both optional asynchronous archive tiers disabled.

**Explanation:** Lifecycle transitions place both existing objects and newly delivered objects into S3 Intelligent-Tiering without requiring Firehose to select that storage class directly. Intelligent-Tiering automatically moves eligible objects among Frequent Access, Infrequent Access, and Archive Instant Access according to access patterns, with millisecond access and no per-GB retrieval charges. Access to an object in an infrequent tier returns it to Frequent Access. Disabling the optional Archive Access and Deep Archive Access tiers avoids restore requirements, and the stated object sizes qualify for automatic tiering.

### Question 4 (SOA-C03)

**Question:**

A company uses an AWS DataSync task to copy selected historical datasets from an Amazon S3 bucket to an S3 Standard bucket in another AWS Region for analysis. The source datasets were transitioned to S3 Glacier Deep Archive. The task cannot read these objects. The company can allow 72 hours for retrieval before starting the transfer and wants to minimize retrieval charges. The source objects must retain their archive storage class, and temporary restored copies must remain available for 7 days.

Which solution should a CloudOps engineer implement?

**Correct answer:** Request Bulk retrieval for the selected source objects with a 7-day restoration period. Wait for restoration to complete, and then run the DataSync task.

**Explanation:** S3 Glacier Deep Archive objects must be restored before DataSync can read them. Bulk retrieval is the lowest-cost retrieval option and typically completes within 48 hours, fitting the allowed retrieval window. A 7-day restoration period makes temporary copies available for transfer without changing the source objects' archive storage class.

### Question 5 (DOP-C02)

**Question:**

A company stores compressed application log bundles in an Amazon S3 general purpose bucket for 2 years. Each object is between 32 MiB and 128 MiB. Investigators frequently read new bundles, but access usually declines after several weeks. An investigation can make any older bundle frequently accessed again for several days, so object age does not reliably predict access frequency.

A DevOps engineer must reduce storage costs by automatically moving bundles between access tiers as usage changes. Every bundle must remain available through ordinary GET requests with millisecond access, without a restore operation. The solution must not incur per-GB data retrieval charges, excluding request and data transfer charges. The engineer must not implement custom access-tracking automation.

Which configuration meets these requirements?

**Correct answer:** Store the bundles in S3 Intelligent-Tiering. Keep the optional Archive Access and Deep Archive Access tiers disabled, and configure expiration separately for the required retention period.

**Explanation:** S3 Intelligent-Tiering automatically moves eligible objects among its Frequent Access, Infrequent Access, and Archive Instant Access tiers according to access patterns. These tiers provide millisecond access without restore operations or data retrieval charges. Accessing an object in an infrequent tier returns it to the Frequent Access tier. The objects exceed the minimum size for automatic tiering, and disabling the optional asynchronous archive tiers preserves immediate access.

### Question 6 (DEA-C01)

**Question:**

A company uses an S3 Lifecycle rule to transition objects tagged archive=true from S3 Standard to S3 Glacier Flexible Retrieval 90 days after creation. The bucket is unversioned, and all objects are larger than 10 MB.

A change to an analytics pipeline requires a selected set of already archived objects to become permanently available in S3 Standard under their existing object keys. These objects must not be archived again. A one-time asynchronous restore is acceptable, but subsequent access must not depend on temporary restored copies. All other objects must continue to follow the existing archival policy.

Which workflow meets these requirements?

**Correct answer:** Restore the selected objects, wait for restoration to complete, and copy each object to its existing key with S3 Standard as the storage class. During the copy, replace the tags to remove archive=true while preserving any unrelated tags.

**Explanation:** Restoration makes the archived data temporarily accessible so it can be copied. Copying the restored data to the same keys with S3 Standard creates permanent S3 Standard replacements. Removing the archival tag prevents the existing Lifecycle rule from archiving those replacements again, while leaving other objects unaffected.

### Question 7 (DVA-C02)

**Question:**

A document-processing application stores millions of files, each between 5 MB and 50 MB, in Amazon S3. Files are retained for several years. Some files go unread for months and then become heavily accessed again, regardless of their creation date. Every file must remain available through a normal GET request with millisecond retrieval latency, without a restore operation. The team wants to reduce storage costs during periods of inactivity without incurring per-GB data retrieval charges or implementing application-level access tracking.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Store the files in S3 Intelligent-Tiering and leave the optional Archive Access and Deep Archive Access tiers disabled.

**Explanation:** S3 Intelligent-Tiering automatically moves eligible objects among its Frequent Access, Infrequent Access, and Archive Instant Access tiers based on access patterns. These tiers support millisecond retrieval without restore operations or data retrieval charges. Monitoring and automation charges apply, but application-level tracking is unnecessary. Disabling the optional asynchronous archive tiers preserves immediate access.

### Question 8 (SAA-C03)

**Question:**

A company stores 100 TB of immutable reference data in Amazon S3 Standard. Each object is at least 100 MB and will be retained for another year. An analytics application reads a different subset of the data each month. Total monthly data retrieval consistently equals 50% of the stored data volume. Reads must begin with millisecond latency without a restore operation, and the data must remain resilient to the loss of an Availability Zone.

A solutions architect uses the following rates for the company's AWS Region:
• S3 Standard: $0.023 per GB-month, with no data retrieval charge.
• S3 Standard-IA: $0.0125 per GB-month, plus $0.01 per GB retrieved.
• S3 One Zone-IA: $0.01 per GB-month, plus $0.01 per GB retrieved.
• S3 Glacier Instant Retrieval: $0.004 per GB-month, plus $0.03 per GB retrieved.

Assume request charges, transition charges, and data transfer charges are negligible. Which storage decision will provide the lowest ongoing cost while meeting all requirements?

**Correct answer:** Transition all objects to S3 Standard-IA.

**Explanation:** S3 Standard-IA provides millisecond access and stores data across multiple Availability Zones. Its effective monthly cost per stored GB is $0.0125 + (0.5 × $0.01) = $0.0175, which is lower than both S3 Standard and S3 Glacier Instant Retrieval for this workload. The object sizes and remaining retention period also avoid minimum billable size and early-deletion concerns.

## Practice Storage Tiering in a full exam

Questions on Storage Tiering in each practice exam, with every answer option and an explanation for each:

- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 19 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 9 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 9 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 5 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 5 questions
- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 2 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 2 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 1 question

## What is Storage Tiering

Storage tiering is the practice of assigning data to storage classes that match its access requirements and economic value. Frequently accessed data generally belongs in a tier designed for immediate, economical access. Infrequently accessed data can use a lower-cost tier, while long-lived records that are rarely retrieved may fit an archive tier. Terms such as hot, cool, and cold describe these patterns, but their exact performance and pricing vary between platforms.

In the cloud, engineers can choose a tier when writing data or configure policies to move it later. Lifecycle policies automate actions when data meets conditions such as age, location, or metadata tags. For example, application logs might remain in a frequently accessed class for 30 days, move to an infrequent-access class, and then transition to an archive class after 180 days. These intervals should reflect investigation requirements, retrieval deadlines, and the storage service's transition restrictions rather than arbitrary cost targets.

For AWS certification scenarios, Amazon S3 Lifecycle is a key example. Rules can transition eligible objects between supported storage classes and can expire objects when their retention period ends. A rule can target a subset of objects using filters such as a prefix or tags. Transitioning an object changes its storage class; expiration deletes data according to the applicable versioning behavior. These are different actions, and a cost-saving transition does not require deleting the object.

Age-based lifecycle rules and access-based automatic tiering solve different problems. An S3 Lifecycle transition based on object age does not determine whether that object was recently read. Access-aware capabilities, such as S3 Intelligent-Tiering, can adapt placement when usage is unpredictable. Engineers should choose automation that matches the workload rather than assuming every lifecycle policy monitors access frequency.

The lowest storage price does not necessarily produce the lowest total cost. Evaluate transition requests, retrieval charges, minimum billable object sizes, minimum storage durations, monitoring fees, and any temporary restored copies. Moving many small objects or retrieving archived data frequently can eliminate expected savings. Deleting or moving data before a minimum storage duration ends can also incur additional charges.

Access behavior is another important trade-off. Some archive classes provide immediate access, while others require a restore operation and a waiting period. A compliance archive that can wait hours for retrieval has different requirements from incident-response logs needed within seconds. Test retrieval workflows before relying on an archive tier for operational recovery.

Finally, tiering is not a substitute for backup, replication, or retention enforcement. Lower cost does not automatically mean lower durability, but individual classes can differ in availability and resilience characteristics. For versioned objects, account for noncurrent versions because managing only the current version can leave substantial storage charges. Review access patterns, actual bills, and recovery requirements regularly to keep policies aligned with the workload.

## Learn Storage Tiering in lessons

14 short lessons on Storage Tiering in 7 certification courses.

- CLF-C02: Data Retention vs. Storage Tiering (Premium), https://app.blowstack.com/lessons/data-retention-vs-storage-tiering-clf-c02
- MLA-C02 (beta): Data Retention vs Storage Tiering (Premium), https://app.blowstack.com/lessons/data-retention-vs-storage-tiering-mla-c02
- SAP-C03: Storage tiering: access-driven tier placement (Premium), https://app.blowstack.com/lessons/storage-tiering-access-driven-tier-placement-sap-c03
- SOA-C03: Storage Tiering: S3 Lifecycle transitions (Premium), https://app.blowstack.com/lessons/storage-tiering-s3-lifecycle-transitions-soa-c03
- DOP-C02: Data Archiving vs Storage Tiering (Premium), https://app.blowstack.com/lessons/data-archiving-vs-storage-tiering-dop-c02
- DEA-C01: Storage Tiering: age-based transitions with S3 Lifecycle (Premium), https://app.blowstack.com/lessons/storage-tiering-age-based-transitions-with-s3-lifecycle-dea-c01
