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

Questions 1–5

1. 1foundation · easy

   An application frequently runs queries that filter on both lastName and firstName in an Azure Cosmos DB for NoSQL container. Which indexing feature would best improve the performance of these multi-property queries?

   • AA spatial index on the address property
   • BA hash index on lastName only
   • CA range index on firstName only
   • DA composite index on (lastName, firstName)
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   A developer notices that a query in Azure Cosmos DB for NoSQL is consuming a high number of request units (RUs). The query filters on a property that is not currently indexed. What is the most direct way to optimize the query's performance?

   • AAdd the property to the indexing policy
   • BDisable indexing on the container
   • CChange the partition key of the container
   • DIncrease the container's provisioned throughput
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   A logging system writes millions of small documents to an Azure Cosmos DB for NoSQL container each day. The documents are rarely read, and when they are read, it is by ID only. Which indexing strategy is most appropriate for this write-heavy workload?

   • AEnable automatic indexing on all properties to ensure future query flexibility
   • BCreate a composite index on the timestamp and severity properties
   • CSet the indexing mode to None to eliminate all index overhead
   • DUse a custom policy that indexes only the id property
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   A reporting query in Azure Cosmos DB for NoSQL filters on a timestamp property using a range condition such as timestamp > '2024-01-01'. Which index type should be configured on that property to optimize this query?

   • ARange index
   • BComposite index
   • CSpatial index
   • DHash index
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A healthcare application stores patient records in Azure Cosmos DB for NoSQL. The application runs many read-only queries that filter by lastName and firstName, and also by lastName and dateOfBirth. The data is rarely updated. The team wants to maximize read performance. What should the indexing policy include?

   • AAdd a single composite index on (lastName, firstName, dateOfBirth)
   • BAdd range indexes on lastName, firstName, and dateOfBirth individually
   • CAdd composite indexes on (lastName, firstName) and (lastName, dateOfBirth)
   • DSet the indexing mode to None and rely on point reads
   Reveal Solution Discussion Select an answer first