Cosmos DB overview and use cases in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Cosmos DB Consistency Levels

Which Cosmos DB consistency level guarantees the highest data consistency but may impact latency and availability?

A Strong consistency

B Bounded staleness consistency

C Session consistency

D Eventual consistency

💡 Hint

Think about the trade-off between consistency and latency in distributed databases.

Strong consistency ensures that reads always return the most recent committed write, providing the highest data consistency. However, it can increase latency and reduce availability in distributed systems.

❓ Architecture

intermediate

Choosing Cosmos DB API for a Use Case

You need to build a globally distributed application that stores JSON documents and requires rich querying capabilities. Which Cosmos DB API should you choose?

A SQL (Core) API

B Cassandra API

C Gremlin API

D Table API

💡 Hint

Consider which API is optimized for JSON document storage and querying.

The SQL (Core) API is designed for JSON document storage and supports rich SQL-like queries, making it ideal for document-based applications.

❓ service_behavior

advanced

Impact of Partition Key Choice on Cosmos DB Performance

What is the most likely impact of choosing a partition key with low cardinality in Cosmos DB?

A Automatic scaling of storage without performance impact

B Hot partition causing throttling and reduced performance

C Improved write throughput due to even data distribution

D Increased consistency across regions

💡 Hint

Think about how data distribution affects load balancing in Cosmos DB.

A partition key with low cardinality causes many requests to target the same partition, creating a hot partition that leads to throttling and reduced performance.

❓ security

advanced

Securing Access to Cosmos DB Data

Which method provides the most secure way to grant an application read-only access to a Cosmos DB container without exposing the master key?

A Use the master key directly in the application code

B Enable IP firewall rules only

C Use the primary key with read permissions

D Create a read-only resource token scoped to the container

💡 Hint

Consider least privilege and key exposure risks.

Resource tokens provide scoped, time-limited access to specific resources without exposing the master key, following the principle of least privilege.

✅ Best Practice

expert

Optimizing Cosmos DB for Global Distribution and Latency

You have a Cosmos DB account replicated in multiple regions worldwide. To minimize read latency for users globally, which configuration should you enable?

A Enable multi-master write regions with single write region

B Use strong consistency across all regions

C Configure preferred regions for read requests in the SDK

D Disable automatic failover

💡 Hint

Think about how the SDK can direct read requests to the nearest region.

Configuring preferred regions in the Cosmos DB SDK directs read requests to the nearest region, reducing latency for global users.

Practice

1. What is the main benefit of using Azure Cosmos DB for global applications?

easy

A. It provides low latency and high availability worldwide.

B. It only supports SQL queries.

C. It requires manual scaling of resources.

D. It is designed for local, single-region apps only.

Solution

1. Step 1: Understand Cosmos DB's global distribution

   Cosmos DB is designed to replicate data across multiple regions to provide fast access and high availability.

2. Step 2: Identify the benefit for global apps

   This replication ensures low latency and continuous availability for users worldwide.

3. Final Answer:

   It provides low latency and high availability worldwide. -> Option A

4. Quick Check:

   Global apps need low latency and high availability = A [OK]

Hint: Global apps need fast, reliable data access worldwide [OK]

Common Mistakes:

• Thinking Cosmos DB only supports SQL
• Assuming manual scaling is required
• Believing it's for single-region use only

2. Which of the following is a supported API model in Azure Cosmos DB?

easy

A. Oracle SQL API

B. MySQL API

C. MongoDB API

D. PostgreSQL API

Solution

1. Step 1: Recall Cosmos DB supported APIs

   Azure Cosmos DB supports multiple APIs including SQL, MongoDB, Cassandra, Gremlin, and Table APIs.

2. Step 2: Identify the correct API from options

   MongoDB API is officially supported, while Oracle, MySQL, and PostgreSQL APIs are not.

3. Final Answer:

   MongoDB API -> Option C

4. Quick Check:

   MongoDB API is supported by Cosmos DB = B [OK]

Hint: Remember Cosmos DB supports MongoDB API, not Oracle or MySQL [OK]

Common Mistakes:

• Confusing Cosmos DB with relational databases
• Assuming all SQL-based APIs are supported
• Selecting unsupported database APIs

3. Given this Cosmos DB use case: A global e-commerce app needs to store product catalog data with fast reads and writes worldwide. Which Cosmos DB feature best supports this?

medium

A. Local SSD caching only

B. Multi-region replication with automatic failover

C. Single-region write with manual backups

D. Manual sharding without replication

Solution

1. Step 1: Analyze the requirement for global fast reads and writes

   The app needs data available quickly everywhere and must handle writes globally.

2. Step 2: Match Cosmos DB features to requirements

   Multi-region replication with automatic failover allows writes and reads in multiple regions with high availability and low latency.

3. Final Answer:

   Multi-region replication with automatic failover -> Option B

4. Quick Check:

   Global fast reads/writes need multi-region replication = C [OK]

Hint: Global writes need multi-region replication with failover [OK]

Common Mistakes:

• Choosing single-region write limits scalability
• Confusing caching with replication
• Ignoring automatic failover importance

4. You created a Cosmos DB container but notice your app experiences high latency when accessing data globally. What is the most likely cause?

medium

A. The container is configured with single-region write and no multi-region replication.

B. The container uses multi-region replication with automatic failover.

C. The container has indexing enabled for all properties.

D. The container is using the MongoDB API.

Solution

1. Step 1: Understand latency causes in global apps

   High latency often happens if data is only written and read from one region far from users.

2. Step 2: Identify configuration causing latency

   Single-region write without multi-region replication means users far from that region experience delays.

3. Final Answer:

   The container is configured with single-region write and no multi-region replication. -> Option A

4. Quick Check:

   Single-region write without replication causes high latency = A [OK]

Hint: Check if multi-region replication is enabled to reduce latency [OK]

Common Mistakes:

• Assuming indexing causes latency
• Confusing API choice with latency issues
• Believing multi-region replication increases latency

5. A company wants to build a globally distributed IoT app that collects sensor data continuously and requires automatic scaling and low latency. Which Cosmos DB feature combination best fits this use case?

hard

A. Gremlin API with no replication and fixed throughput

B. Single API support with manual scaling and single-region writes

C. Table API with single-region replication and manual failover

D. Multi-model support with multi-region writes and automatic scaling

Solution

1. Step 1: Identify IoT app requirements

   The app needs to handle continuous data ingestion globally with automatic scaling and low latency.

2. Step 2: Match Cosmos DB features to these needs

   Multi-model support allows flexible data types; multi-region writes enable global data ingestion; automatic scaling handles variable loads.

3. Final Answer:

   Multi-model support with multi-region writes and automatic scaling -> Option D

4. Quick Check:

   IoT needs global writes and scaling = D [OK]

Hint: IoT needs multi-region writes plus auto scaling [OK]

Common Mistakes:

• Choosing single-region writes limits global data ingestion
• Ignoring automatic scaling for variable IoT loads
• Selecting APIs without replication support