Halloween Sale Special Limited Time 75% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code = drift75

Home
Microsoft
Microsoft Certified: Azure Cosmos DB Developer Specialty
DP-420
Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB Questions and Answers

Pass the Microsoft Certified: Azure Cosmos DB Developer Specialty DP-420 Questions and answers with ExamsMirror

Practice at least 50% of the questions to maximize your chances of passing.

Exam DP-420 Premium Access

View all detail and faqs for the DP-420 exam

Go to Exam

782 Students Passed

93% Average Score

94% Same Questions

Viewing page 7 out of 7 pages

Viewing questions 61-70 out of questions

Questions # 61:

You need to recommend indexes for con-product and con-productVendor. The solution must meet the product catalog requirements and the business requirements.

Which type of index should you recommend for each container? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Question # 61

Options:

Answer

Answer:

Questions # 62:

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.

Question # 62

Options:

Answer

Answer:

Questions # 63:

You need to provide a solution for the Azure Functions notifications following updates to con-product. The solution must meet the business requirements and the product catalog requirements.

Which two actions should you perform? Each correct answer presents part of the solution.

NOTE: Each correct selection is worth one point.

Options:

Configure the trigger for each function to use a different leaseCollectionPrefix

Configure the trigger for each function to use the same leaseCollectionNair.e

Configure the trigger for each function to use a different leaseCollectionName

Configure the trigger for each function to use the same leaseCollectionPrefix

Answer

A, C

Explanation

leaseCollectionPrefix: when set, the value is added as a prefix to the leases created in the Lease collection for this Function. Using a prefix allows two separate Azure Functions to share the same Lease collection by using different prefixes.

Scenario: Use Azure Functions to send notifications about product updates to different recipients.

Trigger the execution of two Azure functions following every update to any document in the con-product container.

[Reference:, https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-cosmosdb-v2-trigger, , ]

Questions # 64:

You need to identify which connectivity mode to use when implementing App2. The solution must support the planned changes and meet the business requirements.

Which connectivity mode should you identify?

Options:

Direct mode over HTTPS

Gateway mode (using HTTPS)

Direct mode over TCP

Answer

Explanation

Scenario: Develop an app named App2 that will run from the retail stores and query the data in account2. App2 must be limited to a single DNS endpoint when accessing account2.

By using Azure Private Link, you can connect to an Azure Cosmos account via a private endpoint. The private endpoint is a set of private IP addresses in a subnet within your virtual network.

When you ' re using Private Link with an Azure Cosmos account through a direct mode connection, you can use only the TCP protocol. The HTTP protocol is not currently supported.

[Reference:, https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-configure-private-endpoints, , ]

Questions # 65:

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

What should you select?

Options:

the timestamp

the humidity

the temperature

the device ID

Answer

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, , ]

Questions # 66:

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?

Options:

Enable time to live for the con-product container.

Set the default consistency level of account1 to strong.

Set the default consistency level of account1 to bounded staleness.

Add a custom indexing policy to the con-product container.

Answer

Explanation

Bounded staleness is frequently chosen by globally distributed applications that expect low write latencies but require total global order guarantee. Bounded staleness is great for applications featuring group collaboration and sharing, stock ticker, publish-subscribe/queueing etc.

Scenario: Application updates in con-product frequently cause HTTP status code 429 " Too many requests " . You discover that the 429 status code relates to excessive request unit (RU) consumption during the updates.

[Reference:, https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels, , , ]

Questions # 67:

You need to implement a solution to meet the product catalog requirements.

What should you do to implement the conflict resolution policy.

Options:

Remove frequently changed field from the index policy of the con-product container.

Disable indexing on all fields in the index policy of the con-product container.

Set the default consistency level for account1 to eventual.

Create a new container and migrate the product catalog data to the new container.

Answer

Questions # 68:

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

You have an Azure Cosmos DB Core (SQL) API account named account 1 that uses autoscale throughput.

You need to run an Azure function when the normalized request units per second for a container in account1 exceeds a specific value.

Solution: You configure an Azure Monitor alert to trigger the function.

Does this meet the goal?

Options:

Yes

Answer

Explanation

You can set up alerts from the Azure Cosmos DB pane or the Azure Monitor service in the Azure portal.

Note: Alerts are used to set up recurring tests to monitor the availability and responsiveness of your Azure Cosmos DB resources. Alerts can send you a notification in the form of an email, or execute an Azure Function when one of your metrics reaches the threshold or if a specific event is logged in the activity log.

[Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/create-alerts, , ]

Questions # 69:

You have an Azure Cosmos DB account named account1 that has a default consistency level of session.

You have an app named App1.

You need to ensure that the read operations of App1 can request either bounded staleness or consistent prefix consistency.

What should you modify for each consistency level? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Question # 69

Options:

Answer

Answer:

Explanation

Box 1 = The request level options

Azure Cosmos DB offers five well-defined consistency levels: strong, bounded staleness, session, consistent prefix and eventual. You can configure the default consistency level on your Azure Cosmos DB account at any time2. The default consistency level applies to all databases and containers under that account1. You can also override the default consistency level for a specific request by using the request options2.

Box 2 = The request level options

To modify the consistency level of a read operation in Azure Cosmos DB, you can use request-level options to override the account ' s default consistency setting. Therefore, to ensure that the read operations of App1 can request either consistent prefix or session consistency, you need to modify the request-level options for each operation. Reference: - https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

Questions # 70:

You have an Azure Cosmos OB for NoSQL account configured for global distribution across four regions. At connection time, the SQL SDK needs to identify the optimal endpoint for reading and writing. Which two factors can influence the SDK? Each correct answer presents a complete solution NOTE- Each correct selection is worth one point.