Study DEA-C01 Analysis, Visualization and SQL Patterns: key concepts, common traps, and exam decision cues.
DEA-C01 expects more than pipeline movement. It also expects you to know how data gets queried, explored, and visualized. Strong answers recognize when SQL, notebooks, or BI tools are the right access path.
Analytical access path: The combination of query engine, notebook, warehouse, or BI tool used to explore and consume data.
Serverless SQL: Query pattern where you run SQL against data without provisioning a long-lived cluster for the query engine.
Visualization layer: Tooling that turns curated query results into dashboards, KPIs, and reader-friendly charts.
AWS wants you to separate:
DEA-C01 often hides the real choice behind generic “analytics” wording. The strongest first move is to identify the user and the access path before naming the service.
| Requirement | Strongest first fit | Why |
|---|---|---|
| SQL over data in S3 without standing up a cluster | Amazon Athena | The need is serverless SQL on data-lake storage |
| repeated analytical queries on modeled warehouse data | Amazon Redshift | DEA-C01 expects a warehouse answer when structured analytical performance matters |
| business users need shareable dashboards and KPIs | Amazon QuickSight | The need is BI delivery, not only query execution |
| engineers or analysts need exploratory code, notes, and iterative analysis | notebook workflow such as Glue Studio notebooks or SageMaker notebooks | The need is interactive exploration, not static dashboards |
| the SQL itself is slow because of scan waste or poor pruning | improve partitions, layout, or warehouse design | The problem is data-access efficiency, not dashboarding |
| If the stem emphasizes… | Think first | Why this fits |
|---|---|---|
| ad hoc SQL against data in S3 | Athena | This is serverless lake querying |
| repeated analytical queries on curated warehouse tables | Redshift | This is a warehouse workload |
| charts, dashboards, KPI sharing, or scheduled visual refresh | QuickSight | This is BI delivery |
| iterative exploration with code, notes, and experiments | Notebook workflow | This is exploratory work, not governed presentation |
| slow query behavior | storage layout, partitions, file format, or warehouse design | The issue is query efficiency, not dashboard cosmetics |
| Question | SQL engine | Notebook | BI layer |
|---|---|---|---|
| Main job | execute queries | explore and iterate | present results |
| Strongest first user | analyst or engineer | engineer, data scientist, power analyst | business reader or manager |
| Typical DEA-C01 cue | “run SQL” or “query the lake” | “explore, prototype, compare” | “dashboard, scorecard, business view” |
| Common trap | treating Athena as a dashboard tool | assuming notebooks replace governed reporting | assuming BI replaces data modeling |
flowchart LR
A["Analytics request"] --> B{"What is the user really trying to do?"}
B -->|Run ad hoc SQL on S3 data| C["Athena"]
B -->|Query curated warehouse tables repeatedly| D["Redshift"]
B -->|Explore iteratively with code and notes| E["Notebook workflow"]
B -->|Share dashboards and KPIs| F["QuickSight"]
| Symptom | Better reading |
|---|---|
| Athena queries scan too much data | check partitioning, file format, compression, and projection opportunities |
| Redshift dashboard queries are inconsistent under repeated load | think about warehouse design, sort or distribution choices, and workload behavior |
| the SQL works but users want scheduled visual refreshes | the missing layer may be QuickSight rather than another query engine |
| users keep exporting ad hoc CSVs because dashboards do not fit | the presentation layer may be weak, even if the underlying data model is fine |
Use this order when analytics access paths look similar:
| Trap | Better reading |
|---|---|
| “Athena is basically QuickSight.” | Athena executes queries, while QuickSight presents results. |
| “A notebook is just a prettier dashboard.” | A notebook is exploratory and iterative, not the same as governed BI delivery. |
| “If SQL is slow, add another dashboard layer.” | Slow SQL usually points to access-path or storage-design issues. |
| “Warehouse and lake queries are interchangeable on the exam.” | DEA-C01 expects you to read the storage model, workload, and audience carefully. |
A finance team wants reusable dashboards over curated metrics, while engineers still need a low-friction way to query raw partitioned data in S3 during investigations. What is the strongest reading first?
Correct answer: A. DEA-C01 expects you to separate BI delivery from ad hoc query access. QuickSight is the dashboard layer, while Athena is the strongest first serverless SQL lane for raw S3-based exploration.