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

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


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 that stores data about families.
The following is a sample document.

You run the following query against the container.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.
Note: Each correct selection is worth one point.
Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: No
The result is empty, since the cross product of each item from source and an empty set is empty:
Note: Joins result in a complete cross product of the sets participating in the join. The result of an N-way join is a set of N-element tuples, where each value in the tuple is associated with the aliased set participating in the join and can be accessed by referencing that alias in other clauses.
Box 2: No
The cross join is not on the pets.
Box 3: Yes
The cross join is not on the pets.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/sql-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.
-

Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.
You have an Azure Cosmos DB for NoSQL database. The database hosts a container named families that stores data in the following format.

You need to return the following data:
● The ID of the family
● The family names of the children
● The name of any pets if the pet is a cat
Solution: You run the following query.

Does this meet the goal?

  1. Yes
  2. No

Answer(s): B

Explanation:

CROSS APPLY should not be used.
Correct:
* You run the following query.

The following Azure Cosmos DB NoSQL query fulfills the requirements by unnesting child array items and filtering the pet array:
To retrieve the family ID, the children's family names, and the rabbit's name, you can use the query below.
SELECT f.id, c.familyName AS FamilyName, p.givenName AS petName
FROM families f
JOIN f.children c
JOIN (SELECT VALUE p FROM p IN c.pets WHERE p.type = 'cat') AS p
1. Flatten the Children Array
To access individual properties within the children sub-array, use a JOIN statement. In Azure Cosmos DB, a JOIN performs an inner product between the document root (f) and the array (f.children). This filters out any family documents that contain no children.
2. Isolate Cat Pets
To inspect the properties of the pets array embedded inside each child, apply a secondary JOIN on c.pets. The WHERE clause then filters these projected items to only include cases where the property $p.type$ matches the string "cat".
3. Project Specific Attributes
The SELECT clause restricts the final JSON output schema to contain exactly three custom-aliased properties: familyId: Extracted from the root document
IDchildFamilyName: Extracted from the current child item iterationpetName: Extracted from the matching pet item iteration
Incorrect:
* You run the following query.

Use two JOINS and one subquery, not three JOINS and a subquery.
* You run the following query.

CROSS APPLY should not be used.


Reference:

https://learn.microsoft.com/en-us/cosmos-db/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.
-

DRAG DROP (Drag and Drop is not supported)
You are designing three apps named App1, App2, and App3. Each app will use a separate Azure Cosmos DB for NoSQL account. The apps have the following consistency requirements:
-App1: Reads must always return the most recent committed version of an item, where the commit occurred during the same session.
-App2: Reads must always return the most recent committed version of an item, even if the commit occurred during another session.
-App3: Write latency must be minimized and data staleness can be tolerated.
You need to recommend a default consistency level for each Azure Cosmos DB for NoSQL account. The solution must minimize concurrency.
What should you recommend for the account of each app? To answer, drag the appropriate consistency levels to the correct apps. Each consistency level may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Session
App1: Reads must always return the most recent committed version of an item, where the commit occurred during the same session.
Session consistency
In session consistency, within a single client session, reads are guaranteed to honor the read-your-writes, and write-follows-reads guarantees. This guarantee assumes a single “writer” session or sharing the session token for multiple writers.
Like all consistency levels weaker than Strong, writes are replicated to a minimum of three replicas (in a four replica set) in the local region, with asynchronous replication to all other regions.
Box 2: Strong
App2: Reads must always return the most recent committed version of an item, even if the commit occurred during another session.
Strong consistency offers a linearizability guarantee. Linearizability refers to serving requests concurrently. The reads are guaranteed to return the most recent committed version of an item. A client never sees an uncommitted or partial write. Users are always guaranteed to read the latest committed write.
Box 3: Eventual
App3: Write latency must be minimized and data staleness can be tolerated.
Eventual consistency
Like all consistency levels weaker than Strong, writes are replicated to a minimum of three replicas (in a four replica set) in the local region, with asynchronous replication to all other regions.
In Eventual consistency, the client issues read requests against any one of the four replicas in the specified region. This replica may be lagging and could return stale or no data.
Eventual consistency is the weakest form of consistency because a client may read the values that are older than the ones it read in the past. Eventual consistency is ideal where the application doesn't require any ordering guarantees. Examples include count of Retweets, Likes, or non-threaded comments. The following graphic illustrates the eventual consistency with musical notes.
Incorrect:
* Bounded Staleness
For a single-region account, Bounded Staleness provides the same write consistency guarantees as Session and Eventual Consistency. With Bounded Staleness, data is replicated to a local majority (three replicas in a four replica set) in the single region.
For single-region write accounts with two or more regions, data is replicated from the primary region to all secondary (read-only) regions. For multi-region write accounts with two or more regions, data is replicated from the region it was originally written in to all other writable regions. In both scenarios, while not common, there may occasionally be a replication lag from one region to another.
* Consistent prefix consistency
Like all consistency levels weaker than Strong, writes are replicated to a minimum of three replicas (in a four-replica set) in the local region, with asynchronous replication to all other regions.
In consistent prefix, updates made as single document writes see eventual consistency.
Updates made as a batch within a transaction, are returned consistent to the transaction in which they were committed. Write operations within a transaction of multiple documents are always visible together.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels




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 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.

  1. the consistency level in RequestOptions
  2. regional latency
  3. the default consistency level
  4. the PreferredLocations configuration
  5. a region being available

Answer(s): D,E

Explanation:

Connecting to a preferred region using the API for NoSQL
The SDKs accept an optional parameter PreferredLocations that is an ordered list of Azure regions.
The SDK will automatically send all writes to the current write region. All reads will be sent to the first available region in the preferred locations list. If the request fails, the client will fail down the list to the next region.
The SDK will only attempt to read from the regions specified in preferred locations. So, for example, if the Azure Cosmos DB account is available in four regions, but the client only specifies two read(non-write) regions within the PreferredLocations, then no reads will be served out of the read region that is not specified in PreferredLocations. If the read regions specified in the PreferredLocations list are not available, reads will be served out of write region.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/tutorial-global-distribution




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 designing an Azure Cosmos DB for NoSQL solution to store data from IoT devices. Writes from the devices will be occur every second. Data will be retained indefinitely.
The following is a sample of the data.

You need to select a partition key that meets the following requirements for writes:
-Minimizes the partition skew
-Avoids capacity limits
-Avoids hot partitions
What should you do?

  1. Create a new synthetic key that contains deviceId and timestamp
  2. Use timestamp as the partition key
  3. Use deviceManufacturer as the partition key
  4. Use sensor1Value as the partition key

Answer(s): A

Explanation:

Correct:
* Create a new synthetic key that contains deviceId and a random number.
Use a partition key with a random suffix. Distribute the workload more evenly is to append a random number at the end of the partition key value.
When you distribute items in this way, you can perform parallel write operations across partitions.
* Create a new synthetic key that contains deviceId and timestamp.
Concatenate multiple properties of an item.
You can form a partition key by concatenating multiple property values into a single artificial partitionKey property. These keys are referred to as synthetic keys.
For example, consider the following example document:
{
"deviceId": "abc-123",
"date": 2018
}
For the previous document, one option is to set /deviceId or /date as the partition key. Use this option, if you want to partition your container based on either device ID or date. Another option is to concatenate these two values into a synthetic partitionKey property that's used as the partition key.
{
"deviceId": "abc-123",
"date": 2018,
"partitionKey": "abc-123-2018"
Incorrect:
* Create a new synthetic key that contains deviceId and deviceManufacturer.
All the devices could have the same manufacturer.
* Create a new synthetic key that contains deviceId and sensor1Value.
Senser1Value has only two values.
* Use deviceId as the partition key.
* Use deviceManufacturer as the partition key.
All the devices could have the same manufacturer.
* Use sensor1Value as the partition key
* Use timestamp as the partition key.
You will also not like to partition the data on “DateTime”, because this will create a hot partition. Imagine you have partitioned the data on time, then for a given minute, all the calls will hit one partition. If you need to retrieve the data for a customer, then it will be a fan-out query because data may be distributed on all the partitions.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/synthetic-partition-keys https://docs.microsoft.com/en-us/azure/cosmos-db/concepts-limits




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 plan to create an Azure Cosmos DB for NoSQL account that will have a single write region and three read regions.
You need to set the consistency level for the account. The solution must meet the following requirements:
-In the write region, writes must replicate synchronously across at least three replicas.
-In the read regions, reads must see writes in order for transactional batches.
-Throughput for reads and writes must be maximized.
Which consistency level should you select?

  1. Consistent Prefix
  2. Bounded Staleness
  3. Eventual
  4. Strong

Answer(s): D




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 database named db1 in an Azure Cosmos DB for NoSQL account.
You are designing an application that will use db1.
In db1, you are creating a new container named coll1 that will store online orders.
The following is a sample of a document that will be stored in coll1.

The application will have the following characteristics:
-New orders will be created frequently by different customers.
-Customers will often view their past order history.
You need to select the partition key value for coll1 to support the application. The solution must minimize costs.
To what should you set the partition key?

  1. orderId
  2. customerId
  3. orderDate
  4. id

Answer(s): B

Explanation:

If most of your workload's requests are queries and most of your queries have an equality filter on the same property, this property can be a good partition key choice. For example, if you frequently run a query that filters on UserID, then selecting UserID as the partition key would reduce the number of cross-partition queries.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/partitioning-overview




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.
-

DRAG DROP (Drag and Drop is not supported)
You have an Azure Cosmos DB for NoSQL account.
You need to implement Always Encrypted for all the data stored in the account. The solution must minimize administrative effort.
At which level should you define the encryption policy and set the data encryption key? To answer, drag the appropriate levels to the correct requirements. Each level may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
Note: Each correct selection is worth one point.
Select and Place:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Define the encryption policy: Container
Defining the encryption policy at the container level allows you to specify encryption for all items within that container.
Set the data encryption key: Account
Setting the data encryption key at the account level allows you to manage the encryption keys centrally for the entire Cosmos DB account, simplifying key management.



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

S
srameh
4/14/2026 10:09:29 AM

Question 3:

  • Correct answer: Phase 4, Post Accreditation

  • Explanation:
- In DITSCAP, the four phases are: - Phase 1: Definition (concept and requirements) - Phase 2: Verification (design and testing) - Phase 3: Validation (fielding and evaluation) - Phase 4: Post Accreditation (ongoing operations and lifecycle management) - The description—continuing operation of an accredited IT system and addressing changing threats throughout its life cycle—fits the Post Accreditation phase, which covers operations, maintenance, monitoring, and reauthorization as threats and environment evolve.

O
onibokun10
4/13/2026 7:50:14 PM

Question 129:
Correct answer: CNAME

  • A CNAME record creates an alias for a domain, so newapplication.comptia.org will resolve to whatever IP address www.comptia.org resolves to. This ensures both names point to the same resource without duplicating the IP.
  • Why not the others:
- SOA defines authoritative information for a zone. - MX specifies mail exchange servers. - NS designates name servers for a zone.
  • Notes: The alias name (newapplication.comptia.org) should not have other records if you use a CNAME for it, and CNAMEs aren’t used for the zone apex (root) domain. This scenario uses a subdomain, so a CNAME is appropriate.

A
Anonymous User
4/13/2026 6:29:58 PM

Question 1:

  • Correct answer: C

  • Why this is best:
- Uses OS Login with IAM, so SSH access is granted via Google accounts rather than distributing per-user SSH keys. - Granting the compute.osAdminLogin role to a Google group gives admin access to all team members in a centralized, auditable way. - Access is auditable: Cloud Audit Logs show who accessed which VM, satisfying the security requirement to determine who accessed a given instance.
  • How it works:
- Enable OS Login on the project/instances (enable-oslogin metadata). - Add the team’s

A
Anonymous User
4/13/2026 1:00:51 PM

Question 2:

  • Answer: D. Azure Advisor

  • Why: To view security-related recommendations for resources in the Compute and Apps area (including App Service Web Apps and Functions), you use Azure Advisor. Advisor surfaces personalized best-practice recommendations across resources, including security, and shows which resources are affected and the severity.

  • Why not the others:
- Azure Log Analytics is for ad-hoc querying of telemetry, not for viewing security recommendations. - Azure Event Hubs is for streaming telemetry data, not for security recommendations.
  • Quick tip: In the portal, navigate to Azure Advisor and check the Security recommendations for App Services to see actionable items and affe

D
Don
4/11/2026 5:36:42 AM

Recommend using AI for Solutions rather the Answer(s) submitted here

M
Mogae Malapela
4/8/2026 6:37:56 AM

This is very interesting

A
Anon
4/6/2026 5:22:54 PM

Are these the same questions you have to pay for in ExamTopics?

L
LRK
3/22/2026 2:38:08 PM

For Question 7 - while the answer description indicates the correct answer, the option no. mentioned is incorrect. Nice and Comprehensive. Thankyou

R
Rian
3/19/2026 9:12:10 AM

This is very good and accurate. Explanation is very helpful even thou some are not 100% right but good enough to pass.

G
Gerrard
3/18/2026 6:58:37 AM

The DP-900 exam can be tricky if you aren't familiar with Microsoft’s specific cloud terminology. I used the practice questions from free-braindumps.com and found them incredibly helpful. The site breaks down core data concepts and Azure services in a way that actually mirrors the real test. As a resutl I passed my exam.

V
Vineet Kumar
3/6/2026 5:26:16 AM

interesting

J
Joe
1/20/2026 8:25:24 AM

Passed this exam 2 days ago. These questions are in the exam. You are safe to use them.

N
NJ
12/24/2025 10:39:07 AM

Helpful to test your preparedness before giving exam

A
Ashwini
12/17/2025 8:24:45 AM

Really helped

J
Jagadesh
12/16/2025 9:57:10 AM

Good explanation

S
shobha
11/29/2025 2:19:59 AM

very helpful

P
Pandithurai
11/12/2025 12:16:21 PM

Question 1, Ans is - Developer,Standard,Professional Direct and Premier

E
Einstein
11/8/2025 4:13:37 AM

Passed this exam in first appointment. Great resource and valid exam dump.

D
David
10/31/2025 4:06:16 PM

Today I wrote this exam and passed, i totally relay on this practice exam. The questions were very tough, these questions are valid and I encounter the same.

T
Thor
10/21/2025 5:16:29 AM

Anyone used this dump recently?

V
Vladimir
9/25/2025 9:11:14 AM

173 question is A not D

K
khaos
9/21/2025 7:07:26 AM

nice questions

K
Katiso Lehasa
9/15/2025 11:21:52 PM

Thanks for the practice questions they helped me a lot.

E
Einstein
9/2/2025 7:42:00 PM

Passed this exam today. All questions are valid and this is not something you can find in ChatGPT.

V
vito
8/22/2025 4:16:51 AM

i need to pass exam for VMware 2V0-11.25

M
Matt
7/31/2025 11:44:40 PM

Great questions.

O
OLERATO
7/1/2025 5:44:14 AM

great dumps to practice for the exam

A
Adekunle willaims
6/9/2025 7:37:29 AM

How reliable and relevant are these questions?? also i can see the last update here was January and definitely new questions would have emerged.

A
Alex
5/24/2025 12:54:15 AM

Can I trust to this source?

S
SPriyak
3/17/2025 11:08:37 AM

can you please provide the CBDA latest test preparation

C
Chandra
11/28/2024 7:17:38 AM

This is the best and only way of passing this exam as it is extremely hard. Good questions and valid dump.

S
Sunak
1/25/2025 9:17:57 AM

Can I use this dumps when I am taking the exam? I mean does somebody look what tabs or windows I have opened ?

F
Frank
2/15/2024 11:36:57 AM

Finally got a change to write this exam and pass it! Valid and accurate!

A
Anonymous User
2/2/2024 6:42:12 PM

Upload this exam please!

AI Tutor 👋 I’m here to help!