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

Questions 11–15

1. 11expert · hard

   A SaaS provider runs a multi-tenant application on Azure Cosmos DB for NoSQL. Each tenant has a container with a custom indexing policy. The operations team reports that one tenant's container has high write RU consumption and slow query performance. The queries in that container filter by tenantId and status, and also by tenantId and createdDate. The current policy includes a wildcard index on all paths and a composite index on (tenantId, status). The team wants to reduce write RU consumption while maintaining or improving query performance. What should they do?

   • ASet indexing mode to None and rely on point reads by ID
   • BReplace the wildcard index with explicit paths for tenantId, status, and createdDate, and add a composite index on (tenantId, createdDate)
   • CKeep the current policy but change the indexing mode to Lazy
   • DKeep the wildcard index but change the composite index to (tenantId, status, createdDate)
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   An application queries an Azure Cosmos DB for NoSQL container with equality filters on a property named category. Which index type is most appropriate for this property to optimize equality queries?

   • AComposite index
   • BRange index
   • CHash index
   • DSpatial index
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A media company stores video metadata in Azure Cosmos DB for NoSQL. Queries frequently filter by genre and year, and also by genre and rating. The team notices that queries are consuming high RUs. They want to reduce RU consumption without changing the application code. What should they do?

   • AAdd a single composite index on (genre, year, rating)
   • BSet the indexing mode to None
   • CAdd composite indexes on (genre, year) and (genre, rating)
   • DChange all indexes to hash type
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A retail company uses Azure Cosmos DB for NoSQL to store product catalog data. The application runs a dashboard that frequently queries products by category and price range, and also by category and brand. The team wants to minimize query latency for these two patterns while keeping the indexing overhead low for the occasional product updates. What should the indexing policy include?

   • ASet the indexing mode to Consistent and add a wildcard path for all properties
   • BEnable range indexing on the category, price, and brand properties individually
   • CA single composite index on (category ASC, price ASC, brand ASC)
   • DA composite index on (category ASC, price ASC) and another on (category ASC, brand ASC)
   Reveal Solution Discussion Select an answer first
6. 15foundation · easy

   When configuring a custom indexing policy in the Azure portal for an Azure Cosmos DB for NoSQL container, which action is performed in the 'Indexing Policy' editor?

   • AEditing the JSON policy to include or exclude paths and set index types
   • BSelecting the partition key for the container
   • CSetting the default consistency level for the container
   • DConfiguring the throughput for the container
   Reveal Solution Discussion Select an answer first