Home / data-analytics / AWS Certified Data Engineer - Associate (DEA-C01) / Cheat Sheet
AWS Certified Data Engineer - Associate (DEA-C01)

DEA-C01 Cheat Sheet

DEA-C01 Tests Picking the Lowest-Overhead Pipeline That Meets the Latency Target

An associate exam for engineers who build and run data pipelines on AWS. Several options usually work; the shift is choosing the serverless or managed path that meets latency and cost with the least operational effort.

Check Your Readiness →
Among the harder certs
Avg: Not published by Amazon Web Services
Pass: 750 / 1000
Most candidates understand AWS Certified Data Engineer - Associate (DEA-C01) concepts — and still fail. This exam tests how you apply knowledge under pressure.

DEA-C01 Domain Map (exam guide v1.1)

Questions read like design reviews: source, arrival pattern, volume, latency target and a cost or operations constraint, then the service or pipeline order. Guide v1.1 only merged the knowledge and skills lists; domains, weights and all 17 task statements are unchanged.

  1. 01
    Data Ingestion and Transformation (34%) — Kinesis vs. Firehose vs. MSK, Glue vs. EMR vs. Lambda, orchestration
  2. 02
    Data Store Management (26%) — Redshift, DynamoDB, S3 with Athena, partitions, catalog updates, lifecycle and TTL
  3. 03
    Data Operations and Support (22%) — job failures, skew, monitoring, Athena vs. Redshift Serverless, data quality rules
  4. 04
    Data Security and Governance (18%) — Lake Formation fine-grained grants, KMS, Secrets Manager, CloudTrail, Config, Macie

Wrong instinct vs correct approach

A 500 GB file lands nightly and must be transformed before morning reporting
✕ Wrong instinct

Trigger a Lambda function to process the file

✓ Correct approach

Lambda stops at 15 minutes and has limited memory and storage. An AWS Glue Spark job handles this serverlessly; choose EMR only when you need custom frameworks, instance control or Spot pricing.

Hourly jobs keep reprocessing every file in the same S3 prefix
✕ Wrong instinct

Reload the full prefix each run to stay consistent

✓ Correct approach

Enable Glue job bookmarks so each run processes only new data, or trigger on S3 event notifications through EventBridge. Full reloads waste DPU hours and create duplicates downstream.

A Redshift cluster runs near full utilization around the clock and finance wants lower cost
✕ Wrong instinct

Move it to Redshift Serverless to save money

✓ Correct approach

Serverless saves money for intermittent or unpredictable demand. Steady, heavy usage is usually cheaper on provisioned nodes with reserved pricing, with concurrency scaling covering occasional peaks.

Auditors want to see a bucket's encryption setting as it was six months ago
✕ Wrong instinct

Search CloudTrail for the PutBucketEncryption call

✓ Correct approach

AWS Config records resource configuration history and evaluates compliance over time. CloudTrail shows who made API calls and CloudTrail Lake helps investigations, but neither is the configuration timeline auditors asked for.

Expired DynamoDB session items must be removed without writing custom jobs
✕ Wrong instinct

Schedule a nightly Lambda to scan and delete old items

✓ Correct approach

DynamoDB Time to Live deletes items once a timestamp attribute passes, without consuming write capacity, and the deletions appear in DynamoDB Streams for archiving. S3 Lifecycle expiration plays the same role for objects.

Know these cold

  • ▸ Kinesis Data Streams replays within retention; Firehose has no replay; DynamoDB Streams keeps 24 hours
  • ▸ Lambda maxes out at 15 minutes; heavy ETL goes to Glue, custom clusters to EMR
  • ▸ Step Functions for retries and service integrations; MWAA when the team already writes Airflow DAGs
  • ▸ EventBridge starts pipeline work on events but does not track pipeline state
  • ▸ Partition projection for predictable keys; crawlers for unknown schemas; MSCK REPAIR as a manual fallback
  • ▸ Spectrum reads S3 files; federated query reads RDS and Aurora; data sharing avoids copies
  • ▸ Athena bills per data scanned; Parquet, compression and partitions cut both cost and runtime
  • ▸ Glue job errors live in CloudWatch Logs; CloudTrail only shows who called the API
  • ▸ Glue Data Quality quarantines bad rows in-pipeline; DataBrew rulesets suit analysts with no code
  • ▸ Credentials needing automatic rotation belong in Secrets Manager, not Parameter Store SecureString

Can you answer these without checking your notes?

In this scenario: "A 500 GB file lands nightly and must be transformed before morning reporting" — what should you do first?
Lambda stops at 15 minutes and has limited memory and storage. An AWS Glue Spark job handles this serverlessly; choose EMR only when you need custom frameworks, instance control or Spot pricing.
In this scenario: "Hourly jobs keep reprocessing every file in the same S3 prefix" — what should you do first?
Enable Glue job bookmarks so each run processes only new data, or trigger on S3 event notifications through EventBridge. Full reloads waste DPU hours and create duplicates downstream.
In this scenario: "A Redshift cluster runs near full utilization around the clock and finance wants lower cost" — what should you do first?
Serverless saves money for intermittent or unpredictable demand. Steady, heavy usage is usually cheaper on provisioned nodes with reserved pricing, with concurrency scaling covering occasional peaks.

Common Exam Mistakes — What candidates get wrong

Choosing Amazon Data Firehose when consumers must replay events

Firehose delivers to S3, Redshift, OpenSearch and other targets with no consumer code, but keeps nothing for replay. Kinesis Data Streams retains records for the configured period so a new consumer can reprocess them. MSK fits teams that need Kafka APIs.

Adding Kinesis shards to fix throttling caused by one hot partition key

Records with the same partition key always map to one shard, so extra shards leave the hotspot in place. Use a higher-cardinality partition key. The same logic applies to Glue Spark jobs where one skewed key exhausts a single executor.

Running a Glue crawler every few minutes to expose new partitions

For partitions that follow a predictable date pattern, Athena partition projection computes them without catalog updates, and ALTER TABLE ADD PARTITION registers them precisely. Crawlers suit unknown or changing schemas; MSCK REPAIR TABLE works but rescans prefixes.

Using an S3 bucket policy to hide a PII column from analysts

Bucket policies act on whole objects and prefixes. Column, row and cell-level restrictions on Data Catalog tables come from AWS Lake Formation grants, which Athena, Redshift Spectrum and EMR honor. Macie can find the PII but never blocks access.

Loading years of archived data into Redshift for an occasional report

Query it in place: Redshift Spectrum reads S3 files from the cluster, and Athena charges per data scanned. Store archives as partitioned Parquet to cut scan cost. Federated query targets operational databases such as RDS and Aurora, not S3 files.

Resources to help you pass AWS Data Engineer Associate on your first attempt

DEA-C01 rewards the least-overhead pipeline that meets the target. See which service choices you still miss.