Home / data-analytics / Microsoft Certified: Azure Data Fundamentals (DP-900) / Cheat Sheet
Microsoft Certified: Azure Data Fundamentals (DP-900)

DP-900 Cheat Sheet

DP-900 Tests Picking the Right Data Category and Azure Service — Not Building Them

A 45-minute fundamentals exam for anyone starting with data on Azure. Most items ask you to classify data or a workload, then name the matching service or role; configuration depth is not expected.

Check Your Readiness →
Among the harder certs
Avg: Not published by Microsoft
Pass: 750 / 1000
Most candidates understand Microsoft Certified: Azure Data Fundamentals (DP-900) concepts — and still fail. This exam tests how you apply knowledge under pressure.

DP-900 Domain Map (skills measured as of July 21, 2026)

Questions are short and definitional: a description of data, a workload or a requirement, and you choose the category, service, API or visual. The current outline names Microsoft Fabric and Azure Databricks for large-scale analytics; Azure Synapse Analytics is no longer named. Question count not published.

  1. 01
    Core data concepts (25–30%) — structured vs semi-structured data, file formats, OLTP vs analytics, data roles
  2. 02
    Relational data on Azure (20–25%) — keys, normalization, SQL statement types, Azure SQL family, open-source databases
  3. 03
    Non-relational data on Azure (15–20%) — Blob tiers, Data Lake Storage Gen2, Azure Files, Table storage, Cosmos DB APIs
  4. 04
    Analytics workloads (25–30%) — warehouse, lake and lakehouse, Fabric and Databricks, streaming, Power BI

Wrong instinct vs correct approach

An existing MongoDB application must move to Azure with minimal code changes
✕ Wrong instinct

Rewrite it for the Cosmos DB NoSQL API

✓ Correct approach

Choose Azure Cosmos DB for MongoDB: it speaks the MongoDB wire protocol, so drivers and queries keep working. The NoSQL API is the default for new apps; Cassandra and Gremlin APIs serve column-family and graph workloads.

Monthly reports must stay available on demand at the lowest storage cost
✕ Wrong instinct

Move the reports to the archive tier

✓ Correct approach

Archive blobs must be rehydrated, which takes hours, before they can be read. The cool or cold tier lowers storage cost while keeping data online; archive suits data that is rarely needed and never urgently.

A 5 TB export arrives every night, and reports refresh each morning
✕ Wrong instinct

Use stream processing because the volume is large

✓ Correct approach

Bounded data with no low-latency requirement is a batch workload. Streaming fits unbounded events processed as they arrive, such as telemetry ingested by Event Hubs and analysed with Stream Analytics, Spark or a Fabric eventhouse.

A new cloud-born app needs a relational database with the least administration
✕ Wrong instinct

Run SQL Server on Azure VMs for full control

✓ Correct approach

Azure SQL Database is the fully managed PaaS choice with the lowest admin effort, with elastic pools for many databases. Managed Instance suits lift-and-shift needing instance features; on VMs, patching stays with the customer.

Raw JSON, images and logs must be stored before anyone decides how to model them
✕ Wrong instinct

Load everything straight into a data warehouse

✓ Correct approach

Warehouses hold modelled relational tables. Raw multi-format files belong in a data lake, where schema is applied on read, or a lakehouse that adds Delta tables and SQL access on top, such as OneLake in Microsoft Fabric.

Know these cold

  • ▸ ACID defines OLTP transactions — tomic, consistent, isolated, durable, with many small concurrent writes
  • ▸ ETL transforms before loading; ELT loads first and transforms inside the target store
  • ▸ Primary keys are unique and never null; foreign keys reference them and may repeat
  • ▸ Normalization stores each fact once; analytical star schemas denormalize to cut joins
  • ▸ Views store a query, not data; stored procedures run parameterised logic on the server
  • ▸ DBA owns backups and security; engineer builds pipelines; analyst builds Power BI reports
  • ▸ Blob tiers run hot, cool, cold, archive — heaper storage means costlier, slower reads
  • ▸ Cosmos DB throughput is measured in request units; reads, writes and queries all consume RUs
  • ▸ Table storage finds entities by partition key and row key, with no joins or foreign keys
  • ▸ Event Hubs only ingests events; Stream Analytics, Spark or an eventhouse does the analysis

Can you answer these without checking your notes?

In this scenario: "An existing MongoDB application must move to Azure with minimal code changes" — what should you do first?
Choose Azure Cosmos DB for MongoDB: it speaks the MongoDB wire protocol, so drivers and queries keep working. The NoSQL API is the default for new apps; Cassandra and Gremlin APIs serve column-family and graph workloads.
In this scenario: "Monthly reports must stay available on demand at the lowest storage cost" — what should you do first?
Archive blobs must be rehydrated, which takes hours, before they can be read. The cool or cold tier lowers storage cost while keeping data online; archive suits data that is rarely needed and never urgently.
In this scenario: "A 5 TB export arrives every night, and reports refresh each morning" — what should you do first?
Bounded data with no low-latency requirement is a batch workload. Streaming fits unbounded events processed as they arrive, such as telemetry ingested by Event Hubs and analysed with Stream Analytics, Spark or a Fabric eventhouse.

Common Exam Mistakes — What candidates get wrong

Classifying data by its file type instead of its organisation

A CSV with a header row and identical fields is structured. JSON, XML and YAML are semi-structured because records carry their own keys and can differ. Images, audio, video and documents are unstructured. Storage location never decides the category.

Mixing up row-based Avro with columnar Parquet

Avro stores whole rows with the schema embedded, which suits serialisation and write-heavy ingestion. Parquet and ORC store data by column, so analytics engines read only the columns a query needs and compress better.

Confusing DELETE with DROP and the SQL statement families

DELETE is DML and removes rows while the table survives; DROP TABLE is DDL and removes the definition. SELECT, INSERT and UPDATE are DML, CREATE and ALTER are DDL, and GRANT, DENY and REVOKE are DCL.

Using Blob storage where servers need a mapped drive

Blob storage is object storage reached over HTTP. A share that servers mount as a drive over SMB or NFS is Azure Files. Data Lake Storage Gen2 is a storage account with hierarchical namespace enabled, not a separate service.

Using a calculated column where a Power BI measure is needed

Calculated columns are computed per row at refresh and ignore slicers. Measures are DAX calculations evaluated at query time for each filter context. Dashboards are single-page canvases of pinned tiles built in the Power BI service, not in Desktop.

Resources to help you pass Azure Data Fundamentals DP-900 on your first attempt

Check whether you can match each data type, workload and Azure service the DP-900 way.