Courseiva

DP-900 Practice Question: Describe considerations for working with non-relational data on Azure

Which TWO Azure services can be used to store non-relational data? (Choose two.)

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Azure Cosmos DB

Azure Cosmos DB (A) is correct because it is Microsoft's globally distributed, multi-model NoSQL database service that natively stores non-relational data such as documents, key-value pairs, graphs, and column-family data. Azure Table Storage (E) is also correct because it is a NoSQL key-attribute store designed for storing large amounts of non-relational structured data (entities with partition key and row key) at low cost. Azure SQL Database (B) is a relational PaaS database engine using T-SQL, so it stores relational data, not non-relational. Azure Synapse Analytics (C) is an analytics service built on relational MPP (massively parallel processing) SQL pools and Spark, primarily for data warehousing and analytics rather than non-relational storage. Azure Database for MySQL (D) is a managed relational MySQL database, so it stores relational data in tables with schemas and foreign keys.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Azure Cosmos DB

    Why this is correct

    Azure Cosmos DB is a globally distributed, multi-model NoSQL database supporting document, key-value, graph and column-family APIs. Its schema-agnostic design satisfies the non-relational requirement, unlike Azure SQL Database, which enforces relational tables, schemas and joins.

  • ✗

    Azure SQL Database

    Why it's wrong here

    Azure SQL Database is a relational engine requiring predefined schemas and SQL tables, so it cannot store non-relational data. It tempts as a familiar managed PaaS database, and would be right when the workload needs relational modelling, joins and Transact-SQL querying over structured data.

  • ✗

    Azure Synapse Analytics

    Why it's wrong here

    Azure Synapse Analytics is an analytics workspace with SQL and Spark pools; it queries data rather than serving as a non-relational store. It suits large-scale analytical workloads, whereas non-relational storage requires services such as Azure Cosmos DB or Azure Table Storage.

  • ✗

    Azure Database for MySQL

    Why it's wrong here

    MySQL stores data in relational tables with a fixed schema, enforced by primary and foreign keys, so it cannot hold non-relational data. It tempts because it is a managed Azure database service, and would be correct when the workload needs a relational engine with SQL querying and ACID transactions.

  • ✓

    Azure Table Storage

    Why this is correct

    Azure Table Storage is a key-value NoSQL store holding schemaless entities, so it satisfies the non-relational requirement. Unlike relational engines, it stores data as flexible property sets without fixed schemas, joins or foreign keys, making it suitable for semi-structured workloads.

About these practice questions

One of 851 original DP-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This DP-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-900 exam.