Free DP-420 Exam Braindumps
Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB Questions 16–20 (page: 23)

Updated On: 16-Nov-2026
View Related Case Study

You have an Azure Cosmos DB account in the East US Azure region. The account hosts a container named Container1 that has a throughput of 10,000 request units per second (RU/s) and stores 0.5 TB of data.
You plan to make the account available in the West US Azure region and configure Container1 to support reads and writes.
What will be the approximate total costs once the planned changes are complete?

  1. Approximately two times the existing costs for storage and two times the existing costs for throughput
  2. Approximately four times the existing costs for storage and four times the existing costs for throughput
  3. Approximately two times the existing costs for storage and four times the existing costs for throughput
  4. Approximately four times the existing costs for storage and two times the existing costs for throughput

Answer(s): C

Explanation:

Storage Cost Increase
Existing Cost: You pay for 0.5 TB of data stored in your single initial US region.
New Cost: Adding a second region replicates the exact 0.5 TB of data (plus indexes) to the new region. Azure Cosmos DB charges for storage across all associated regions.
Difference: Exactly +100% higher (adding an identical second block of 0.5 TB storage).
Throughput Cost (300% Increase, 4 times the cost):
Provisioned throughput for a single-region write account costs $0.008 per hour per 100 RU/s.
When you enable multi-region writes (allowing reads and writes in both regions), two things happen to your billing:
The standard rate doubles from $0.008 to $0.016 per hour per 100 RU/s across the account.
The provisioned throughput (10,000 RU/s) is duplicated and dedicated to each of your 2 regions


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/optimize-cost-regions



View Related Case Study

You plan to create an Azure Cosmos DB account that will use an integrated cache.
What will prevent you from using an integrated cache?

  1. a user-assigned managed identity
  2. Azure Private Link
  3. a default consistency level of Session
  4. availability zones

Answer(s): B

Explanation:

Integrated cache in Azure Cosmos DB cannot be used in conjunction with Azure Private Link. Private Link provides a private endpoint for securely accessing Azure services without exposing them to the public internet, but it currently does not support integration with the Cosmos DB integrated cache.



View Related Case Study

You are designing an Azure Cosmos DB for NoSQL solution to store data from IoT devices. Writes from the devices will occur every second. Data will be retained indefinitely.
The following is a sample of the data.

You need to select a partition key that meets the following requirements for writes:
-Minimizes the partition skew
-Avoids capacity limits
-Avoids hot partitions
What should you do?

  1. Create a new synthetic key that contains deviceId and timestamp.
  2. Use timestamp as the partition key.
  3. Use sensor1Value as the partition key.
  4. Create a new synthetic key that contains deviceId and deviceManufacturer.

Answer(s): A

Explanation:

Correct:
* Create a new synthetic key that contains deviceId and a random number.
Use a partition key with a random suffix. Distribute the workload more evenly is to append a random number at the end of the partition key value.
When you distribute items in this way, you can perform parallel write operations across partitions.
* Create a new synthetic key that contains deviceId and timestamp.
Concatenate multiple properties of an item.
You can form a partition key by concatenating multiple property values into a single artificial partitionKey property. These keys are referred to as synthetic keys.
For example, consider the following example document:
{
"deviceId": "abc-123",
"date": 2018
}
For the previous document, one option is to set /deviceId or /date as the partition key. Use this option, if you want to partition your container based on either device ID or date. Another option is to concatenate these two values into a synthetic partitionKey property that's used as the partition key.
{
"deviceId": "abc-123",
"date": 2018,
"partitionKey": "abc-123-2018"
Incorrect:
* Create a new synthetic key that contains deviceId and deviceManufacturer.
All the devices could have the same manufacturer.
* Create a new synthetic key that contains deviceId and sensor1Value.
Senser1Value has only two values.
* Use deviceId as the partition key.
* Use deviceManufacturer as the partition key.
All the devices could have the same manufacturer.
* Use sensor1Value as the partition key
* Use timestamp as the partition key.
You will also not like to partition the data on “DateTime”, because this will create a hot partition. Imagine you have partitioned the data on time, then for a given minute, all the calls will hit one partition. If you need to retrieve the data for a customer, then it will be a fan-out query because data may be distributed on all the partitions.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/synthetic-partition-keys https://docs.microsoft.com/en-us/azure/cosmos-db/concepts-limits



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You are developing an application that will connect to an Azure Cosmos DB for NoSQL account.
The web tier of the application will be hosted in five Azure regions.
You need to design a database layout that meets the following requirements:
● Always allows writes, even when a region fails
● Maintains high availability, even when a region fails
● Minimizes costs
In how many regions should the database be configured, and how many regions should be configured as writeable? To answer, select the appropriate options in the answer area.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Two database regions are needed, and both of them should be writable.
Box 1: 2
Deploying in 2 regions handles a single-region outage. Matching all 5 web tier regions is unnecessary and increases costs.
Box 2: 2
Multi-region writes must be enabled so that if one region fails, the remaining region can immediately accept writes without waiting for a failover.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/multi-region-writes



View Related Case Study

You have an Azure Cosmos DB for NoSQL account that uses the default consistency level.
How can the consistency level be modified as part of a query request?

  1. stronger consistency for write operations
  2. weaker consistency for write operations
  3. stronger consistency for read operations
  4. weaker consistency for read operations

Answer(s): D

Explanation:

Override the default consistency level
Clients can override the default consistency level that is set by the service. Consistency level can be set on a per request, which overrides the default consistency level set at the account level.
Consistency can only be relaxed at the SDK instance or request level. To move from weaker to stronger consistency, update the default consistency for the Azure Cosmos DB account.
Note: Overriding the default consistency level only applies to *reads* within the SDK client. An account configured for strong consistency by default will still write and replicate data synchronously to every region in the account.
When the SDK client instance or request overrides this with Session or weaker consistency, reads will be performed using a single replica.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-manage-consistency



Viewing page 23 of 61
Viewing questions 111 - 115 out of 296 questions


Post your Comments and Discuss Microsoft DP-420 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!