A company runs a global e-commerce platform on Azure Cosmos DB. They have a single container that stores both product catalog data and per-user shopping carts. The product catalog is read-heavy and experiences predictable traffic, while shopping carts are write-heavy and have unpredictable spikes during flash sales. The team wants to optimize resource governance and minimize throttling during flash sales. What should they do?

Split the data into two containers: one for product catalog and one for shopping carts, each with its own provisioned throughput

Use database-level throughput for the container and rely on autoscale to handle the spikes

Keep both data types in one container and use a composite index to improve query performance

Keep both data types in one container and provision a single high RU/s throughput to handle the peak of both workloads

A company is designing an Azure Cosmos DB solution for a production application that requires predictable performance and has a steady, continuous workload. The team needs to ensure that the database can handle a consistent amount of traffic without throttling. Which throughput mode should they choose?

Either mode, as they provide the same performance guarantees

A team is designing an Azure Cosmos DB database for an application with multiple departments. Each department has different throughput needs, and the team wants to manage and scale each department's resources independently. Which design approach provides the most granular control over throughput?

Use a separate database for each department

Use a separate container for each department with container-level throughput

Use a single container with database-level throughput

Use a single database with serverless mode

A team is planning the storage requirements for an Azure Cosmos DB container that will store user profile documents. Each document is approximately 2 KB, and the team expects 10 million users. They also need to account for index overhead. What is the minimum storage capacity they should plan for?

Exactly 20 GB because indexes are stored separately and do not count toward storage

At least 20 GB plus additional storage for indexes

Microsoft Certified:Azure Cosmos DB Developer Specialty

Domain 1Objective 3

Plan and Implement Sizing and Scaling for a Database Created with Azure Cosmos DB DP-420 Practice Questions (Page 1)

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 26 practice questions to prepare you well beyond it. (estimate)

26questions here

6free pages

9concepts

Questions 1–5

1expert · medium
A company runs a global e-commerce platform on Azure Cosmos DB. They have a single container that stores both product catalog data and per-user shopping carts. The product catalog is read-heavy and experiences predictable traffic, while shopping carts are write-heavy and have unpredictable spikes during flash sales. The team wants to optimize resource governance and minimize throttling during flash sales. What should they do?
Select an answer first
2foundation · easy
A company is designing an Azure Cosmos DB solution for a production application that requires predictable performance and has a steady, continuous workload. The team needs to ensure that the database can handle a consistent amount of traffic without throttling. Which throughput mode should they choose?
Select an answer first
3foundation · easy
A team is designing an Azure Cosmos DB database for an application with multiple departments. Each department has different throughput needs, and the team wants to manage and scale each department's resources independently. Which design approach provides the most granular control over throughput?
Select an answer first
4application · medium
A team is planning the storage requirements for an Azure Cosmos DB container that will store user profile documents. Each document is approximately 2 KB, and the team expects 10 million users. They also need to account for index overhead. What is the minimum storage capacity they should plan for?
Select an answer first
5foundation · easy
A developer is estimating the throughput requirements for a new Azure Cosmos DB container that will support an application with a predictable workload. The application performs 500 point reads per second, and each point read has a cost of 1 request unit (RU). The developer also expects 200 small write operations per second, each costing 5 RUs. What is the minimum provisioned throughput (in RU/s) required to support this workload without exceeding the provisioned capacity?
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.

Plan and Implement Sizing and Scaling for a Database Created with Azure Cosmos DB DP-420 Practice Questions (Page 1)

Questions 1–5

A team is designing an Azure Cosmos DB database for an application with multiple departments. Each department has different throughput needs, and the team wants to manage and scale each department's resources independently. Which design approach provides the most granular control over throughput?

A team is planning the storage requirements for an Azure Cosmos DB container that will store user profile documents. Each document is approximately 2 KB, and the team expects 10 million users. They also need to account for index overhead. What is the minimum storage capacity they should plan for?

Keep studying — Design and implement data models