Azure Databricks Data Engineer Associate study materials
Azure Databricks Data Engineer Associate study resources

Azure Databricks Data Engineer Associate study plan

Azure Databricks Data Engineer Associate · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Data Ingestion and Loading

  • Map each ingestion path (Auto Loader, COPY INTO, streaming table ingestion, batch connector reads) to the workload scenario where it is the correct choice, and write a one-page decision table in your own words.

  • Configure Auto Loader with cloudFiles schema inference and schema evolution modes (addNewColumns, failOnNewColumns, rescue) and explain in notes when each mode protects pipeline continuity.

  • Create a bronze ingestion notebook that lands raw JSON and CSV files into a Unity Catalog managed volume and writes to a bronze Delta table with ingestion metadata columns (source file, ingestion timestamp, rescue data).

  • Compare idempotent re-run strategies (checkpoint reuse, file notification vs directory listing, MERGE-based deduplication) and document the failure mode each one prevents.

  • Practice reading the Auto Loader monitoring metrics (numFilesOutstanding, numBytesOutstanding) and state what each metric tells you during a backlog.

Your checkpoint

A working bronze ingestion notebook plus a written decision table covering at least four ingestion patterns with their trade-offs.

Week 2

Data Ingestion and Loading

  • Ingest from an external relational source using a JDBC-style batch read and land the result in a bronze table partitioned sensibly for downstream filtering.

  • Implement incremental ingestion of only changed rows using a watermark column, and prove a second run does not duplicate rows.

  • Handle malformed records by routing them to a quarantine table with the rescue schema, then write a query that counts and classifies the rejected records.

  • Set up a streaming ingestion that survives a deliberate schema change by adding a new column to the source files mid-stream.

  • Document the cost and latency trade-offs between continuous, triggered, and available-now trigger modes for your ingestion.

Your checkpoint

An end-to-end ingestion demo that runs twice without duplication, quarantines bad records, and survives a mid-stream schema change, with a short runbook describing how to operate it.

Week 3

Data Transformation and Modeling

  • Design a medallion layout (bronze, silver, gold) for a small dataset and justify what belongs in each layer rather than copying raw data upward.

  • Write silver-layer transformations that deduplicate on a business key, cast types explicitly, and standardize nulls and timestamps.

  • Implement an upsert with MERGE INTO, including matched-update, not-matched-insert, and a delete-handling branch, and explain the semantics of each clause.

  • Diagnose and fix the small-file problem by compacting a table with OPTIMIZE and evaluating whether liquid clustering or partitioning is the better fit for the query pattern.

  • Compare a batch transformation with its Structured Streaming equivalent for the same logic and note where the code diverges.

Your checkpoint

A silver and gold layer built from your bronze table, containing at least one MERGE upsert and one OPTIMIZE run, with before-and-after file counts recorded.

Week 4

Data Transformation and Modeling & Databricks Intelligence Platform

  • Apply Delta Lake table constraints (NOT NULL, CHECK) and observe what happens to a violating write, then decide where enforcement belongs in the pipeline.

  • Use time travel to query a prior table version and explain how retention and VACUUM interact with that ability.

  • Build at least one gold-layer aggregate that answers a concrete business question, and validate the result against a hand-computed check.

  • Describe the workspace objects (notebooks, clusters, SQL warehouses, catalogs, volumes, jobs) and how they relate, in a diagram you draw yourself.

  • Explain the difference between a managed and an external table in Unity Catalog and pick the correct one for two given scenarios.

Your checkpoint

A gold aggregate with a written validation note showing your hand-computed expected value matches the query output, plus a hand-drawn platform object diagram.

Week 5

Working with Lakeflow Jobs

  • Convert your multi-notebook pipeline into a Lakeflow Job with explicit task dependencies and a defined task-level cluster configuration.

  • Add job parameters and reference them from task code so the same job can be pointed at different environments.

  • Configure retries, timeouts, and a failure notification so a broken task surfaces to a human instead of failing silently.

  • Add a conditional or dependent task that runs only when upstream data passes a row-count sanity check.

  • Schedule the job and explain how the trigger type you chose affects cost and freshness.

Your checkpoint

A scheduled multi-task job that runs green end to end, with a screenshot-free written description of its dependency graph, parameters, and failure-handling settings.

Week 6

Implementing CI/CD & Troubleshooting, Monitoring, and Optimization

  • Store notebooks and job definitions in a Git-backed folder, create a feature branch, and open a pull request containing a pipeline change.

  • Define a Databricks Asset Bundle that declares your job, its clusters, and its parameters, then deploy it to a second target environment from the command line.

  • Explain how bundle targets, variables, and environment-specific overrides keep one definition usable across dev and prod.

  • Read the Spark UI for a slow query and identify the stage with the spill or skew, then state the specific fix you would apply.

  • Use the query profile or event log to find a task that retried, and explain what the retry indicates about the underlying data or code.

Your checkpoint

A bundle definition deployed successfully to two targets from one repository, plus a written performance diagnosis of one deliberately slow query with the fix you applied and the timing change.

Week 7

Governance and Security & Troubleshooting, Monitoring, and Optimization

  • Create a Unity Catalog catalog, schema, and volume, then grant least-privilege access to a group so a user can read gold but not bronze.

  • Explain the relationship between catalog, schema, table, and storage credential, and where each privilege is actually granted.

  • Implement row-level filtering or column masking on a gold table and verify the restriction with a query run as a lower-privileged principal.

  • Explain how a Delta Live Tables or Lakeflow pipeline's expectations differ from table constraints in where they block bad data.

  • Set up a baseline monitoring approach: capture table row counts and freshness over time and describe how you would alert on a freshness breach.

Your checkpoint

A documented access-control matrix for your pipeline (who can read which layer) plus a working masked or filtered view demonstrated against a restricted principal.

Week 8

Data Ingestion and Loading & Data Transformation and Modeling & Working with Lakeflow Jobs & Implementing CI/CD & Troubleshooting, Monitoring, and Optimization & Governance and Security & Databricks Intelligence Platform

  • Rebuild your end-to-end pipeline from an empty workspace using only your own notes and the bundle, to expose the gaps in your documentation.

  • Write and answer 40 or more original practice questions across all seven domains, weighted toward ingestion, transformation, and jobs, and log every miss by domain.

  • Re-study only the two domains with the lowest practice-question accuracy, focusing on the specific concepts you missed rather than re-reading broadly.

  • Explain aloud, without notes, the trade-off between Auto Loader and COPY INTO, between MERGE and overwrite, and between job clusters and all-purpose clusters.

  • Review the official exam skills outline one final time and confirm you can point to concrete work you have done for every listed skill.

Your checkpoint

A clean-room rebuild of the pipeline completed within the week, plus a scored practice-question log showing at least 80 percent accuracy overall and no domain below 70 percent.

Milestones

Week 2: You can ingest from files and a relational source, re-run without duplicating rows, and explain when Auto Loader beats COPY INTO.

Week 4: A bronze-to-silver-to-gold pipeline exists with a MERGE upsert, a compaction, and a validated gold aggregate.

Week 6: The pipeline runs as a scheduled multi-task job deployed from a Git-backed bundle to two targets, and you can diagnose a slow stage in the Spark UI.

Week 8: You rebuilt the pipeline from scratch, scored at least 80 percent on 40 original practice questions, and have no domain below 70 percent.