File Info
| Exam | Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB (beta) |
| Number | DP-420 |
| File Name | Microsoft.DP-420.VCEplus.2022-03-13.51q.tqb |
| Size | 8 MB |
| Posted | Mar 13, 2022 |
| Download | Microsoft.DP-420.VCEplus.2022-03-13.51q.tqb |
How to open VCEX & EXAM Files?
Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.
Coupon: MASTEREXAM
With discount: 20%
Demo Questions
Question 1
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?
- 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.
Correct answer: C
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 discoverthat 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 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 discoverthat 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
Question 2
You need to select the partition key for con-iot1. The solution must meet the IoT telemetry requirements.
What should you select?
- the timestamp
- the humidity
- the temperature
- the device ID
Correct answer: 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 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
Question 3
You configure multi-region writes for account1.
You need to ensure that App1 supports the new configuration for account1. The solution must meet the business requirements and the product catalog requirements.
What should you do?
- Set the default consistency level of account1 to bounded staleness.
- Create a private endpoint connection.
- Modify the connection policy of App1.
- Increase the number of request units per second (RU/s) allocated to the con-product and con-productVendor containers.
Correct answer: D
Explanation:
App1 queries the con-product and con-productVendor containers. Note: Request unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB. Scenario: Develop an app named App1 that will run from all locations and query the data in account1. Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1. Whenever there are multiple solutions for a requirement, select the solution that provides the best performance, as long as there are no additional costs associated. Incorrect Answers: A: Bounded staleness relates to writes. App1 only do reads. Note: 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. Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels App1 queries the con-product and con-productVendor containers.
Note: Request unit is a performance currency abstracting the system resources such as CPU, IOPS, and memory that are required to perform the database operations supported by Azure Cosmos DB.
Scenario:
Develop an app named App1 that will run from all locations and query the data in account1.
Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
Whenever there are multiple solutions for a requirement, select the solution that provides the best performance, as long as there are no additional costs associated.
Incorrect Answers:
A:
Bounded staleness relates to writes. App1 only do reads.
Note: 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.
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels
