AWS DEA-C01 Study Plan (30 / 60 / 90 Days)

A practical DEA-C01 study plan you can follow: 30-day intensive, 60-day balanced, and 90-day part-time schedules with weekly focus by domain, suggested hours/week, and tips for using the Mastery Cloud practice app.

This page answers the question most candidates actually have: “How do I structure my DEA‑C01 prep?”
Below are three realistic schedules (30/60/90 days) based on the official domain weights and the way DEA‑C01 questions are written (scenario + trade-offs + operational best practices).

Use the plan that matches your available time, then follow the loop: Syllabus → drills → review misses → mixed sets → timed runs.


How long should you study?

Typical ranges based on background:

Your starting pointTypical total study timeBest-fit timeline
You build data pipelines on AWS already40–60 hours30–60 days
You know data engineering but are newer to AWS services60–90 hours60–90 days
You’re newer to data platforms and analytics services90–120+ hours90 days

Choose a plan based on hours per week:

Time you can commitRecommended planWhat it feels like
10–15 hrs/week30‑day intensiveFast learning + lots of practice
6–9 hrs/week60‑day balancedSteady progress + room for review
3–5 hrs/week90‑day part‑timeSlow-and-solid with repetition

Use the exam weights to allocate time

DEA‑C01 domain weights:

DomainWeightPrep focus
Domain 1: Data Ingestion and Transformation34%Ingestion patterns, ETL/processing choices, orchestration
Domain 2: Data Store Management26%Store selection, catalogs, lifecycle, modeling + schema evolution
Domain 3: Data Operations and Support22%Automation, analytics, monitoring, data quality
Domain 4: Data Security and Governance18%IAM/Lake Formation, encryption/masking, audit logs, privacy

If you want one rule: spend ~60% learning + 40% practice early, then invert it to ~30% learning + 70% practice in the final 1–2 weeks.


30-Day Intensive Plan

Target pace: ~10–15 hours/week.
Goal: cover the blueprint quickly, then harden instincts through drills and mixed sets.

WeekFocus (domains/tasks)What to doLinks
1Domain 1 foundations
Task 1.1
Task 1.2
Build ingestion + ETL service pickers (Kinesis/MSK/DMS/AppFlow; Glue/EMR/Lambda/Redshift). Do 2–3 focused drills and start a miss log.SyllabusCheatsheetPractice
2Domain 1 orchestration + programming + start Domain 2
Task 1.3
Task 1.4
Task 2.1
Focus on orchestration trade-offs (MWAA vs Step Functions vs Glue workflows) + IaC/SQL basics. End the week with a 30–40Q mixed set.CheatsheetPractice
3Domain 2 store management + modeling
Task 2.2
Task 2.3
Task 2.4
Catalog + partitions + lifecycle policies + schema evolution. Drill data format/partitioning questions until they feel automatic.SyllabusPractice
4Domain 3 ops + Domain 4 governance + review
Task 3.1
Task 3.2
Task 3.3
Task 3.4
Task 4.1Task 4.5
Do 2 mixed sets + 1 timed run (65Q/130m). Review every miss and re-drill weak tasks until misses repeat less.PracticeFAQ

60-Day Balanced Plan

Target pace: ~6–9 hours/week.
Goal: spaced repetition and deeper drills while steadily building practice volume.

WeeksFocusWhat to do
1–2Domain 1 (Tasks 1.1–1.4)Ingestion, ETL/processing, orchestration, SQL/IaC basics; do 2 drills per week.
3–4Domain 2 (Tasks 2.1–2.4)Store selection, catalog/partitions, lifecycle, modeling/schema evolution; end week 4 with a mixed set.
5–6Domain 3 (Tasks 3.1–3.4)Automation, analytics choices, monitoring, data quality; do weekly mixed sets.
7–8Domain 4 (Tasks 4.1–4.5) + final reviewIAM/Lake Formation, encryption, audit logs, privacy; 2 timed runs and re-drill weak tasks.

Use task links from the Syllabus to drill each area as you go.


90-Day Part-Time Plan

Target pace: ~3–5 hours/week.
Goal: slow repetition with consistent drills and periodic mixed sets.

WeekFocus (tasks)What to do
1Task 1.1Batch vs streaming + triggers/schedules; do one drill set.
2Task 1.2Glue vs EMR vs Redshift; drill.
3Task 1.3MWAA vs Step Functions vs Glue workflows; drill.
4Task 1.4SQL + IaC basics; drill.
5Task 2.1Store selection + access patterns; drill.
6Task 2.2Glue catalog + crawlers + partitions; drill.
7Task 2.3Lifecycle + retention + TTL; do a mixed set.
8Task 2.4Modeling + schema evolution; drill.
9Task 3.1Automation + orchestration patterns; drill.
10Task 3.2Athena/Redshift + QuickSight; drill.
11Task 3.3 + Task 3.4Monitoring + data quality; drill.
12Domain 4 (Tasks 4.1–4.5) + final reviewSecurity/governance; 2 timed runs and re-drill weak tasks.

How to integrate the Mastery Cloud app

Use the app to turn the syllabus into a repeatable loop:

  1. Start in the Syllabus and open a task.
  2. Drill that task in Practice.
  3. After each set, write 3–5 “rules” from your misses (for example: Parquet + partitions for Athena, Lake Formation for fine-grained access).
  4. Re-run weak tasks 48–72 hours later (spaced repetition).

Direct practice link: /app/cloud/#/topic-selection/aws_dea-c01