top of page

DP-900 practice exam

Microsoft Azure Data Fundamentals

Timed practice exams for DP-900 on the real exam's 45 minute limit, with 50 questions in each full exam. Microsoft publishes no question count for DP-900, so 50 questions is the site's practice setting. Every question is original and every option is explained. Your score is broken down by the sections Microsoft publishes, so you see what to study next. The question bank holds hundreds of practice questions.

Exam facts

  • Time limit: 45 minutes [1]
  • Passing score: 700 or greater [2]
  • Exam languages (real exam): English, Arabic (Saudi Arabia), Chinese (Simplified), Chinese (Traditional), French, German, Indonesian (Indonesia), Italian, Japanese, Korean, Portuguese (Brazil), Russian, Spanish [1]

Tokens: 1 for $4.99, 5 for $14.99, 10 for $24.99 or 25 for $49.99. One token runs a full timed DP-900 practice exam, and every shorter session on that exam is then free. The Unlimited pass is $149.99 for a year of every practice session on every exam.

Get tokens

Exam sections and weights

Microsoft publishes these sections and objectives for DP-900, quoted here as Microsoft words them. [2]

Section 1: Describe core data concepts, 25 to 30% of the exam

  • "Describe the features of structured data"
  • "Describe the features of semi-structured data"
  • "Describe the features of unstructured data"
  • "Describe common formats for data files"
  • "Describe features of common data stores including databases"
  • "Identify Azure datastores for common use cases"
  • "Describe features of transactional workloads"
  • "Describe features of analytical workloads"
  • "Describe responsibilities for database administrators"
  • "Describe responsibilities for data engineers"
  • "Describe responsibilities for data analysts"

Section 2: Identify considerations for relational data on Azure, 20 to 25% of the exam

  • "Identify features of relational data"
  • "Describe normalization and why it is used"
  • "Identify common structured query language (SQL) statements"
  • "Identify common database objects"
  • "Describe the Azure SQL family of products, including Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure Virtual Machines"
  • "Identify Azure database services for open-source database systems"

Section 3: Describe considerations for working with non-relational data on Azure, 15 to 20% of the exam

  • "Describe features of Azure Blob storage"
  • "Describe features of Azure Files"
  • "Describe features of Azure Table storage"
  • "Identify use cases for Azure Cosmos DB"
  • "Describe Azure Cosmos DB APIs"

Section 4: Describe an analytics workload, 25 to 30% of the exam

  • "Describe considerations for data ingestion and processing"
  • "Describe options for analytical data stores"
  • "Describe Microsoft cloud services for large-scale analytics, including Azure Databricks and Microsoft Fabric"
  • "Describe the difference between batch and streaming data"
  • "Identify Microsoft cloud services for real-time analytics"
  • "Identify the capabilities of Power BI"
  • "Describe features of data models in Power BI"
  • "Identify appropriate visualizations for data"

Sample questions

Three questions from the DP-900 practice bank, with the answer and why each option is right or wrong.

Question 1

A payroll system keeps one record per employee, and every record holds the same fields: EmployeeID, FullName, HireDate and Salary. How should this data be classified?

  • A. Unstructured data
  • B. Semi-structured data
  • C. Structured data
  • D. Vector data

Answer: C. Structured data follows a fixed schema, so every record carries the same fields. [3]

  • A. Wrong. Unstructured data, such as documents, images or audio, has no specific structure. The payroll records have named fields.
  • B. Wrong. Semi-structured data lets fields vary from one record to the next, and no payroll record here differs from the others.
  • C. Right. Every payroll record carries the same four fields, the fixed schema that marks structured data.
  • D. Wrong. The payroll fields hold names, dates and amounts for each employee. AI applications use vector data to find similar content, and the payroll system has no such need.

Question 2

A hotel wants PassportNo as the primary key of its Guest table. Every passport number is different, but some guests don't give one at check-in, so their rows would leave PassportNo empty. Why can't PassportNo be the primary key?

  • A. Other tables can't reference a column that serves as a primary key.
  • B. Every column in a primary key must be defined as not null.
  • C. Primary key values have to come from an identity column that the database fills in.
  • D. A primary key has to combine two or more columns.

Answer: B. Every column in a primary key constraint must be not null, so a column that some rows leave empty can't be the key. [4]

  • A. Wrong. Columns in other tables do reference primary key values. That has no bearing on the guests whose PassportNo would be empty.
  • B. Right. All columns in a primary key constraint must be defined as not null. Guests who give no passport number would leave PassportNo empty, so the column can't hold the key.
  • C. Wrong. Primary keys are often defined on an identity column, but nothing makes that a requirement. The problem with PassportNo is the guests who leave it empty.
  • D. Wrong. A primary key can be one column or a combination of columns. The obstacle in the stem is the empty values, not the number of columns.

Question 3

A team keeps two kinds of blobs in one Azure Blob Storage account that uses the default flat namespace: signed supplier contracts and public product images. Only the legal staff may read the contracts. How should the team arrange the blobs so that it can set who reads each kind?

  • A. Put each kind in its own container and set access on each container
  • B. Keep both kinds in one container and move the contracts to the Archive tier
  • C. Keep both kinds in one container and store the contracts as append blobs
  • D. Put each kind in its own virtual folder in one container and set access on each folder

Answer: A. In Azure Blob Storage, access to blobs is set per container. Virtual folders in a flat namespace carry no access control of their own. [5]

  • A. Right. Who can read and write blobs is controlled at the container level, so a container of its own for the contracts lets the team limit reads to the legal staff.
  • B. Wrong. Access tiers balance access latency against storage cost. The team's need is about who may read the contracts, and a tier doesn't decide that.
  • C. Wrong. Choosing a blob type doesn't separate readers. Read access is set at the container level, and both kinds would still share one container.
  • D. Wrong. In a flat namespace a folder is only a "/" character in each blob name. Those folders are virtual, and the team can't control access at folder level.

Practice for DP-900 on ExamSens.ai

ExamSens.ai is not authorized, endorsed or sponsored by Microsoft.

References

[1] https://learn.microsoft.com/en-us/credentials/certifications/azure-data-fundamentals/

[2] https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/dp-900

[3] https://learn.microsoft.com/en-us/training/modules/explore-core-data-concepts/2-data-formats

[4] https://learn.microsoft.com/en-us/sql/relational-databases/tables/primary-and-foreign-key-constraints?view=sql-server-ver17

[5] https://learn.microsoft.com/en-us/training/modules/explore-provision-deploy-non-relational-data-services-azure/2-azure-blob-storage

bottom of page