Define and Implement an Indexing Strategy for Azure Cosmos DB for NoSQL DP-420 Practice Questions (Page 4)

Questions 16–17

1. 16foundation · easy

   A developer is designing an Azure Cosmos DB for NoSQL container that will serve a reporting application. The application will run frequent point reads by ID and occasional queries that filter on a single property. The team expects a high ratio of read operations to write operations. Which indexing strategy best supports this workload?

   • ADisable indexing on the container to reduce write overhead
   • BUse the default automatic indexing policy with a range index on the filtered property
   • CUse a custom policy that indexes only the partition key
   • DSet the indexing mode to None and rely on the partition key for all reads
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A gaming company stores player session data in Azure Cosmos DB for NoSQL. The application writes millions of session records per day and only occasionally queries by playerId and sessionDate. The team wants to reduce write RU consumption. What should the indexing policy be?

   • ASet indexing mode to None and use a composite index on (playerId, sessionDate)
   • BExclude all paths except playerId and sessionDate, and add a composite index on (playerId, sessionDate)
   • CSet indexing mode to None and rely on point reads by ID
   • DKeep the default policy and add a composite index on (playerId, sessionDate)
   Reveal Solution Discussion Select an answer first