AWS DEA-C01 Study Plan: Ingestion, Catalogs, and Lakehouse in 30, 60, and 90 Days

AWS DEA-C01 30-, 60-, and 90-day study plan for ingestion, catalogs, lakehouse, review loops, and final-week priorities.

Use this study plan when you want a structured route through AWS Certified Data Engineer - Associate (DEA-C01) instead of memorizing isolated data services. DEA-C01 is an associate-level data engineering exam. It tests whether you can ingest, transform, store, govern, monitor, troubleshoot, and optimize data pipelines on AWS.

AWS’s current exam guide emphasizes production data-platform judgment: volume, variety, velocity, schema design, governance, privacy, cost, performance, and pipeline supportability. The exam is not an ML training exam and does not require language-specific syntax, but it does expect you to understand SQL, high-level programming concepts, Git basics, data lakes, and current data-platform patterns such as vectors where they affect data engineering decisions.

Current exam facts

I verified these current AWS exam facts on May 16, 2026.

Item Value
Exam AWS Certified Data Engineer - Associate
Exam code DEA-C01
Category Associate
Questions 65 total
Scoring 50 scored + 15 unscored (unscored items are not identified)
Question types Multiple choice and multiple response
Time 130 minutes
Passing score 720, scaled 100-1000
Cost 150 USD
Target candidate 2-3 years of data engineering experience and 1-2 years of hands-on AWS services experience

AWS says exam guides are periodically revised and that revisions are published before changes affect the exam. Recheck the official guide before scheduling, especially for newer data, vector, governance, and AI-adjacent data-processing scope.

Weight-driven study allocation

Domain Weight How to allocate study time
Data Ingestion and Transformation 34% Spend the most time on batch vs streaming ingestion, transformation service fit, file formats, orchestration, notifications, IaC, and code-performance concepts.
Data Store Management 26% Drill data-store selection, Glue Data Catalog, crawlers, partitions, lifecycle, load/unload, data modeling, schema evolution, and optimization.
Data Operations and Support 22% Practice automation, APIs, analytics operations, SQL, visualization, monitoring, logging, troubleshooting, consistency, quality, and skew.
Data Security and Governance 18% Study IAM, secrets, network access, Lake Formation, least privilege, encryption, masking, privacy, sovereignty, and audit logging.

The first two domains carry 60% of scored content. That does not mean security and operations are optional. Many hard questions combine ingestion, storage, monitoring, and governance in one scenario.

Pick the right timeline

Starting point Typical study time Best-fit timeline
You build AWS data pipelines today 45-70 hours 30-60 days
You know data engineering but are newer to AWS analytics services 70-100 hours 60 days
You know AWS but have less data-platform depth 80-120 hours 60-90 days
You are new to both AWS and data engineering operations 120+ hours 90 days before scheduling

Choose the longer route if you cannot explain the difference between Kinesis, MSK, DMS, Glue, EMR, Lambda, Step Functions, MWAA, Athena, Redshift, Lake Formation, and Glue Data Catalog by job to be done.

The DEA-C01 study loop

Use one repeatable loop. Data-engineering exam prep works best when every service choice is tied to a pipeline failure mode.

    flowchart LR
	  S["Source and volume"] --> I["Ingestion pattern"]
	  I --> T["Transform and format"]
	  T --> M["Metadata and store"]
	  M --> O["Operate and monitor"]
	  O --> G["Govern and protect"]
	  G --> R["Miss rule"]
Step What to ask
Source and volume Is the source batch, streaming, database CDC, application event, SaaS, file, or API?
Ingestion pattern Does the pipeline need durability, replay, ordering, low latency, schedule control, or backfill?
Transform and format Should processing happen with Glue, EMR, Lambda, Redshift, SQL, Spark, or a managed workflow?
Metadata and store What catalog, schema, partitioning, lifecycle, and access pattern make the data queryable?
Operate and monitor What metric, log, alert, retry, data-quality check, or troubleshooting path proves the pipeline works?
Govern and protect What identity, Lake Formation permission, encryption, masking, audit, or privacy control is required?

30-day intensive plan

Use this route only if you already understand data engineering basics and can study most days.

Week Focus What to produce
1 Ingestion and transformation A picker for batch, streaming, CDC, SaaS, API, file, trigger, orchestration, and transformation service choices.
2 Data stores, catalogs, and lifecycle A lakehouse map covering S3, Glue Data Catalog, crawlers, partitions, schema evolution, formats, lifecycle policies, and access patterns.
3 Operations, support, and quality A runbook for monitoring, logging, retries, troubleshooting, skew, consistency, data-quality checks, SQL operations, and analytics handoff.
4 Security, governance, and mixed review A governance checklist for IAM, Lake Formation, KMS, secrets, network access, masking, privacy, sovereignty, CloudTrail, and CloudWatch Logs.

30-day rule

Every day should create one artifact that improves scenario reasoning.

Artifact Why it matters
Pipeline sketch Forces you to separate source, ingestion, transformation, storage, operations, and governance.
Service chooser Prevents treating Glue, EMR, Lambda, Redshift, Step Functions, and MWAA as interchangeable.
Metadata checklist Keeps catalog, partitions, schema, crawler, table, and format decisions visible.
Failure-mode log Turns missed questions into replay, late data, duplicate, schema drift, skew, permission, or quality rules.
Governance matrix Keeps IAM, Lake Formation, KMS, masking, privacy, and audit evidence distinct.

60-day balanced plan

This is the best default route for most candidates.

Weeks Focus What to do
1-2 Data Ingestion and Transformation Drill source patterns, streaming vs batch, triggers, schedules, transformation services, formats, orchestration, notifications, IaC, and code-performance concepts.
3-4 Data Store Management Study store choice, access patterns, Glue Data Catalog, crawlers, partitions, lifecycle, retention, schema evolution, modeling, and optimization.
5 Data Operations and Support Practice automation, APIs, analytics operations, SQL patterns, visualization, pipeline monitoring, logging, troubleshooting, quality, consistency, and skew.
6 Data Security and Governance Drill authentication, secrets, network access, authorization, Lake Formation, encryption, masking, cross-account controls, logging, privacy, and sovereignty.
7 Mixed pipeline scenarios Run timed sets and group misses by failure mode: ingestion, transform, metadata, store, operation, quality, or governance.
8 Final repair and scheduling decision Reread weak lessons, review the cheat sheet, answer sample questions, and schedule only if misses are narrow.

90-day part-time plan

Use this route if you are building AWS data-engineering depth while studying.

Phase Weeks Outcome
Ingestion foundation 1-3 You can choose batch, streaming, CDC, file, SaaS, API, and trigger patterns and explain replay/backfill implications.
Transformation and orchestration 4-5 You can choose transformation and workflow tools based on volume, latency, complexity, dependency, cost, and support needs.
Stores, catalogs, and lifecycle 6-7 You can design cataloged, partitioned, governed, and lifecycle-managed data stores for query and retention needs.
Operations and quality 8-9 You can monitor, troubleshoot, automate, query, visualize, and validate data pipelines.
Security and governance 10-11 You can protect data with IAM, Lake Formation, KMS, masking, audit logs, network controls, privacy, and sovereignty decisions.
Exam execution 12 You can answer mixed scenarios under time pressure and explain every repeated miss as a pipeline decision rule.

What to drill by domain

Domain Drill questions until you can answer…
Data Ingestion and Transformation What source pattern, latency need, durability requirement, and transformation engine fit the pipeline?
Data Store Management What store, format, partitioning, catalog, schema, lifecycle, and model fit the access pattern?
Data Operations and Support What metric, log, alert, retry, query, quality check, or troubleshooting action proves the pipeline is healthy?
Data Security and Governance What identity, permission layer, encryption key, masking rule, privacy control, and audit evidence protects the data?

High-yield service comparisons

Decision Choose by asking…
Kinesis vs MSK Do you need AWS-managed streaming primitives or Kafka compatibility/ecosystem control?
DMS vs DataSync vs Transfer Family Is the source a database migration/CDC stream, file transfer/sync path, or managed SFTP/FTPS/FTP access pattern?
Glue vs EMR vs Lambda Is the transformation serverless ETL/catalog-aware, cluster-scale/custom Spark/Hadoop, or short event-driven code?
Step Functions vs MWAA vs Glue workflows Is the workflow general service orchestration, Airflow DAG compatibility, or Glue-centered ETL coordination?
Athena vs Redshift Is the workload ad hoc/query-on-S3 and serverless, or warehouse-style analytics with performance and modeling needs?
S3 formats: CSV vs JSON vs Parquet Is the priority human readability, semi-structured interchange, or columnar analytics efficiency?
IAM vs Lake Formation Is the question about broad AWS permissions or fine-grained data lake permissions and governance?
CloudTrail vs CloudWatch Logs Is the evidence API activity/audit trail or application/service log output and operational telemetry?

Data-quality and failure-mode checklist

DEA-C01 often tests whether you can keep pipelines trustworthy after the happy path breaks.

Failure mode What to review
Late or missing data Watermarks, schedule windows, retries, alerts, backfills, and downstream dependency handling
Duplicate records Idempotency, deduplication keys, checkpointing, CDC handling, and replay design
Schema drift Glue Data Catalog, crawlers, schema evolution, validation, compatibility, and downstream impact
Small files or skew Partition design, compaction, distribution keys, file sizing, Spark tuning concepts, and query cost
Poor query performance Columnar formats, partition pruning, compression, statistics, indexes, sort/distribution choices, and materialization
Access failure IAM role, resource policy, Lake Formation grant, KMS key policy, network path, and secret rotation
Governance gap Audit log, retention, masking, anonymization, sovereignty, lineage, and least-privilege evidence

Final-week checklist

Use the final week for mixed pipeline decision speed.

Day Work
7 days out Reread the cheat sheet and summarize each domain as one pipeline decision problem.
6 days out Drill ingestion and transformation: batch/streaming, CDC, triggers, formats, Glue, EMR, Lambda, Redshift, Step Functions, and MWAA.
5 days out Drill data store management: access patterns, S3, Glue Data Catalog, partitions, crawlers, lifecycle, schema evolution, and optimization.
4 days out Drill operations and support: automation, APIs, Athena, Redshift, QuickSight, SQL, monitoring, logging, troubleshooting, data quality, and skew.
3 days out Drill security and governance: IAM, secrets, network access, Lake Formation, KMS, masking, privacy, sovereignty, CloudTrail, and CloudWatch Logs.
2 days out Run one mixed timed block and convert repeated misses into short pipeline rules.
1 day out Review only weak rules, domain weights, current facts, high-yield comparisons, and exam logistics.

Readiness signals

You are close to ready when:

  • You can draw a source-to-consumer pipeline and place ingestion, transform, catalog, storage, operations, and governance decisions correctly.
  • You can explain why a service choice fits volume, velocity, variety, latency, replay, and support requirements.
  • You can separate metadata/catalog problems from storage-engine problems.
  • You can choose the evidence source for pipeline troubleshooting before guessing at a fix.
  • You can distinguish IAM, Lake Formation, KMS, masking, network access, and audit logging.
  • You can keep a steady pace across 65 questions in 130 minutes.

If you only have 48 hours

This is only reasonable if you are already near-ready.

  1. Read the cheat sheet twice: once before practice and once after reviewing misses.
  2. Drill one mixed timed block and classify every miss by pipeline layer.
  3. Spend one focused block on ingestion/transformation and one on catalogs/store management.
  4. Review operations, data quality, Lake Formation, KMS, IAM, masking, CloudTrail, CloudWatch Logs, and high-yield service comparisons.
  5. Recheck the current official AWS page before scheduling or buying an exam attempt.

Booking signal

Schedule only when your misses are narrow and explainable. If you still choose services by recognition instead of source pattern, access pattern, metadata need, failure mode, or governance boundary, keep studying. DEA-C01 rewards practical data-platform reasoning, not a memorized list of analytics products.

Revised on Monday, June 15, 2026