D.

Increase the number of request units per second (RU/s) allocated to the con-product
and con-productVendor containers.

Explanation:
App1 queries the con-product and con-productVendor containers.
Note: Request unit is a performance currency abstracting the system resources such as
CPU, IOPS, and memory that are required to perform the database operations supported
by Azure Cosmos DB.
Scenario:
Develop an app named App1 that will run from all locations and query the data in account1.
Once multi-region writes are configured, maximize the performance of App1 queries
against the data in account1.
Whenever there are multiple solutions for a requirement, select the solution that provides
the best performance, as long as there are no additional costs associated.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/consistency-levels

A.

Create a container for Author and a container for Book. In each Author document,
embed bookId for each book by the author. In each Book document embed authorId of
each author.

Explanation:
Store multiple entity types in the same container.

C.

Direct mode over TCP

Explanation:
Scenario: 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 DNS endpoint when accessing
account2.
By using Azure Private Link, you can connect to an Azure Cosmos account via a private
endpoint. The private endpoint is a set of private IP addresses in a subnet within your
virtual network.
When you're using Private Link with an Azure Cosmos account through a direct mode
connection, you can use only the TCP protocol. The HTTP protocol is not currently
supported.
Reference:
https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-configure-private-endpoints

C.

Register the trigger as a pre-trigger.

Explanation:
C: When triggers are registered, you can specify the operations that it can run with.
F: When executing, pre-triggers are passed in the RequestOptions object by specifying
PreTriggerInclude and then passing the name of the trigger in a List object.
Reference: https://docs.microsoft.com/en-us/azure/cosmos-db/sql/how-to-use-storedprocedures-
triggers-udfs

D.

the device ID

Explanation:
The partition key is what will determine how data is routed in the various partitions by
Cosmos DB and needs to make sense in the context of your specific scenario. The IoT
Device ID is generally the "natural" partition key for IoT applications.
Scenario: The iotdb database will contain two containers named con-iot1 and con-iot2.
Ensure that Azure Cosmos DB costs for IoT-related processing are predictable.
Reference:
https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/iot-usingcosmos-
db

D.

a function that receives items pushed from the conflicts feed and is triggered by an Azure Cosmos DB trigger

Explanation: The Azure Cosmos DB Trigger uses the Azure Cosmos DB Change Feed to
listen for inserts and updates across partitions. The change feed publishes inserts and
updates, not deletions.
Reference: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindingscosmosdb