You have a container named container1 in an Azure Cosmos DB Core (SQL) API account.
The container1 container has 120 GB of data.
The following is a sample of a document in container1.

You are designing an Azure Cosmos DB Core (SQL) API solution to store data from IoT
devices. Writes from the devices will be occur every second.
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?

You have an Azure Cosmos DB Core (SQL) API account named account1.
You have the Azure virtual networks and subnets shown in the following table.

You have an Azure Cosmos DB Core (SQL) API account that is configured for multi-region
writes. The account contains a database that has two containers named container1 and
container2.
The following is a sample of a document in container1:
{
"customerId": 1234,
"firstName": "John",
"lastName": "Smith",
"policyYear": 2021
}
The following is a sample of a document in container2:
{
"gpsId": 1234,
"latitude": 38.8951,
"longitude": -77.0364
}
You need to configure conflict resolution to meet the following requirements:
For container1 you must resolve conflicts by using the highest value for policyYear.
For container2 you must resolve conflicts by accepting the distance closest to latitude:
40.730610 and longitude: -73.935242.
Administrative effort must be minimized to implement the solution.
What should you configure for each container? To answer, drag the appropriate
configurations to the correct containers. Each configuration 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.

Note: This question is part of a series of questions that present the same scenario. Each
question in the series contains a unique solution that might meet the stated goals. Some
question sets might have more than one correct solution, while others might not have a
correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result,
these questions will not appear in the review screen.
You have a container named container1 in an Azure Cosmos DB Core (SQL) API account.
You need to make the contents of container1 available as reference data for an Azure
Stream Analytics job.
Solution: You create an Azure Synapse pipeline that uses Azure Cosmos DB Core (SQL)
API as the input and Azure Blob Storage as the output.
Does this meet the goal?

You have a container in an Azure Cosmos DB Core (SQL) API account. The container
stores telemetry data from IoT devices. The container uses telemetryId as the partition key
and has a throughput of 1,000 request units per second (RU/s). Approximately 5,000 IoT
devices submit data every five minutes by using the same telemetryId value.
You have an application that performs analytics on the data and frequently reads telemetry
data for a single IoT device to perform trend analysis.
The following is a sample of a document in the container.

You need to reduce the amount of request units (RUs) consumed by the analytics
application.
What should you do?

You have a container named container1 in an Azure Cosmos DB Core (SQL) API account.
You need to provide a user named User1 with the ability to insert items into container1 by
using role-based access control (RBAC). The solution must use the principle of least
privilege.
Which roles should you assign to User1?

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