AWS Certified Data Engineer - Associate (DEA-C01) covers more ground than any other exam on this blog, with 19 domain deep-dive posts backing it — and for good reason. It validates the entire lifecycle of ingesting, storing, operating, and securing data in a single certification. Just as a distribution center runs receiving, inventory, shipping, and security as one connected system, a data engineer owns everything from the moment data arrives to the moment it lands in an analyst's hands. AWS introduced this certification in 2023 to formally recognize data engineering as its own discipline, and the exam scope reflects that — it's considerably more hands-on than the older big data certifications it replaced.
Who Needs This Exam, and the Exam Overview
An architect draws the blueprint, but the systems technician is the one who actually gets water and electricity flowing through the building. DEA-C01 is the certification for the technician who makes data actually flow through an organization. It fits data engineers building ETL pipelines, real-time processing specialists working with streaming data, and architects designing data warehouses and lakes. Only 50 of the 65 questions are scored; the other 15 are unscored questions AWS is testing for future exams. The exam fee is 150 USD, and certification stays valid for three years.
Exam Format: Inspecting an Entire Pipeline in 130 Minutes
Like a routine physical, this exam spends 130 minutes running 65 questions across the full breadth of data engineering. The passing score is 720 out of 1000. It covers noticeably more AWS services than other Associate-level exams, so even when names like Kinesis, Glue, EMR, Redshift, and Athena are familiar, knowing exactly when to reach for each one is what actually determines whether you pass.
Domain 1: Data Ingestion and Transformation (34%)
Just as smaller tributaries converge into a larger river, this domain covers gathering data from varied sources and shaping it into something usable. It carries the highest weight of any domain, so it decides the outcome of the exam more than any other. The essentials are real-time streaming ingestion with Kinesis, serverless ETL with Glue, large-scale Spark and Hadoop processing with EMR, and pipeline orchestration plus core programming concepts. Eight related posts cover this domain: Complete Guide to Data Ingestion Services, Kinesis Explained, AWS Glue Explained, EMR Explained, Streaming and Batch Data Ingestion, Data Transformation and Processing, Data Pipeline Orchestration, and Programming, IaC, and CI/CD.
Domain 2: Data Store Management (26%)
Just as a warehouse manager decides where items go and how they're categorized, this domain covers deciding which storage service holds your data and in what structure. The essentials are data warehousing with Redshift, choosing the right store for a given workload, managing metadata through a data catalog, and lifecycle policies plus schema evolution. Four related posts cover this domain: Redshift Explained, Choosing and Configuring Data Stores, Data Catalog Systems, and Data Lifecycle and Schema Evolution.
Domain 3: Data Operations and Support (22%)
Just as an air traffic controller watches the status of many flights at once, this domain covers confirming that an already-built pipeline is actually running well and analyzing the data flowing through it. The essentials are serverless querying and analysis with Athena, monitoring pipelines and managing data quality, and process automation. Four related posts cover this domain: Athena Explained, Pipeline Monitoring and Data Quality, Data Analysis and Visualization, and Data Processing Automation.
Domain 4: Data Security and Governance (18%)
A bank doesn't hand its vault key to just anyone, and this domain covers controlling who can touch data and how, across the entire pipeline. It carries the lowest weight, but it cuts across all three other domains. The essentials are audit logging and privacy compliance, encrypting and masking data at rest and in transit, and authentication and authorization mechanisms. Three related posts cover this domain: Audit Logs and Data Privacy Governance, Data Encryption and Masking, and Authentication and Authorization Mechanisms.
A Study Order for Beginners, and Common Mistakes
Walking an unfamiliar city without a map means retracing the same streets twice. If you're new to data engineering, start with Domain 1 (ingestion and transformation), the highest-weighted domain, and get hands-on with Kinesis and Glue in the console, then move into Domain 2 (data store management) and sort out how Redshift differs from other storage options. From there, run real queries in Athena for Domain 3 (operations and support), and finish by layering in encryption and authorization for Domain 4 (security and governance). The most common mistake, given how many services this exam covers, is memorizing names and functions as one-to-one pairs — the real exam loves comparative questions like "which fits this situation better, Kinesis Data Streams or Kinesis Data Firehose?" A second common mistake is lumping Glue and EMR together as "the big data processing services"; the real distinction is whether you want serverless simplicity or fine-grained control over the cluster.
Exam Key Takeaways
"Ingests and processes real-time data streams" -- Amazon Kinesis "Fully managed real-time delivery to S3 or Redshift" -- Kinesis Data Firehose "Serverless ETL jobs and a shared data catalog" -- AWS Glue "Managed Spark and Hadoop clusters for large-scale processing" -- Amazon EMR "Petabyte-scale data warehouse" -- Amazon Redshift "Serverless SQL queries directly against data in S3" -- Amazon Athena "A shared catalog that centralizes metadata" -- AWS Glue Data Catalog "Rarely accessed data moves to a cheaper tier" -- S3 Lifecycle policies "Encrypts data both at rest and in transit" -- AWS KMS "Obscures sensitive fields to minimize exposure" -- data masking
DEA-C01 tests whether you can pick the right service for a situation, not whether you know every service name, so the surest shortcut to passing is organizing similar-looking service pairs around the question "when this one, and when that one instead.