Merge pull request #50313 from wwlpublish/a0180384e3f8cbc89e953adbe9ad67b2b8c34dc846751ae569848808d2998877-live

v-ccolin · web-flow · commit daaccc16858a · 2025-05-07T10:01:33.000+01:00
Modules/M01-choose-indexes-azure-cosmos-db-sql-api
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/1-introduction.yml b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/1-introduction.yml
@@ -2,15 +2,16 @@
 uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.introduction
 title: Introduction
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Introduction
   description: "Introduction"
-  ms.date: 04/02/2025
+  ms.date: 05/07/2025
   author: wwlpublish
   ms.author: calopez
   ms.topic: unit
-azureSandbox: false
-labModal: false
+  ms.custom:
+  - N/A
 durationInMinutes: 2
 content: |
-  [!include[](includes/1-introduction.md)]
-
+  [!include[](includes/1-introduction.md)]
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/2-index-usage.yml b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/2-index-usage.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.index-usage
 title: Index usage
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Index usage
   description: "Index usage"
-  ms.date: 04/02/2025
+  ms.date: 05/07/2025
   author: wwlpublish
   ms.author: calopez
   ms.topic: unit
-azureSandbox: false
-labModal: false
+  ms.custom:
+  - N/A
 durationInMinutes: 10
 content: |
-  [!include[](includes/2-index-usage.md)]
+  [!include[](includes/2-index-usage.md)]
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/3-review-read-heavy-index-patterns.yml b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/3-review-read-heavy-index-patterns.yml
@@ -2,15 +2,16 @@
 uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.review-read-heavy-index-patterns
 title: Review read-heavy index patterns
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Review read-heavy index patterns
   description: "Review read-heavy index patterns"
-  ms.date: 04/02/2025
+  ms.date: 05/07/2025
   author: wwlpublish
   ms.author: calopez
   ms.topic: unit
-azureSandbox: false
-labModal: false
+  ms.custom:
+  - N/A
 durationInMinutes: 5
 content: |
-  [!include[](includes/3-review-read-heavy-index-patterns.md)]
-
+  [!include[](includes/3-review-read-heavy-index-patterns.md)]
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/4-review-write-heavy-index-patterns.yml b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/4-review-write-heavy-index-patterns.yml
@@ -2,15 +2,16 @@
 uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.review-write-heavy-index-patterns
 title: Review write-heavy index patterns
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Review write-heavy index patterns
   description: "Review write-heavy index patterns"
-  ms.date: 04/02/2025
+  ms.date: 05/07/2025
   author: wwlpublish
   ms.author: calopez
   ms.topic: unit
-azureSandbox: false
-labModal: false
+  ms.custom:
+  - N/A
 durationInMinutes: 4
 content: |
-  [!include[](includes/4-review-write-heavy-index-patterns.md)]
-
+  [!include[](includes/4-review-write-heavy-index-patterns.md)]
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/5-exercise-optimize-containers-index-policy-common-operations.yml b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/5-exercise-optimize-containers-index-policy-common-operations.yml
@@ -2,12 +2,16 @@
 uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.exercise-optimize-containers-index-policy-for-common-operations
 title: Exercise - Optimize an Azure Cosmos DB for NoSQL container's index policy for common operations
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Exercise - Optimize an Azure Cosmos DB for NoSQL container's index policy for common operations
   description: "Exercise - Optimize an Azure Cosmos DB for NoSQL container's index policy for common operations"
-  ms.date: 04/02/2025
+  ms.date: 05/07/2025
   author: wwlpublish
   ms.author: calopez
   ms.topic: unit
+  ms.custom:
+  - N/A
 durationInMinutes: 15
 content: |
-  [!include[](includes/5-exercise-optimize-containers-index-policy-common-operations.md)]
+  [!include[](includes/5-exercise-optimize-containers-index-policy-common-operations.md)]
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/6-knowledge-check.yml b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/6-knowledge-check.yml
@@ -1,19 +1,22 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.knowledge-check
-title: Knowledge check
+title: Module assessment
 metadata:
-  title: Knowledge check
+  adobe-target: true
+  prefetch-feature-rollout: true
+  title: Module assessment
   description: "Knowledge check"
-  ms.date: 04/02/2025
+  ms.date: 05/07/2025
   author: wwlpublish
   ms.author: calopez
   ms.topic: unit
-azureSandbox: false
-labModal: false
+  ms.custom:
+  - N/A
 durationInMinutes: 5
 quiz:
+  title: ""
   questions:
-  - content: "The application team wrote a SQL query for Azure Cosmos DB for NoSQL with the following text: ``SELECT * FROM c WHERE c.sku = 'RD3387G'``. Which lookup method will the query engine use for the **sku** filter?"
+  - content: "Your team has written a SQL query for Azure Cosmos DB for NoSQL with the following text: ``SELECT * FROM c WHERE c.sku = 'RD3387G'``. Which lookup method will the query engine use for the **sku** filter?"
     choices:
     - content: "``Full scan``"
       isCorrect: false
@@ -24,7 +27,7 @@ quiz:
     - content: "``Index seek``."
       isCorrect: true
       explanation: "Correct. The equality filter allows the query engine to perform a seek of a specific value."
-  - content: "Which property of an indexing policy should be set to disable all indexing for a container?"
+  - content: "Which property of an indexing policy should you set to disable all indexing for a container?"
     choices:
     - content: "``indexingMode``"
       isCorrect: true
@@ -34,4 +37,4 @@ quiz:
       explanation: "Incorrect. The ``excludedPaths`` property determines which paths are excluded from the index, not whether the indexer runs."
     - content: "``automatic``"
       isCorrect: false
-      explanation: "Incorrect. Disabling ``automatic`` indexing using a boolean value of ``false`` doesn't disable all indexing for the container."
+      explanation: "Incorrect. Disabling ``automatic`` indexing using a boolean value of ``false`` doesn't disable all indexing for the container."
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/7-summary.yml b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/7-summary.yml
@@ -2,14 +2,16 @@
 uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.summary
 title: Summary
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Summary
   description: "Summary"
-  ms.date: 04/02/2025
+  ms.date: 05/07/2025
   author: wwlpublish
   ms.author: calopez
   ms.topic: unit
-azureSandbox: false
-labModal: false
+  ms.custom:
+  - N/A
 durationInMinutes: 2
 content: |
-  [!include[](includes/7-summary.md)]
+  [!include[](includes/7-summary.md)]
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/1-introduction.md b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/1-introduction.md
@@ -4,3 +4,4 @@ After completing this module, you'll be able to:
 
 - Customize an indexing policy for read-heavy workloads
 - Customize an indexing policy for write-heavy workloads
+
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/2-index-usage.md b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/2-index-usage.md
@@ -7,7 +7,7 @@ The query engine evaluates query filters and then traverses the index of your co
 | **Full scan** | The query engine will load the items, in their entirety, to the transactional store to evaluate the filters. | This type of scan does not use the index; however, the RU charge for loading items is based on the number of items in the entire container. |
 
 > [!NOTE]
-> An index scan can range in complexity from an efficient and precise index scan, to a more involved expanded index scan, and finally the most complex full index scan.
+> An index scan can range in complexity from an efficient and precise index seek, to a more involved expanded index scan, and finally the most complex full index scan.
 
 As a query developer, it’s essential to understand which queries will require a seek vs. a scan. It’s also important to understand which queries cannot use the index and will require a full scan. Specifically, you should optimize your queries to use filter predicates that use the most efficient lookup method.
 
@@ -124,3 +124,4 @@ The query engine will traverse the tree in the following order:
 This binary search moved the query, in complexity, from an index seek to a precise index scan. The query engine scans all possible values in the index, but this is still far more efficient than a full scan of all JSON content. Queries that use range comparisons and string functions often will require the use of an index scan.
 
 There are edge cases where the query engine cannot use the index to evaluate a filter. These cases will require the query engine to load the JSON content of all items into the transactional store before evaluating the filter. Full scans can potentially have significant request unit charges as the charge scales linearly with the total number of items in the container. While full scans are rare, it is essential to know that they are possible when using specific built-in functions in query filters.
+
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/3-review-read-heavy-index-patterns.md b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/3-review-read-heavy-index-patterns.md
@@ -84,3 +84,4 @@ Alternatively, you can exclude all paths and only selectively include the **name
 
 > [!TIP]
 > The preferred approach is to index everything by default and selectively exclude specific paths. Changes to the index policy require an index rebuild. Applying this preferred approach allows your application to adapt to schema changes making new properties available for queries immediately.
+
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/4-review-write-heavy-index-patterns.md b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/4-review-write-heavy-index-patterns.md
@@ -1,6 +1,6 @@
 If you want your NoSQL queries to be endlessly flexible, why exclude any paths at all? Well, each insert or update operation requires the indexer to run to update the inverted index with data from your newly created or updated item. More oversized items, or bulk workloads, can cause the indexing to use many RU/s or take a significant amount of time.
 
-Let’s consider an example JSON object that is much larger than previous examples.
+Let’s consider an example JSON object that is larger than previous examples.
 
 ```json
 {
@@ -76,7 +76,7 @@ WHERE
     p.price = <numeric-value>
 ```
 
-An indexing policy that excludes all paths, except for the **price** property path, would be appropriate here. This policy will still index items, but it will do so quickly because only one property is added to the inverted index.
+An indexing policy that excludes all paths, except for the **price** property path, would be appropriate here. This policy will still index items, but it does so quickly because only one property is added to the inverted index.
 
 ```json
 {
@@ -96,9 +96,9 @@ An indexing policy that excludes all paths, except for the **price** property pa
 ```
 
 > [!TIP]
-> Again, the drawback to this approach is that you will need to update the index anytime you change your schema.
+> Again, the drawback to this approach is that you'll need to update the index anytime you change your schema.
 
-Here is a diagram of the inverted index showing that it only has a single property to traverse and then multiple potential values.
+Here's a diagram of the inverted index showing that it only has a single property to traverse and then multiple potential values.
 
 ![Inverted tree with a single property node of price and multiple child nodes](../media/4-inverted-tree.png)
 
@@ -109,3 +109,4 @@ Suppose your application is write-heavy and only ever does point reads using the
   "indexingMode": "none",
 }
 ```
+
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/5-exercise-optimize-containers-index-policy-common-operations.md b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/5-exercise-optimize-containers-index-policy-common-operations.md
@@ -1,8 +1,7 @@
-
 ### Set up environment
 
 > [!NOTE]
-> To complete this exercise, you will need a [Microsoft Azure subscription](https://azure.microsoft.com/free?azure-portal=true) in which you have administrative access.
+> To complete this exercise, you'll need a [Microsoft Azure subscription](https://azure.microsoft.com/free?azure-portal=true) in which you have administrative access.
 
 To set up the lab environment for this exercise, sign into your Azure subscription and follow these instructions to provision your Azure resources:
 
@@ -15,3 +14,4 @@ To set up the lab environment for this exercise, sign into your Azure subscripti
 Launch the exercise and follow the instructions.
 
 [![Button to launch exercise.](../media/launch-exercise.png)](https://go.microsoft.com/fwlink/?linkid=2294943&azure-portal=true)
+
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/7-summary.md b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/includes/7-summary.md
@@ -13,3 +13,4 @@ For more information about the topics discussed in this module, see:
 
 [/azure/cosmos-db/index-overview]: /azure/cosmos-db/index-overview
 [/azure/cosmos-db/index-policy]: /azure/cosmos-db/index-policy
+
diff --git a/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/index.yml b/learn-pr/wwl-data-ai/choose-indexes-azure-cosmos-db-sql-api/index.yml
@@ -1,22 +1,29 @@
 ### YamlMime:Module
 uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api
 metadata:
+  adobe-target: true
+  prefetch-feature-rollout: true
   title: Customize an indexing policy in Azure Cosmos DB for NoSQL
   description: "Tune the indexing policy based on your SQL queries in Azure Cosmos DB for NoSQL."
-  ms.date: 04/02/2025
+  ms.date: 05/07/2025
   author: wwlpublish
   ms.author: calopez
   ms.topic: module-standard-task-based
+  ms.collection: N/A
+  ms.custom:
+  - N/A
   ms.service: azure-cosmos-db
   ms.subservice: nosql
+  ai-usage: human-only
 title: Customize an indexing policy in Azure Cosmos DB for NoSQL
 summary: Tune the indexing policy based on your SQL queries in Azure Cosmos DB for NoSQL.
 abstract: |
   After completing this module, you'll be able to:
-  *   Customize an indexing policy for read-heavy workloads
-  *   Customize an indexing policy for write-heavy workloads
-prerequisites: |
-  Before starting this module, you should have experience of building cloud applications with Microsoft C# or a similar programming language.
+
+  -   Customize an indexing policy for read-heavy workloads
+
+  -   Customize an indexing policy for write-heavy workloads
+prerequisites: Before starting this module, you should have experience of building cloud applications with Microsoft C# or a similar programming language.
 iconUrl: /training/achievements/azure-cosmos-db-sql-api-choose-index.svg
 levels:
 - intermediate
@@ -35,4 +42,4 @@ units:
 - learn.wwl.choose-indexes-azure-cosmos-db-sql-api.knowledge-check
 - learn.wwl.choose-indexes-azure-cosmos-db-sql-api.summary
 badge:
-  uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.badge
+  uid: learn.wwl.choose-indexes-azure-cosmos-db-sql-api.badge

Original file line number	Diff line number	Diff line change
`@@ -4,3 +4,4 @@ After completing this module, you'll be able to:`
`4`	`4`
`5`	`5`	`- Customize an indexing policy for read-heavy workloads`
`6`	`6`	`- Customize an indexing policy for write-heavy workloads`
	`7`	`+`
Original file line number	Diff line number	Diff line change
`@@ -84,3 +84,4 @@ Alternatively, you can exclude all paths and only selectively include the **name`
`84`	`84`
`85`	`85`	`> [!TIP]`
`86`	`86`	`> The preferred approach is to index everything by default and selectively exclude specific paths. Changes to the index policy require an index rebuild. Applying this preferred approach allows your application to adapt to schema changes making new properties available for queries immediately.`
	`87`	`+`