DP-900 domain - 18% of the exam

Describe Considerations for Working with Non-Relational Data on Azure

Describe Considerations for Working with Non-Relational Data on Azure is 18% of the DP-900 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

48
Practice questions
2
Objectives
18
Easy
30
Medium

Where people go wrong

  • Picking a Cosmos DB API that does not match the workload

    The wrong answers choose a Cosmos DB API without matching it to the workload. An existing Azure Table Storage application is offered the NoSQL API or Cassandra, a MongoDB application is offered the NoSQL API, and a Cassandra application is offered MongoDB or Gremlin. Each compatible API keeps the existing programming model, drivers or query language such as CQL, so a migration takes the matching API: Table, MongoDB or Cassandra. The NoSQL API, which stores JSON documents queried with a SQL-like syntax, is the native choice for new applications.

    See it in a sample question
  • Confusing Blob, Files, Table and Queue storage

    The wrong answers hand a workload to the service next door. Images, video and archives are offered to Azure Files or Table storage, an SMB network drive is offered to Blob containers, and messaging between components is offered to Tables or Blobs. Blob storage holds unstructured objects read through its API and suits streaming media. Azure Files is a mountable SMB share. Table storage holds key/value rows. Queue storage holds messages for asynchronous processing between components.

    See it in a sample question
  • Giving non-relational stores relational features

    The wrong answers credit Table storage or Cosmos DB with relational behaviour: foreign keys enforced between tables, an entity normalised across joined tables, or one fixed column layout defined upfront. Table storage has no foreign keys, relationships, stored procedures or views, and it denormalises data so one row holds an entire entity and rows can differ in their fields. A Cosmos DB container is schema-agnostic, so its items can have entirely different properties and adding a property needs no schema migration.

    See it in a sample question
  • Mixing up block, page and append blobs

    The wrong answers attach one blob type's behaviour to another. Block blobs are offered for virtual machine disks, and append blobs are offered as the type behind a managed disk. Page blobs are optimised for random read and write, which is why Azure uses them for virtual disk storage and stores managed disks as page blobs. Block blobs suit discrete, large binary objects that change infrequently, and append blobs only add blocks to the end, with no update of existing blocks.

    See it in a sample question
  • Replacing global distribution with throughput, caching or copying

    The wrong answers offer other routes to low latency across continents: more throughput in one region, a content delivery network, a browser cache, a manual export and re-import, a scheduled nightly copy, or one primary region that every user reads from. None gives each user a nearby read and write replica. In Cosmos DB, global distribution means adding Azure regions to the account, after which the service replicates data automatically and users read from and write to the nearest regional replica.

    See it in a sample question

Objectives in this domain

Sample questions from this domain

Free sampleDescribe Considerations for Working with Non-Relational Data on Azuremedium

An organisation already runs a production application built on MongoDB and wants to move it to a managed cloud database with minimal code changes. Which Azure Cosmos DB API best fits this migration?

  • AAzure Cosmos DB for NoSQL, the native JSON-document API recommended for new apps
  • BAzure Cosmos DB for Apache Cassandra, compatible with Cassandra and CQL
  • CAzure Cosmos DB for MongoDB, compatible with MongoDB drivers and client libraries Correct
  • DAzure Cosmos DB for Table, using the Azure Table Storage programming model
Cosmos DB for MongoDB lets existing MongoDB apps connect with minimal code changes. Cosmos DB for MongoDB is compatible with MongoDB drivers and client libraries, so an existing MongoDB application can connect without significant code changes.

Why A is wrong: The NoSQL API is recommended for new applications; reusing existing MongoDB code on it would require rewriting against a different query syntax.

Why B is wrong: The Cassandra API suits teams migrating an Apache Cassandra workload, not an existing MongoDB application.

Why C is correct: Correct. Cosmos DB for MongoDB is compatible with MongoDB drivers and client libraries, so an existing MongoDB application can connect without significant code changes.

Why D is wrong: The Table API targets key-value workloads using the Azure Table Storage model, not MongoDB drivers or collections.

Free sampleDescribe Considerations for Working with Non-Relational Data on Azureeasy

A team needs to store large numbers of images, video files, and backup archives so that applications can read and write them through a cloud storage API. Which Azure storage service is designed for this kind of unstructured data?

  • AAzure Blob storage Correct
  • BAzure Files
  • CAzure Table storage
  • DAzure Queue storage
Blob storage is Azure's object store for unstructured data such as images, video, and backups. Azure Blob storage stores massive amounts of unstructured data as binary large objects (blobs) that applications read and write through the Blob storage API, making it the fit for images, video, and archives.

Why A is correct: Correct. Azure Blob storage stores massive amounts of unstructured data as binary large objects (blobs) that applications read and write through the Blob storage API, making it the fit for images, video, and archives.

Why B is wrong: Azure Files provides cloud network file shares mounted over SMB or NFS, not an object store accessed through a Blob API.

Why C is wrong: Table storage holds semi-structured key/value rows, not arbitrary binary objects such as images or video.

Why D is wrong: Queue storage holds messages for asynchronous processing between application components, not large binary files.

Free sampleDescribe Considerations for Working with Non-Relational Data on Azureeasy

Azure Table storage supports foreign keys and enforced relationships between its tables in the same way a relational database does. Is this statement correct?

  • AYes
  • BNo Correct
Table storage has no foreign keys or relationships; it stores denormalised, semi-structured rows. Azure Table storage tables have no concept of foreign keys, relationships, stored procedures, or views, so they cannot enforce relationships the way a relational database does.

Why A is wrong: Answering Yes wrongly treats a Table as a relational table; in reality data is usually denormalised so each row holds the entire entity, and no cross-table relationships are enforced.

Why B is correct: Correct. Azure Table storage tables have no concept of foreign keys, relationships, stored procedures, or views, so they cannot enforce relationships the way a relational database does.

Free sampleDescribe Considerations for Working with Non-Relational Data on Azuremedium

Azure Blob Storage supports three blob types. Which blob type does Azure use to implement virtual disk storage for virtual machines?

  • APage blobs, which are optimized to support random read and write operations Correct
  • BBlock blobs, which store discrete large binary objects that change infrequently
  • CAppend blobs, which only allow new blocks to be added to the end of the blob
  • DArchive blobs, which keep historical data offline at the lowest storage cost
Page blobs back Azure virtual machine disks because they are optimized for random read and write operations. Page blobs are optimized to support random read and write operations, and Azure uses page blobs to implement virtual disk storage for virtual machines.

Why A is correct: Correct. Page blobs are optimized to support random read and write operations, and Azure uses page blobs to implement virtual disk storage for virtual machines.

Why B is wrong: Block blobs are best for discrete, large binary objects that change infrequently, not for the random IO needed by virtual disks.

Why C is wrong: Append blobs only support adding blocks to the end and cannot update existing blocks, so they are unsuitable for virtual disks.

Why D is wrong: Archive describes an access tier for rarely read data, not a blob type used to back virtual machine disks.

Free sampleDescribe Considerations for Working with Non-Relational Data on Azuremedium

A company wants users on different continents to read and write to a database copy near them so response times stay low everywhere. Which Cosmos DB capability addresses this need?

  • AIncreasing the provisioned request units on the single original region so it can serve more global users at once
  • BPlacing a content delivery network in front of the database to cache its responses for users that are far away
  • CGlobal distribution, which replicates data to added Azure regions so users work against the nearest replica Correct
  • DA client-side cache that stores recent results in each user's browser instead of replicating any data
Cosmos DB global distribution replicates data across regions so users work against the nearest replica for low latency. Cosmos DB is built for global distribution: you add Azure regions and the service automatically replicates data so users read from and write to the nearest regional replica, keeping latency low wherever they are.

Why A is wrong: Adding throughput in one region raises how many requests it handles but does not move data closer to distant users, so cross-continent latency is unchanged.

Why B is wrong: A content delivery network caches static content, not live read and write database operations, so it does not give distant users a local database replica.

Why C is correct: Correct. Cosmos DB is built for global distribution: you add Azure regions and the service automatically replicates data so users read from and write to the nearest regional replica, keeping latency low wherever they are.

Why D is wrong: A browser cache does not provide regional read and write replicas; Cosmos DB delivers low latency through server-side regional replication.

Other domains in this exam

See also the DP-900 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.