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

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


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 named container1 in an Azure Cosmos DB for NoSQL account. The container1 container has 120 GB of data.
The following is a sample of a document in container1.

The orderId property is used as the partition key.
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: Yes
Records with different OrderIDs will match.
Box 2: Yes
Records with different OrderIDs will match.
Box 3: No
Only records with one specific OrderId will match




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 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. Use deviceId as the partition key.
  2. Create a new Synthetic key that contains deviceId and deviceManufacturer.
  3. Use deviceManufacturer as the partition key.
  4. Create a new synthetic key that contains deviceId and a random number.

Answer(s): D

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

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 that stores customer data. Each customer data item includes the customer’s name and zero or more related business categories in an array.
You need identify customers that have one of their business categories set to “retail”. The solution must return the customerName and businessCategories fields.
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:



Box 1: EXISTS
In Azure Cosmos DB, the EXISTS keyword is used with a subquery to determine if a specific value exists within a nested array. The syntax SELECT VALUE bc FROM bc IN c.businessCategories WHERE bc = "retail" creates a temporary set from the array elements and returns true if any element matches the filter.
Box 2: VALUE
Incorrect:
* ARRAY_CONTAINS
Standard way to handle this, but does not work well in subqueries.


Reference:

https://devblogs.microsoft.com/cosmosdb/understanding-how-to-query-arrays-in-azure-cosmos-db/




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 subscription that contains an Azure Cosmos DB for NoSQL account.
You need to write a SQL query that will return multiple items. The solution must meet the following requirements:
-For each item returned, include the current Coordinated Universal Time (UTC) date and time, formatted as an ISO 8601 string.
-Minimize development effort.
What should you use?

  1. a user-defined function
  2. GetCurrentTimestamp()
  3. GetCurrentDateTime()
  4. DateTimePart()

Answer(s): B

Explanation:

GetCurrentTimestamp() is a built-in system function in Azure Cosmos DB's SQL API, which returns the current Coordinated Universal Time (UTC) in ISO 8601 format as a string. It can be used directly in a SQL query without any additional effort. This approach minimizes development effort because it doesn't require custom logic or user-defined functions.




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. The subscription contains an Azure Cosmos DB for NoSQL account named account1 that hosts a container named Container1. Container1 has the analytical store enabled.
You have an Azure Synapse Analytics workspace named Workspace1. Workspace1 contains an Apache Spark pool named Spark1 that runs Spark3. Workspace1 contains the Azure Synapse Link for an Azure Cosmos DB database named DB1.
You need to write the content of a DataFrame to Container1.
How should you complete 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: ("cosmos.oltp")\
To write the content of a Spark DataFrame to an Azure Cosmos DB for NoSQL container using Spark 3 and the Azure Cosmos DB Spark connector, you should use the transactional store format (OLTP)-
Code example:
df.write.format("cosmos.oltp") \
.option("spark.synapse.linkedService", "mycosmosdatabase") \
.option("spark.cosmos.container", "MyContainer") \
.mode('append') \
.save()
Box 2: spark.synapse.linkedService
To write the content of a DataFrame using the Spark 3 OLTP connector in an Azure Synapse Analytics notebook via a linked service, you must use spark.synapse.linkedService.
spark.synapse.linkedService is the correct configuration property when leveraging Azure Synapse Link within a Synapse Spark notebook. It allows Spark to authenticate and connect directly to Azure Cosmos DB through the workspace's configured Linked Service.


Reference:

https://stackoverflow.com/questions/76471055/how-to-run-spark-3-3-0-cosmos-oltp-connector-in-batch-mode




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 the Azure Cosmos DB for NoSQL containers shown in the following table.

You have the items shown in the following table.

When will each item expire? 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: 60 seconds
Item1 is in container1.
Item1 TimeToLive is 60.
Container1 DefaultTimeToLive is -1.
60 overrides -1.
Box 2: Never
Item2 is in container2.
Item2 TimeToLive is 10.
Container1 DefaultTimeToLive null.
Null overrides 10, and items in container2 are never expired.
Box 3: Never
Item3 is in container3.
Item23TimeToLive is -1.
Container1 DefaultTimeToLive 60.
-1 overrides 60. Item3 is never expired.
Note: With Time to Live or TTL, Azure Cosmos DB provides the ability to delete items automatically from a container after a certain time period. By default, you can set time to live at the container level and override the value on a per-item basis. After you set the TTL at a container or at an item level, Azure Cosmos DB will automatically remove these items after the time period, since the time they were last modified.
Time to live for containers and items
The time to live value is set in seconds, and it is interpreted as a delta from the time that an item was last modified. You can set time to live on a container or an item within the container:
1. Time to Live on a container (set using DefaultTimeToLive):
If missing (or set to null), items are not expired automatically.
If present and the value is set to "-1", it is equal to infinity, and items don’t expire by default.
If present and the value is set to some non-zero number "n" – items will expire "n" seconds after their last modified time.
2. Time to Live on an item (set using ttl):
This Property is applicable only if DefaultTimeToLive is present and it is not set to null for the parent container.
If present, it overrides the DefaultTimeToLive value of the parent container.


Reference:

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

You plan to store order data in an Azure Cosmos DB for NoSQL account. The data contains information about orders and their associated items.
You need to develop a model that supports read operations for orders. The solution must minimize the number of requests.
What should you do?

  1. Create a database for orders and a database for order items.
  2. Create a single database that contains a container for orders and a container for order items.
  3. Create a single database that contains one container. Store orders and order items in separate documents in the container.
  4. Create a single database that contains one container. Create a separate document for each order and embed the order items into the order documents.

Answer(s): D

Explanation:

By denormalizing data, your application may need to issue fewer queries and updates to complete common operations.
Typically denormalized data models provide better read performance.
Note: In general, use embedded data models when:
There are contained relationships between entities.
There are one-to-few relationships between entities.
There's embedded data that changes infrequently.
There's embedded data that will not grow without bound.
There's embedded data that is queried frequently together.


Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/sql/modeling-data




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 named account1 and a Log Analytics workspace named Workspace1. Workspace1 stores the logs of account1.
You need to identify which operations used the most request units per second (RU/s) during the last 24 hours.
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:



Box 1: AzureDiagnostics
Find which operations are taking most RU/s
Sort operations by the amount of RU/s they're using.
AzureDiagnostics
| where ResourceProvider=="MICROSOFT.DOCUMENTDB" and Category=="DataPlaneRequests" | where TimeGenerated >= ago(2h)
| summarize max(responseLength_s), max(requestLength_s), max(requestCharge_s), count = count() by OperationName, requestResourceType_s, userAgent_s, collectionRid_s, bin(TimeGenerated, 1h
Box 2: "DataPlaneRequests"
Note: Troubleshoot issues with diagnostics queries
Write simple queries to help troubleshoot issues with your Azure Cosmos DB account using diagnostics logs sent to AzureDiagnostics (legacy) and Resource-specific (preview) tables.
For Azure Diagnostics tables, all data is written into one single table and users need to specify which category they'd like to query.
For resource-specific tables, data is written into individual tables for each category of the resource (not available for table API). We recommend this mode since it makes it much easier to work with the data, provides better discoverability of the schemas, and improves performance across both ingestion latency and query times.


Reference:

https://learn.microsoft.com/en-us/azure/cosmos-db/monitor-logs-basic-queries



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

P
Prem Yadav
7/29/2023 6:20:00 AM

pleaseee upload

A
Ahmed Hashi
7/6/2023 5:40:00 PM

thanks ly so i have information cia

M
mansi
5/31/2023 7:58:00 AM

hello team, i need sap qm dumps for practice

J
Jamil aljamil
12/4/2023 4:47:00 AM

it’s good but not senatios based

C
Cath
10/10/2023 10:19:00 AM

q.119 - the correct answer is b - they are not captured in an update set as theyre data.

P
P
1/6/2024 11:22:00 AM

good matter

S
surya
7/30/2023 2:02:00 PM

please upload c_sacp_2308

S
Sasuke
7/11/2023 10:30:00 PM

please upload the dump. thanks very much !!

V
V
7/4/2023 8:57:00 AM

good questions

T
TTB
8/22/2023 5:30:00 AM

hi, could you please update the latest dump version

T
T
7/28/2023 9:06:00 PM

this question is keep repeat : you are developing a sales application that will contain several azure cloud services and handle different components of a transaction. different cloud services will process customer orders, billing, payment, inventory, and shipping. you need to recommend a solution to enable the cloud services to asynchronously communicate transaction information by using xml messages. what should you include in the recommendation?

G
Gurgaon
9/28/2023 4:35:00 AM

great questions

W
wasif
10/11/2023 2:22:00 AM

its realy good

S
Shubhra Rathi
8/26/2023 1:12:00 PM

oracle 1z0-1059-22 dumps

L
Leo
7/29/2023 8:48:00 AM

please share me the pdf..

A
AbedRabbou Alaqabna
12/18/2023 3:10:00 AM

q50: which two functions can be used by an end user when pivoting an interactive report? the correct answer is a, c because we do not have rank in the function pivoting you can check in the apex app

R
Rohan Limaye
12/30/2023 8:52:00 AM

best to practice

A
Aparajeeta
10/13/2023 2:42:00 PM

so far it is good

V
Vgf
7/20/2023 3:59:00 PM

please provide me the dump

D
Deno
10/25/2023 1:14:00 AM

i failed the cisa exam today. but i have found all the questions that were on the exam to be on this site.

C
CiscoStudent
11/15/2023 5:29:00 AM

in question 272 the right answer states that an autonomous acces point is "configured and managed by the wlc" but this is not what i have learned in my ccna course. is this a mistake? i understand that lightweight aps are managed by wlc while autonomous work as standalones on the wlan.

P
pankaj
9/28/2023 4:36:00 AM

it was helpful

U
User123
10/8/2023 9:59:00 AM

good question

V
vinay
9/4/2023 10:23:00 AM

really nice

U
Usman
8/28/2023 10:07:00 AM

please i need dumps for isc2 cybersecuity

Q
Q44
7/30/2023 11:50:00 AM

ans is coldline i think

A
Anuj
12/21/2023 1:30:00 PM

very helpful

G
Giri
9/13/2023 10:31:00 PM

can you please provide dumps so that it helps me more

A
Aaron
2/8/2023 12:10:00 AM

thank you for providing me with the updated question and answers. this version has all the questions from the exam. i just saw them in my exam this morning. i passed my exam today.

S
Sarwar
12/21/2023 4:54:00 PM

how i can see exam questions?

C
Chengchaone
9/11/2023 10:22:00 AM

can you please upload please?

M
Mouli
9/2/2023 7:02:00 AM

question 75: option c is correct answer

J
JugHead
9/27/2023 2:40:00 PM

please add this exam

S
sushant
6/28/2023 4:38:00 AM

please upoad

AI Tutor 👋 I’m here to help!