Free DP-420 Exam Braindumps
Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB Questions 1–5 (page: 2)

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

You are troubleshooting the current issues caused by the application updates.
Which action can address the application updates issue without affecting the functionality of the application?

  1. Enable time to live for the con-product container.
  2. Set the default consistency level of account1 to strong.
  3. Set the default consistency level of account1 to bounded staleness.
  4. Add a custom indexing policy to the con-product container.

Answer(s): D



View Related Case Study

You need to select the partition key for con-iot1. The solution must meet the IoT telemetry requirements.
What should you select?

  1. the timestamp
  2. the humidity
  3. the temperature
  4. the device ID

Answer(s): D

Explanation:

The partition key is what will determine how data is routed in the various partitions by Cosmos DB and needs to make sense in the context of your specific scenario. The IoT Device ID is generally the "natural" partition key for IoT applications.
Scenario: The iotdb database will contain two containers named con-iot1 and con-iot2.
Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.


Reference:

https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/iot-using-cosmos-db



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You plan to implement con-iot1 and con-iot2.
You need to configure the default Time to Live setting for each container. The solution must meet the IoT telemetry requirements.
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:



Box 1: On (3,600 seconds)
Note: Litware identifies the following IoT telemetry requirements:
Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
Box 2: On (no default)
Time to Live on a container (set using DefaultTimeToLive):
* If missing (or set to null), items are not expired automatically.
* If present and the value is set to "-1", it is equal to infinity, and items don’t expire by default.
* If present and the value is set to some non-zero number "n" – items will expire "n" seconds after their last modified time.
Note: Litware identifies the following IoT telemetry requirements:
Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.


Reference:

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



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You need to select the capacity mode and scale configuration for account2 to support the planned changes and meet the business requirements.
What should you select? 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:



Box 1: Provisioned throughput
Provisioned throughput is best suited for workloads with sustained traffic requiring predictable performance. Billing model: Billing is done on a per-hour basis for the RU/s provisioned, regardless of how many RUs were consumed.
Scenario: Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
Note: Azure Cosmos DB is available in two different capacity modes: provisioned throughput and serverless. You can perform the exact same database operations in both modes, but the way you get billed for these operations is radically different.
Box 2: Autoscale throughput on iotdb and throughput sharing across the containers
You can enable autoscale on a single container, or provision autoscale throughput on a database and share it among all the containers in the database.
Cost-effective: Autoscale helps optimize your RU/s usage and cost usage by scaling down when not in use. You only pay for the resources that your workloads need on a per-hour basis.
Incorrect: cannot autoscale on two containers.
Note: Autoscale provisioned throughput in Azure Cosmos DB allows you to scale the throughput (RU/s) of your database or container automatically and instantly.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/throughput-serverless https://docs.microsoft.com/en-us/azure/cosmos-db/sql/how-to-provision-autoscale-throughput



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure Cosmos DB for NoSQL account named account1 that has the disableKeyBasedMetadataWriteAccess property enabled.
You are developing an app named App1 that will be used by a user named DevUser1 to create containers in account1. DevUser1 has a non-privileged user account in the Azure AD tenant.
You need to ensure that DevUser1 can use App1 to create containers in account1.
What should you do? 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:



Box 1: Resource tokens
Resource tokens provide access to the application resources within a database. Resource tokens:
Provide access to specific containers, partition keys, documents, attachments, stored procedures, triggers, and UDFs.
Box 2: Azure Resource Manager API
You can use Azure Resource Manager to help deploy and manage your Azure Cosmos DB accounts, databases, and containers.
Incorrect Answers:
The Microsoft Graph API is a RESTful web API that enables you to access Microsoft Cloud service resources.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/secure-access-to-data https://docs.microsoft.com/en-us/rest/api/resources/



Viewing page 2 of 61
Viewing questions 6 - 10 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!