A healthcare application stores patient records with patientId, facilityId, and recordType. The system must support queries by patient and by facility. Writes are evenly distributed across patients, but some facilities have many more patients than others. Which partition key strategy best balances query efficiency and write distribution?

Use a synthetic partition key combining patientId and facilityId.

Use facilityId as the partition key.

Use a hierarchical partition key: /facilityId//patientId.

Use patientId as the partition key and create a separate container with facilityId as the partition key for facility queries.

An e-commerce application stores orders and order line items in separate containers. A user's checkout process reads the user's cart, creates an order, and inserts multiple line items. The team wants to use a transactional batch to ensure all inserts succeed or fail together. Which partition key design enables this transaction to target a single logical partition?

Use a synthetic key of userId_orderId for both containers

Use userId as the partition key for both the orders and order line items containers

Use userId for orders and orderId for line items

Use orderId as the partition key for both containers

An e-commerce platform stores order documents with fields: customerId (high cardinality), orderDate (date), and status (string). The most common query is 'get all orders for a customer within a date range'. Writes are evenly distributed across customers. Which partition key strategy best balances query efficiency and write distribution?

Use customerId as the partition key.

Use orderDate as the partition key.

Use status as the partition key.

Use a synthetic key combining customerId and orderDate.

A container stores order items. Each order has an OrderId, a CustomerId, and an OrderDate. The application frequently queries all items for a specific order, and also queries all orders for a customer. Which partition key is most suitable?

A synthetic key combining CustomerId and OrderId

A healthcare platform stores patient records. Each patient belongs to a clinic, and each clinic belongs to a hospital group. The application must support: (1) transactions that span multiple records for a single patient, (2) queries for all patients in a clinic, and (3) queries for all patients in a hospital group. You need to design a partition key that supports all three patterns with minimal cross-partition queries. What should you choose?

Single partition key: hospitalGroupId

Hierarchical partition key: patientId, clinicId, hospitalGroupId

Hierarchical partition key: hospitalGroupId, clinicId, patientId

Single partition key: patientId

Microsoft Certified:Azure Cosmos DB Developer Specialty

Domain 1Objective 2

Design a Data Partitioning Strategy for Azure Cosmos DB for NoSQL DP-420 Practice Questions (Page 4)

Part of the Design and implement data models domain, which makes up ~45% of our current practice bank. Microsoft does not publish an official question count, but from its 100-minute exam (~40–65 total, ~18–29 in this domain), expect 3–4 from this objective — we provide 28 practice questions to prepare you well beyond it. (estimate)

28questions here

6free pages

9concepts

Questions 16–20

16expert · hard
A healthcare application stores patient records with patientId, facilityId, and recordType. The system must support queries by patient and by facility. Writes are evenly distributed across patients, but some facilities have many more patients than others. Which partition key strategy best balances query efficiency and write distribution?
Select an answer first
17application · medium
An e-commerce application stores orders and order line items in separate containers. A user's checkout process reads the user's cart, creates an order, and inserts multiple line items. The team wants to use a transactional batch to ensure all inserts succeed or fail together. Which partition key design enables this transaction to target a single logical partition?
Select an answer first
18application · medium
An e-commerce platform stores order documents with fields: customerId (high cardinality), orderDate (date), and status (string). The most common query is 'get all orders for a customer within a date range'. Writes are evenly distributed across customers. Which partition key strategy best balances query efficiency and write distribution?
Select an answer first
19foundation · easy
A container stores order items. Each order has an OrderId, a CustomerId, and an OrderDate. The application frequently queries all items for a specific order, and also queries all orders for a customer. Which partition key is most suitable?
Select an answer first
20expert · hard
A healthcare platform stores patient records. Each patient belongs to a clinic, and each clinic belongs to a hospital group. The application must support: (1) transactions that span multiple records for a single patient, (2) queries for all patients in a clinic, and (3) queries for all patients in a hospital group. You need to design a partition key that supports all three patterns with minimal cross-partition queries. What should you choose?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DP-420

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “DP-420” is a trademark of its owner, used for identification only.

Design a Data Partitioning Strategy for Azure Cosmos DB for NoSQL DP-420 Practice Questions (Page 4)

Questions 16–20

A container stores order items. Each order has an OrderId, a CustomerId, and an OrderDate. The application frequently queries all items for a specific order, and also queries all orders for a customer. Which partition key is most suitable?

Keep studying — Design and implement data models