DEA-C01 Data Lifecycle, Loads and Retention Guide

DEA-C01 expects you to think about what happens after data lands: how it is loaded, retained, versioned, archived, deleted, or replayed. Lifecycle choices affect cost, compliance, and operational recoverability.

Lifecycle policy: Rule that transitions or expires data based on age or other storage conditions.

Unload: Exporting data from a warehouse such as Amazon Redshift out to storage, commonly Amazon S3.

Retention boundary: Point at which data must be kept, archived, versioned, or deleted to satisfy business and legal requirements.

What AWS is really testing here

AWS wants you to separate:

• keeping data forever from retaining it deliberately
• loading data into an analytical store from archiving it out again
• cost optimization from resiliency and recoverability
• logical expiration rules from physical deletion requirements

The exam usually rewards answers that treat lifecycle as a design discipline, not as “keep everything until someone cleans it up later.”

Lifecycle chooser

Lifecycle, versioning, and expiration are not the same

Load and unload patterns

    flowchart LR
	  A["Data ages or changes role"] --> B{"What is needed?"}
	  B -->|Cheaper storage over time| C["Lifecycle transition"]
	  B -->|Delete after retention boundary| D["Lifecycle expiration"]
	  B -->|Recover previous object state| E["Versioning"]
	  B -->|Expire table items automatically| F["DynamoDB TTL"]
	  B -->|Export warehouse data| G["Redshift UNLOAD"]

Retention, resiliency, and deletion

How strong DEA-C01 answers usually reason

1. Ask whether the problem is tiering, expiration, recoverability, or movement out of the warehouse.
2. Use Lifecycle transitions for cost management, not for restore history.
3. Use versioning when accidental overwrite or deletion recovery matters.
4. Use TTL only when the stem is specifically about DynamoDB item expiry.
5. Keep legal deletion and cheap archival separate in your reasoning.

Decision order that usually wins

When lifecycle controls look similar, use this order:

1. Decide whether the requirement is cheaper storage, deletion, recoverability, item expiry, or warehouse export.
2. If the data should age into cheaper storage, choose a Lifecycle transition.
3. If it must disappear after a retention boundary, choose Lifecycle expiration.
4. If the problem is recovering an older object state, choose versioning.
5. If the question is about Redshift sending data out, choose UNLOAD, not a lifecycle feature.

Common traps

Harder scenario question

A company keeps daily Redshift aggregates for analysts, but legal policy says raw source files must remain restorable for 1 year while older raw data should shift to cheaper storage automatically. What is the strongest reading first?

• A. Disable versioning and keep everything in one hot tier forever
• B. Use Redshift UNLOAD when exports are needed, enable S3 versioning for recovery, and apply S3 Lifecycle transitions and expiration rules to the raw zone
• C. Replace S3 with Route 53
• D. Delete raw data immediately after the first successful query

Correct answer: B. DEA-C01 expects you to combine movement, recoverability, and retention controls instead of forcing one feature to do every lifecycle job.

Quiz