Free DP-420 Exam Braindumps
Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB Questions 6–10 (page: 21)

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

The settings for a container in an Azure Cosmos DB for NoSQL account are configured as shown in the following exhibit.

Which statement describes the configuration of the container?

  1. All items will be deleted after one year.
  2. Items stored in the collection will be retained always, regardless of the items time to live value.
  3. Items stored in the collection will expire only if the item has a time to live value.
  4. All items will be deleted after one hour.

Answer(s): C

Explanation:

When DefaultTimeToLive is -1 then your Time to Live setting is On (No default)
Time to Live on a container, if present and the value is set to "-1", it is equal to infinity, and items don’t expire by default.
Time to Live on an item:
This Property is applicable only if DefaultTimeToLive is present and it is not set to null for the parent container.
If present, it overrides the DefaultTimeToLive value of the parent container.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/time-to-live



View Related Case Study

You have an Azure Cosmos DB for NoSQL account named account1 that is configured for automatic failover. The account1 account has a single read-write region in West US and a read region in East US.
You run the following PowerShell command.
Update-AzCosmosDBAccountFailoverPriority -ResourceGroupName “rg1” -Name “account1” -FailoverPolicy @(“East US”, “West US”)
What is the effect of running the command?

  1. The account will be unavailable to writes during the change
  2. The provisioned throughput for account1 will increase
  3. The account will be configured for multi-region writes
  4. A manual failover will occur

Answer(s): D



View Related Case Study

You have an Azure Cosmos DB for NoSQL account named account1.
You plan to implement a multi-region write scenario.
You enable multi-region writes for account1.
Which two actions should you perform next? Each correct answer presents part of the solution.
Note: Each correct answer is worth one point.

  1. Set ApplicationRegion to the name of the deployed region.
  2. Set UseMultipleWriteLocations to True.
  3. Set consistencyLevel to Eventual.
  4. Update connectionString.

Answer(s): A,B

Explanation:

After enabling multi-region writes in the Azure portal for your Cosmos DB for NoSQL account, your next critical steps involve updating your application code and handling potential data conflicts.
1. Update Application Connection Policy
You must configure your application's SDK to recognize and utilize multiple write locations. Without this, the application may still route all write traffic to a single primary region.
*-> Set UseMultipleWriteLocations to true: This flag informs the SDK that the account is configured for multi-region writes.
*-> Set the ApplicationRegion: Specify the local region where your application instance is deployed.
The SDK will use this to automatically route write and read requests to the nearest available region, reducing latency.
2. Configure Conflict Resolution Policies
3. Review Consistency Levels


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-multi-master



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure Cosmos DB for NoSQL account named account1 that stores IoT telemetry from 50,000 devices across 10 districts. Each device writes one 1-KB document per second. Each document includes three properties named deviceId, districtId, and timestamp.
You need to implement a partitioning solution that meets the following requirements:
● Ensures that queries for a single device remain routable without scanning all the partitions
● Ensures that no single device’s data can exceed the logical partition limit of account1
● Prevents concentrating all the writes for a time window into a single logical partition
What should you configure? To answer, select the appropriate options in the answer area.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




/deviceId as the first level enables device-specific queries to route to the relevant partitions. Adding /timestamp distributes each device’s growing history across logical partitions, each subject to the 20-GB limit. Including the device identifier also distributes simultaneous writes across devices instead of grouping all telemetry for a time window into one logical partition.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/hierarchical-partition-keys?tabs=net-v3%2Cbicep



View Related Case Study

You have an Azure Cosmos DB for NoSQL container named Container1 that has the following configurations:
● Partition key: customerId
● Unique key: /invoiceId
You have the following JSON documents.

You plan to add the JSON documents to Container1.
How many JSON documents can you add to Container1?

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5

Answer(s): E



Viewing page 21 of 61
Viewing questions 101 - 105 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!