Microsoft Designing and Implementing Cloud-Native Applications Using Azure Cosmos DB DP-420 Dumps in PDF

Free Microsoft DP-420 Real Questions (page: 23)


Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Overview
Litware, Inc. is a United States-based grocery retailer. Litware has a main office and a primary datacenter in Seattle. The company has 50 retail stores across the United States and an emerging online presence. Each store connects directly to the internet.
Existing environment. Cloud and Data Service Environments.
Litware has an Azure subscription that contains the resources shown in the following table.

Each container in productdb is configured for manual throughput.
The con-product container stores the company's product catalog data. Each document in con-product includes a con-productVendor value. Most queries targeting the data in con-product are in the following format. SELECT * FROM con-product p WHERE p.con-productVendor = 'name'
Most queries targeting the data in the con-productVendor container are in the following format.
SELECT * FROM con-productVendor pv
ORDER BY pv.creditRating, pv.yearFounded
Existing environment. Current Problems.
Litware identifies the following issues:
-Updates to product categories in the con-productVendor container do not propagate automatically to documents in the con-product container.
-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.
Requirements. Planned Changes
Litware plans to implement a new Azure Cosmos DB for NoSQL account named account2 that will contain a database named iotdb. The iotdb database will contain two containers named con-iot1 and con-iot2.
Litware plans to make the following changes:
-Store the telemetry data in account2.
-Configure account1 to support multiple read-write regions.
-Implement referential integrity for the con-product container.
-Use Azure Functions to send notifications about product updates to different recipients.
-Develop an app named App1 that will run from all locations and query the data in account1.
-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 HTTPS endpoint when accessing account2.
Requirements. Business Requirements
Litware identifies the following business requirements:
-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.
-Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
-Minimize the number of firewall changes in the retail stores.
Requirements. IoT Telemetry Requirements
Litware identifies the following IoT telemetry requirements:
-Write the telemetry data from streamanalytics1 to the con-iot1 container as the data arrives. Use streamanalytics1 to create hopping window aggregated telemetry readings once per hour and write the data to con-iot2.
-Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
-Optimize the partitioning of con-iot1 for queries that support historical data of a specific device.
-Aggregate the telemetry data by device by using streamanalytics1 and write the aggregate data to con-iot2.
-Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.
Requirements. Product Catalog Requirements
Litware identifies the following requirements for the product catalog:
-Implement a custom conflict resolution policy for the product catalog data.
-Minimize the frequency of errors during updates of the con-product container.
-Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
-Trigger the execution of two Azure functions following every update to any document in the con-product container.
-

HOTSPOT (Drag and Drop is not supported)
You have a container in an Azure Cosmos DB for NoSQL account.
You need to use the Azure Cosmos DB SDK to replace a document by using optimistic concurrency.
What should you include in the code? 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: ConsistencyLevel
The ItemRequestOptions Class ConsistencyLevel property gets or sets the consistency level required for the request in the Azure Cosmos DB service.
Azure Cosmos DB offers 5 different consistency levels. Strong, Bounded Staleness, Session, Consistent Prefix and Eventual - in order of strongest to weakest consistency.
Box 2: _etag
The ItemRequestOptions class helped us implement optimistic concurrency by specifying that we wanted the SDK to use the If-Match header to allow the server to decide whether a resource should be updated. The If-Match value is the ETag value to be checked against. If the ETag value matches the server ETag value, the resource is updated.


Reference:

https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.cosmos.itemrequestoptions https://cosmosdb.github.io/labs/dotnet/labs/10-concurrency-control.html




Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Overview
Litware, Inc. is a United States-based grocery retailer. Litware has a main office and a primary datacenter in Seattle. The company has 50 retail stores across the United States and an emerging online presence. Each store connects directly to the internet.
Existing environment. Cloud and Data Service Environments.
Litware has an Azure subscription that contains the resources shown in the following table.

Each container in productdb is configured for manual throughput.
The con-product container stores the company's product catalog data. Each document in con-product includes a con-productVendor value. Most queries targeting the data in con-product are in the following format. SELECT * FROM con-product p WHERE p.con-productVendor = 'name'
Most queries targeting the data in the con-productVendor container are in the following format.
SELECT * FROM con-productVendor pv
ORDER BY pv.creditRating, pv.yearFounded
Existing environment. Current Problems.
Litware identifies the following issues:
-Updates to product categories in the con-productVendor container do not propagate automatically to documents in the con-product container.
-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.
Requirements. Planned Changes
Litware plans to implement a new Azure Cosmos DB for NoSQL account named account2 that will contain a database named iotdb. The iotdb database will contain two containers named con-iot1 and con-iot2.
Litware plans to make the following changes:
-Store the telemetry data in account2.
-Configure account1 to support multiple read-write regions.
-Implement referential integrity for the con-product container.
-Use Azure Functions to send notifications about product updates to different recipients.
-Develop an app named App1 that will run from all locations and query the data in account1.
-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 HTTPS endpoint when accessing account2.
Requirements. Business Requirements
Litware identifies the following business requirements:
-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.
-Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
-Minimize the number of firewall changes in the retail stores.
Requirements. IoT Telemetry Requirements
Litware identifies the following IoT telemetry requirements:
-Write the telemetry data from streamanalytics1 to the con-iot1 container as the data arrives. Use streamanalytics1 to create hopping window aggregated telemetry readings once per hour and write the data to con-iot2.
-Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
-Optimize the partitioning of con-iot1 for queries that support historical data of a specific device.
-Aggregate the telemetry data by device by using streamanalytics1 and write the aggregate data to con-iot2.
-Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.
Requirements. Product Catalog Requirements
Litware identifies the following requirements for the product catalog:
-Implement a custom conflict resolution policy for the product catalog data.
-Minimize the frequency of errors during updates of the con-product container.
-Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
-Trigger the execution of two Azure functions following every update to any document in the con-product container.
-

You are developing a new app named App1 by using the .NET Aspire Azure Cosmos DB integration. App1 will add data to an Azure Cosmos DB database.
You need to validate the functionality of App1 by using a CI/CD workflow. The solution must minimize administrative effort.
What should you use?

  1. Azure Cosmos DB diagnostic logs
  2. Azure Cosmos DB Data Explorer
  3. the Azure Cosmos DB Emulator
  4. Azure Storage Emulator

Answer(s): C

Explanation:

To keep administrative effort low while validating your .NET Aspire app in a CI/CD workflow, you should use the Azure Cosmos DB Emulator.
When utilizing the .NET Aspire Azure Cosmos DB hosting integration, calling the built-in emulator features allows you to run your integration tests without provisioning actual cloud infrastructure or managing complex connection credentials.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/how-to-develop-emulator




Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Overview
Litware, Inc. is a United States-based grocery retailer. Litware has a main office and a primary datacenter in Seattle. The company has 50 retail stores across the United States and an emerging online presence. Each store connects directly to the internet.
Existing environment. Cloud and Data Service Environments.
Litware has an Azure subscription that contains the resources shown in the following table.

Each container in productdb is configured for manual throughput.
The con-product container stores the company's product catalog data. Each document in con-product includes a con-productVendor value. Most queries targeting the data in con-product are in the following format. SELECT * FROM con-product p WHERE p.con-productVendor = 'name'
Most queries targeting the data in the con-productVendor container are in the following format.
SELECT * FROM con-productVendor pv
ORDER BY pv.creditRating, pv.yearFounded
Existing environment. Current Problems.
Litware identifies the following issues:
-Updates to product categories in the con-productVendor container do not propagate automatically to documents in the con-product container.
-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.
Requirements. Planned Changes
Litware plans to implement a new Azure Cosmos DB for NoSQL account named account2 that will contain a database named iotdb. The iotdb database will contain two containers named con-iot1 and con-iot2.
Litware plans to make the following changes:
-Store the telemetry data in account2.
-Configure account1 to support multiple read-write regions.
-Implement referential integrity for the con-product container.
-Use Azure Functions to send notifications about product updates to different recipients.
-Develop an app named App1 that will run from all locations and query the data in account1.
-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 HTTPS endpoint when accessing account2.
Requirements. Business Requirements
Litware identifies the following business requirements:
-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.
-Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
-Minimize the number of firewall changes in the retail stores.
Requirements. IoT Telemetry Requirements
Litware identifies the following IoT telemetry requirements:
-Write the telemetry data from streamanalytics1 to the con-iot1 container as the data arrives. Use streamanalytics1 to create hopping window aggregated telemetry readings once per hour and write the data to con-iot2.
-Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
-Optimize the partitioning of con-iot1 for queries that support historical data of a specific device.
-Aggregate the telemetry data by device by using streamanalytics1 and write the aggregate data to con-iot2.
-Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.
Requirements. Product Catalog Requirements
Litware identifies the following requirements for the product catalog:
-Implement a custom conflict resolution policy for the product catalog data.
-Minimize the frequency of errors during updates of the con-product container.
-Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
-Trigger the execution of two Azure functions following every update to any document in the con-product container.
-

You have an Azure Cosmos DB for NoSQL account.
You run the following query against a container in the account.

What is the output of the query?

  1. [{"A": false, "B": true, "C": false}]
  2. [{"A": true, "B": false, "C": true}]
  3. [{"A": true, "B": true, "C": false}]
  4. [{"A": true, "B": true, "C": true}]

Answer(s): A

Explanation:

IS_NUMBER returns a Boolean value indicating if the type of the specified expression is a number. "1234" is a string, not a number.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/sql-query-is-number




Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Overview
Litware, Inc. is a United States-based grocery retailer. Litware has a main office and a primary datacenter in Seattle. The company has 50 retail stores across the United States and an emerging online presence. Each store connects directly to the internet.
Existing environment. Cloud and Data Service Environments.
Litware has an Azure subscription that contains the resources shown in the following table.

Each container in productdb is configured for manual throughput.
The con-product container stores the company's product catalog data. Each document in con-product includes a con-productVendor value. Most queries targeting the data in con-product are in the following format. SELECT * FROM con-product p WHERE p.con-productVendor = 'name'
Most queries targeting the data in the con-productVendor container are in the following format.
SELECT * FROM con-productVendor pv
ORDER BY pv.creditRating, pv.yearFounded
Existing environment. Current Problems.
Litware identifies the following issues:
-Updates to product categories in the con-productVendor container do not propagate automatically to documents in the con-product container.
-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.
Requirements. Planned Changes
Litware plans to implement a new Azure Cosmos DB for NoSQL account named account2 that will contain a database named iotdb. The iotdb database will contain two containers named con-iot1 and con-iot2.
Litware plans to make the following changes:
-Store the telemetry data in account2.
-Configure account1 to support multiple read-write regions.
-Implement referential integrity for the con-product container.
-Use Azure Functions to send notifications about product updates to different recipients.
-Develop an app named App1 that will run from all locations and query the data in account1.
-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 HTTPS endpoint when accessing account2.
Requirements. Business Requirements
Litware identifies the following business requirements:
-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.
-Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
-Minimize the number of firewall changes in the retail stores.
Requirements. IoT Telemetry Requirements
Litware identifies the following IoT telemetry requirements:
-Write the telemetry data from streamanalytics1 to the con-iot1 container as the data arrives. Use streamanalytics1 to create hopping window aggregated telemetry readings once per hour and write the data to con-iot2.
-Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
-Optimize the partitioning of con-iot1 for queries that support historical data of a specific device.
-Aggregate the telemetry data by device by using streamanalytics1 and write the aggregate data to con-iot2.
-Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.
Requirements. Product Catalog Requirements
Litware identifies the following requirements for the product catalog:
-Implement a custom conflict resolution policy for the product catalog data.
-Minimize the frequency of errors during updates of the con-product container.
-Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
-Trigger the execution of two Azure functions following every update to any document in the con-product container.
-

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription that contains an Azure Cosmos DB for NoSQL account. The account hosts a container named Container1.
Items are stored in Container1 in the following format.

You need to query name, sizeInGb, and currentStockLevel for items that have a value of currentStockLevel that is greater than 100.
How should you complete the query? 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:




Self-joins in Azure Cosmos DB for NoSQL
In Azure Cosmos DB for NoSQL, data is schema-free and typically denormalized. Instead of joining data across entities and sets, like you would in a relational database, joins occur within a single item. Specifically, joins are scoped to that item and can't occur across multiple items and containers.
Box 1: JOIN
In a traditional relational database, the tags would be separated into a separate table and a cross-table join is performed with a filter applied to the results. In the API for NoSQL, we can perform a self-join operation within the item using the JOIN keyword.
Box 2: IN
Example:
SELECT p.sku, t.name AS tag
FROM
products p
JOIN
t IN p.tags
WHERE p.categoryName = "Sleeping Bags" AND t.slug = "bag-shape-mummy"


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/query/join




Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Overview
Litware, Inc. is a United States-based grocery retailer. Litware has a main office and a primary datacenter in Seattle. The company has 50 retail stores across the United States and an emerging online presence. Each store connects directly to the internet.
Existing environment. Cloud and Data Service Environments.
Litware has an Azure subscription that contains the resources shown in the following table.

Each container in productdb is configured for manual throughput.
The con-product container stores the company's product catalog data. Each document in con-product includes a con-productVendor value. Most queries targeting the data in con-product are in the following format. SELECT * FROM con-product p WHERE p.con-productVendor = 'name'
Most queries targeting the data in the con-productVendor container are in the following format.
SELECT * FROM con-productVendor pv
ORDER BY pv.creditRating, pv.yearFounded
Existing environment. Current Problems.
Litware identifies the following issues:
-Updates to product categories in the con-productVendor container do not propagate automatically to documents in the con-product container.
-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.
Requirements. Planned Changes
Litware plans to implement a new Azure Cosmos DB for NoSQL account named account2 that will contain a database named iotdb. The iotdb database will contain two containers named con-iot1 and con-iot2.
Litware plans to make the following changes:
-Store the telemetry data in account2.
-Configure account1 to support multiple read-write regions.
-Implement referential integrity for the con-product container.
-Use Azure Functions to send notifications about product updates to different recipients.
-Develop an app named App1 that will run from all locations and query the data in account1.
-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 HTTPS endpoint when accessing account2.
Requirements. Business Requirements
Litware identifies the following business requirements:
-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.
-Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
-Minimize the number of firewall changes in the retail stores.
Requirements. IoT Telemetry Requirements
Litware identifies the following IoT telemetry requirements:
-Write the telemetry data from streamanalytics1 to the con-iot1 container as the data arrives. Use streamanalytics1 to create hopping window aggregated telemetry readings once per hour and write the data to con-iot2.
-Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
-Optimize the partitioning of con-iot1 for queries that support historical data of a specific device.
-Aggregate the telemetry data by device by using streamanalytics1 and write the aggregate data to con-iot2.
-Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.
Requirements. Product Catalog Requirements
Litware identifies the following requirements for the product catalog:
-Implement a custom conflict resolution policy for the product catalog data.
-Minimize the frequency of errors during updates of the con-product container.
-Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
-Trigger the execution of two Azure functions following every update to any document in the con-product container.
-

You have a container in an Azure Cosmos DB for NoSQL account. The container stores data about families. Data about parents, children, and pets are stored as separate documents.
Each document contains the address of each family. Members of the same family share the same partition key named familyId.
You need to update the address for each member of the same family that share the same address. The solution must meet the following requirements:
-Be atomic, consistent, isolated, and durable (ACID).
-Provide the lowest latency.
What should you do?

  1. Update the document of each family member separately by using a patch operation
  2. Update the document of each family member separately and set the consistency level to strong
  3. Update the document of each family member by using a transactional batch operation

Answer(s): C

Explanation:

Each transaction provides ACID (Atomicity, Consistency, Isolation, Durability) property guarantees. Transactional batch operations offer reduced latency on equivalent operations.
Note: Transactional batch describes a group of point operations that need to either succeed or fail together with the same partition key in a container. In the .NET SDK, the TransactionalBatch class is used to define this batch of operations. If all operations succeed in the order they are described within the transactional batch operation, the transaction will be committed. However, if any operation fails, the entire transaction is rolled back.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/transactional-batch




Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Overview
Litware, Inc. is a United States-based grocery retailer. Litware has a main office and a primary datacenter in Seattle. The company has 50 retail stores across the United States and an emerging online presence. Each store connects directly to the internet.
Existing environment. Cloud and Data Service Environments.
Litware has an Azure subscription that contains the resources shown in the following table.

Each container in productdb is configured for manual throughput.
The con-product container stores the company's product catalog data. Each document in con-product includes a con-productVendor value. Most queries targeting the data in con-product are in the following format. SELECT * FROM con-product p WHERE p.con-productVendor = 'name'
Most queries targeting the data in the con-productVendor container are in the following format.
SELECT * FROM con-productVendor pv
ORDER BY pv.creditRating, pv.yearFounded
Existing environment. Current Problems.
Litware identifies the following issues:
-Updates to product categories in the con-productVendor container do not propagate automatically to documents in the con-product container.
-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.
Requirements. Planned Changes
Litware plans to implement a new Azure Cosmos DB for NoSQL account named account2 that will contain a database named iotdb. The iotdb database will contain two containers named con-iot1 and con-iot2.
Litware plans to make the following changes:
-Store the telemetry data in account2.
-Configure account1 to support multiple read-write regions.
-Implement referential integrity for the con-product container.
-Use Azure Functions to send notifications about product updates to different recipients.
-Develop an app named App1 that will run from all locations and query the data in account1.
-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 HTTPS endpoint when accessing account2.
Requirements. Business Requirements
Litware identifies the following business requirements:
-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.
-Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
-Minimize the number of firewall changes in the retail stores.
Requirements. IoT Telemetry Requirements
Litware identifies the following IoT telemetry requirements:
-Write the telemetry data from streamanalytics1 to the con-iot1 container as the data arrives. Use streamanalytics1 to create hopping window aggregated telemetry readings once per hour and write the data to con-iot2.
-Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
-Optimize the partitioning of con-iot1 for queries that support historical data of a specific device.
-Aggregate the telemetry data by device by using streamanalytics1 and write the aggregate data to con-iot2.
-Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.
Requirements. Product Catalog Requirements
Litware identifies the following requirements for the product catalog:
-Implement a custom conflict resolution policy for the product catalog data.
-Minimize the frequency of errors during updates of the con-product container.
-Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
-Trigger the execution of two Azure functions following every update to any document in the con-product container.
-

You have an Azure Cosmos DB for NoSQL account that hosts a container named Container1.
The DefaultTimeToLive property of Container1 is set to 500.
Container1 contains an item that has a ttl property of 1000.
The item in Container1 is modified.
When will the item be deleted automatically?

  1. in 1,000 hours
  2. in 500 hours
  3. in 1,000 seconds
  4. in 500 seconds

Answer(s): C

Explanation:

The item will be automatically deleted 1,000 seconds after its last modification time.
How Time to Live (TTL) Evaluation Works
Item-Level Override: In Azure Cosmos DB, when a container has a valid DefaultTimeToLive configured (in this case, 1000 seconds), any individual item can override this value by declaring its own ttl property. Because the item's ttl is explicitly set to 1000, the container's default of 500 is completely ignored for this specific item.
Resetting the Clock: TTL expiration calculations are tied directly to the item's system-generated _ts (timestamp) property, which records the last modified time. Every time an item is created or updated, Azure Cosmos DB updates _ts to the current Unix epoch time.
Consequently, modifying the item resets its lifespan, and the system will automatically purge it exactly §,000 seconds after that modification occurred.


Reference:

https://learn.microsoft.com/en-us/cosmos-db/time-to-live




Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Overview
Litware, Inc. is a United States-based grocery retailer. Litware has a main office and a primary datacenter in Seattle. The company has 50 retail stores across the United States and an emerging online presence. Each store connects directly to the internet.
Existing environment. Cloud and Data Service Environments.
Litware has an Azure subscription that contains the resources shown in the following table.

Each container in productdb is configured for manual throughput.
The con-product container stores the company's product catalog data. Each document in con-product includes a con-productVendor value. Most queries targeting the data in con-product are in the following format. SELECT * FROM con-product p WHERE p.con-productVendor = 'name'
Most queries targeting the data in the con-productVendor container are in the following format.
SELECT * FROM con-productVendor pv
ORDER BY pv.creditRating, pv.yearFounded
Existing environment. Current Problems.
Litware identifies the following issues:
-Updates to product categories in the con-productVendor container do not propagate automatically to documents in the con-product container.
-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.
Requirements. Planned Changes
Litware plans to implement a new Azure Cosmos DB for NoSQL account named account2 that will contain a database named iotdb. The iotdb database will contain two containers named con-iot1 and con-iot2.
Litware plans to make the following changes:
-Store the telemetry data in account2.
-Configure account1 to support multiple read-write regions.
-Implement referential integrity for the con-product container.
-Use Azure Functions to send notifications about product updates to different recipients.
-Develop an app named App1 that will run from all locations and query the data in account1.
-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 HTTPS endpoint when accessing account2.
Requirements. Business Requirements
Litware identifies the following business requirements:
-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.
-Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
-Minimize the number of firewall changes in the retail stores.
Requirements. IoT Telemetry Requirements
Litware identifies the following IoT telemetry requirements:
-Write the telemetry data from streamanalytics1 to the con-iot1 container as the data arrives. Use streamanalytics1 to create hopping window aggregated telemetry readings once per hour and write the data to con-iot2.
-Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
-Optimize the partitioning of con-iot1 for queries that support historical data of a specific device.
-Aggregate the telemetry data by device by using streamanalytics1 and write the aggregate data to con-iot2.
-Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.
Requirements. Product Catalog Requirements
Litware identifies the following requirements for the product catalog:
-Implement a custom conflict resolution policy for the product catalog data.
-Minimize the frequency of errors during updates of the con-product container.
-Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
-Trigger the execution of two Azure functions following every update to any document in the con-product container.
-

HOTSPOT (Drag and Drop is not supported)
You plan to create an Azure Cosmos DB for NoSQL container that will contain items in the following format.

You need to define a query that will return the userid values of all the users who purchased an item that has a sku value of 11111.
How should you compete the query? 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: n in c.items
Define n as c.items
Example of subquery with the EXISTS predicate:
SELECT p.name, p.tags
FROM
products p
WHERE
EXISTS (SELECT VALUE t FROM t IN p.tags WHERE t = "outerwear")
Box 2: n.sku
The sku is defined within the items construct.
Note: Subqueries in Azure Cosmos DB for NoSQL
A subquery is a query nested within another query within Azure Cosmos DB for NoSQL. A subquery is also called an inner query or inner SELECT. The statement that contains a subquery is typically called an outer query.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/query/subquery




Case Study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs.
When you are ready to answer a question, click the Question button to return to the question.
Overview
Litware, Inc. is a United States-based grocery retailer. Litware has a main office and a primary datacenter in Seattle. The company has 50 retail stores across the United States and an emerging online presence. Each store connects directly to the internet.
Existing environment. Cloud and Data Service Environments.
Litware has an Azure subscription that contains the resources shown in the following table.

Each container in productdb is configured for manual throughput.
The con-product container stores the company's product catalog data. Each document in con-product includes a con-productVendor value. Most queries targeting the data in con-product are in the following format. SELECT * FROM con-product p WHERE p.con-productVendor = 'name'
Most queries targeting the data in the con-productVendor container are in the following format.
SELECT * FROM con-productVendor pv
ORDER BY pv.creditRating, pv.yearFounded
Existing environment. Current Problems.
Litware identifies the following issues:
-Updates to product categories in the con-productVendor container do not propagate automatically to documents in the con-product container.
-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.
Requirements. Planned Changes
Litware plans to implement a new Azure Cosmos DB for NoSQL account named account2 that will contain a database named iotdb. The iotdb database will contain two containers named con-iot1 and con-iot2.
Litware plans to make the following changes:
-Store the telemetry data in account2.
-Configure account1 to support multiple read-write regions.
-Implement referential integrity for the con-product container.
-Use Azure Functions to send notifications about product updates to different recipients.
-Develop an app named App1 that will run from all locations and query the data in account1.
-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 HTTPS endpoint when accessing account2.
Requirements. Business Requirements
Litware identifies the following business requirements:
-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.
-Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
-Minimize the number of firewall changes in the retail stores.
Requirements. IoT Telemetry Requirements
Litware identifies the following IoT telemetry requirements:
-Write the telemetry data from streamanalytics1 to the con-iot1 container as the data arrives. Use streamanalytics1 to create hopping window aggregated telemetry readings once per hour and write the data to con-iot2.
-Automatically delete items in con-iot1 after one hour unless a per-item time to live is set.
-Optimize the partitioning of con-iot1 for queries that support historical data of a specific device.
-Aggregate the telemetry data by device by using streamanalytics1 and write the aggregate data to con-iot2.
-Ensure that the items in con-iot2 persist regardless of the per-item time to live setting.
Requirements. Product Catalog Requirements
Litware identifies the following requirements for the product catalog:
-Implement a custom conflict resolution policy for the product catalog data.
-Minimize the frequency of errors during updates of the con-product container.
-Once multi-region writes are configured, maximize the performance of App1 queries against the data in account1.
-Trigger the execution of two Azure functions following every update to any document in the con-product container.
-

You have an Azure Cosmos DB for NoSQL account that contains a database named DB1 and a container named Container1.
You need to manage the account by using the Azure Cosmos DB SDK.
What should you do?

  1. Create a container in DB1.
  2. List the physical partitions of Container1.
  3. Read a stored procedure in Container1.
  4. Create a user defined function (UDF) in Container1.

Answer(s): D

Explanation:

How to register and use stored procedures, triggers, and user-defined functions in Azure Cosmos DB
How to work with user-defined functions
The following examples show how to register a user-defined function by using the Azure Cosmos DB SDKs.
The following code shows how to register a user-defined function using the .NET SDK v2:
string udfId = "Tax";
var udfTax = new UserDefinedFunction
{
Id = udfId,
Body = File.ReadAllText($@"..\js\{udfId}.js")
};
Uri containerUri = UriFactory.CreateDocumentCollectionUri("myDatabase", "myContainer");
await client.CreateUserDefinedFunctionAsync(containerUri, udfTax);
Note: Azure Cosmos DB provides language-integrated, transactional execution of JavaScript.
When using the API for NoSQL in Azure Cosmos DB, you can write stored procedures, triggers, and user-defined functions (UDFs) in the JavaScript language. You can write your logic in JavaScript that executed inside the database engine. You can create and execute triggers, stored procedures, and UDFs by using Azure portal, the JavaScript language integrated query API in Azure Cosmos DB or the Azure Cosmos DB for NoSQL client SDKs.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/how-to-use-stored-procedures-triggers-udfs



Share your comments for Microsoft DP-420 exam with other users:

L
Lingaraj
10/26/2023 1:27:00 AM

i love this thank you i need

M
Muhammad Rawish Siddiqui
12/5/2023 12:38:00 PM

question # 142: data governance is not one of the deliverables in the document and content management context diagram.

A
al
6/7/2023 10:25:00 AM

most answers not correct here

B
Bano
1/19/2024 2:29:00 AM

what % of questions do we get in the real exam?

O
Oliviajames
10/25/2023 5:31:00 AM

i just want to tell you. i took my microsoft az-104 exam and passed it. your program was awesome. i especially liked your detailed questions and answers and practice tests that made me well-prepared for the exam. thanks to this website!!!

D
Divya
8/27/2023 12:31:00 PM

all the best

K
KY
1/1/2024 11:01:00 PM

very usefull document

A
Arun
9/20/2023 4:52:00 PM

nice and helpful questions

J
Joseph J
7/11/2023 2:53:00 PM

i found the questions helpful

M
Meg
10/12/2023 8:02:00 AM

q 105 . ans is d

N
Navaneeth S
7/14/2023 7:57:00 AM

i have interest to get a sybase iq dba certification

A
Aish
10/11/2023 5:27:00 AM

want to pass exm.

A
Anonymous
6/12/2023 7:23:00 AM

are the answers correct?

K
Kris
7/7/2023 9:43:00 AM

good morning, could you please upload this exam again, i need it to test my knowledge in sd-wan with version 7.0.

M
Meghraj mali
10/7/2023 1:47:00 PM

very nice question

N
Noel
11/1/2022 9:14:00 PM

i have learning disability and this exam dumps allowed me to focus on the actual questions and not worry about notes and the those other study materials.

J
Jas
10/25/2023 6:01:00 PM

165 should be apt

N
Neetu
6/22/2023 8:41:00 AM

please upload the dumps, real need of them

M
Mark
10/24/2023 1:34:00 AM

any recent feeedback?

G
Gopinadh
8/9/2023 4:05:00 AM

question number 2 is indicating you are giving proper questions. observe and change properly.

S
Santhi
1/1/2024 8:23:00 AM

passed today.40% questions were new.litwere case study,lots of new questions on afd,ratelimit,tm,lb,app gatway.got 2 set series of questions which are not present here.questions on azure cyclecloud, no.of vnet/vms required for implimentation,blueprints assignment/management group etc

R
Raviraj Magadum
1/12/2024 11:39:00 AM

practice test

S
sivaramakrishnan
7/27/2023 8:12:00 AM

want the dumps for emc content management server programming(cmsp)

A
Aderonke
10/23/2023 1:52:00 PM

brilliant and helpful

A
Az
9/16/2023 2:43:00 PM

q75. azure files is pass

K
ketty
11/9/2023 8:10:00 AM

very helpful

S
Sonail
5/2/2022 1:36:00 PM

thank you for these questions. it helped a lot.

S
Shariq
7/28/2023 8:00:00 AM

how do i get the h12-724 dumps

A
adi
10/30/2023 11:51:00 PM

nice data dumps

E
EDITH NCUBE
7/25/2023 7:28:00 AM

answers are correct

R
Raja
6/20/2023 4:38:00 AM

good explanation

B
BigMouthDog
1/22/2022 8:17:00 PM

hi team just want to know if there is any update version of the exam 350-401

F
francesco
10/30/2023 11:08:00 AM

helpful on 2017 scrum guide

A
Amitabha Roy
10/5/2023 3:16:00 AM

planning to attempt for the exam.

AI Tutor 👋 I’m here to help!