Practice Questions

---

Question 1

Which scenario is BEST suited for Azure Cosmos DB?

A. Running complex SQL joins across multiple tables
B. Storing structured financial transactions with strict relational constraints
C. Supporting a globally distributed mobile application with low latency
D. Hosting a traditional on-premises file share

✅ Answer: C

Explanation:
Cosmos DB is ideal for globally distributed applications requiring low latency.

---

Question 2

Which type of application benefits MOST from Cosmos DB’s global distribution capabilities?

A. Local desktop application
B. Single-region reporting system
C. Global e-commerce website
D. Batch processing system

✅ Answer: C

Explanation:
Global applications benefit from multi-region replication and low latency.

---

Question 3

Which use case is BEST suited for Cosmos DB?

A. Data warehouse for historical reporting
B. IoT application collecting real-time sensor data
C. Relational database with complex joins
D. File storage for images

✅ Answer: B

Explanation:
Cosmos DB is optimized for high-ingestion, real-time data scenarios like IoT.

---

Question 4

Why is Cosmos DB suitable for real-time personalization scenarios?

A. It enforces strict relational schemas
B. It supports high-latency operations
C. It provides low-latency read/write performance
D. It requires predefined schemas

✅ Answer: C

Explanation:
Low latency enables instant updates and responses for personalization.

---

Question 5

Which application would MOST benefit from Cosmos DB?

A. Payroll system requiring strict ACID compliance across multiple tables
B. Static website hosting images
C. Gaming application storing player state globally
D. Spreadsheet-based reporting system

✅ Answer: C

Explanation:
Gaming apps require low latency, high throughput, and global availability.

---

Question 6

Which scenario is NOT a good fit for Cosmos DB?

A. Global content management system
B. Real-time analytics dashboard
C. Complex relational reporting with joins
D. Social media application

✅ Answer: C

Explanation:
Cosmos DB is not ideal for complex relational queries or joins.

---

Question 7

Which feature of Cosmos DB makes it ideal for microservices architectures?

A. Fixed schema design
B. Independent scalability for each service
C. Requirement for relational constraints
D. Limited throughput options

✅ Answer: B

Explanation:
Each microservice can scale independently using Cosmos DB.

---

Question 8

Which use case involves storing flexible, evolving data structures?

A. Financial ledger system
B. Product catalog with changing attributes
C. Relational reporting system
D. Fixed-schema inventory system

✅ Answer: B

Explanation:
Cosmos DB’s schema-less design supports evolving data models.

---

Question 9

Which scenario best demonstrates Cosmos DB’s high-throughput capabilities?

A. Processing monthly reports
B. Handling millions of real-time user requests
C. Archiving old documents
D. Storing backup files

✅ Answer: B

Explanation:
Cosmos DB is designed for high-throughput, real-time workloads.

---

Question 10

Which Azure service would you choose for a globally distributed application requiring millisecond response times?

A. Azure Blob Storage
B. Azure Files
C. Azure Cosmos DB
D. Azure Table Storage

✅ Answer: C

Explanation:
Cosmos DB is specifically designed for low-latency, globally distributed applications.

---

✅ Quick Exam Takeaways

✔ Cosmos DB = global, low-latency NoSQL database

✔ Best for:

• Global web/mobile apps
• IoT and telemetry
• Gaming
• Real-time personalization
• Microservices

✔ Key strengths:

• Global distribution
• Massive scalability
• Flexible schema
• High throughput

✔ Not ideal for:

• Complex joins
• Strict relational workloads

✔ Exam tip:
👉 If you see “global + real-time + high scale” → think Cosmos DB

---

Go to the DP-900 Exam Prep Hub main page.