changed files by pdets auto publish service, publishid[d83e3988-3063-4069-ab09-51dab4522efd] and do [publish].

Author: wwlpublish

learn-pr/wwl-azure/understand-app-service-deployment-slots/4a-exercise-swap-deployment-slots.yml

@@ -1,10 +1,10 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.understand-app-service-deployment-slots.knowledge-check
-title: Knowledge check
+title: Module assessment
 metadata:
   adobe-target: true
   prefetch-feature-rollout: true
-  title: Knowledge check
+  title: Module assessment
   description: "Knowledge check"
   ms.date: 05/13/2025
   author: wwlpublish
@@ -13,5 +13,28 @@ metadata:
   ms.custom:
   - N/A
 durationInMinutes: 3
-content: |
-  [!include[](includes/6-knowledge-check.md)]
+quiz:
+  title: "Check your knowledge"
+  questions:
+  - content: "By default, all client requests to the app's production URL (`http://<app_name>.azurewebsites.net`) are routed to the production slot. One can automatically route a portion of the traffic to another slot. What is the default routing rule applied to new deployment slots?"
+    choices:
+    - content: "0%"
+      isCorrect: true
+      explanation: "Correct. By default, new slots are given a routing rule of `0%`."
+    - content: "10%"
+      isCorrect: false
+      explanation: "Incorrect. By default, new slots are given a routing rule of `0%`."
+    - content: "20%"
+      isCorrect: false
+      explanation: "Incorrect. By default, new slots are given a routing rule of `0%`."
+  - content: "Some configuration elements follow the content across a swap (not slot specific), whereas other configuration elements stay in the same slot after a swap (slot specific). Which of the following settings are swapped?"
+    choices:
+    - content: "Publishing endpoints"
+      isCorrect: false
+      explanation: "Incorrect. Publishing endpoints aren't swapped."
+    - content: "WebJobs content"
+      isCorrect: true
+      explanation: "Correct. WebJobs content is swapped."
+    - content: "WebJobs schedulers"
+      isCorrect: false
+      explanation: "Incorrect. WebJobs schedulers aren't swapped."

learn-pr/wwl-azure/understand-app-service-deployment-slots/6-knowledge-check.yml

@@ -1,9 +1,9 @@
-When you deploy your web app, web app on Linux, mobile back end, or API app to Azure App Service, you can use a separate deployment slot instead of the default production slot. This approach is available if you run in the **Standard**, **Premium**, or **Isolated** App Service plan tier. Deployment slots are live apps with their own host names. App content and configuration elements can be swapped between two deployment slots, including the production slot.
+When you deploy your web app, web app on Linux, mobile back end, or API app to Azure App Service, you can use a separate deployment slot instead of the default production slot. This approach is available if you run in the **Standard**, **Premium**, or **Isolated** App Service plan tier. Deployment slots are live apps with their own host names. App content and configurations elements can be swapped between two deployment slots, including the production slot.
 
 Deploying your application to a nonproduction slot has the following benefits:
 
-* Validate app changes in a staging deployment slot before swapping it with the production slot.
-* Deploying an app to a slot first and then swapping it into production ensures that all instances of the slot are warmed up before being swapped into production. This eliminates downtime when you deploy your app. The traffic redirection is seamless, and no requests are dropped because of swap operations. You can automate this entire workflow by configuring auto swap when preswap validation isn't needed.
+* You can validate app changes in a staging deployment slot before swapping it with the production slot.
+* Deploy an app to a slot first and swapping it into production makes sure that all instances of the slot are warmed up before being swapped into production. This eliminates downtime when you deploy your app. The traffic redirection is seamless, and no requests are dropped because of swap operations. You can automate this entire workflow by configuring auto swap when pre-swap validation isn't needed.
 * After a swap, the previous production app is located in the staging slot. If the changes swapped into the production slot aren't as you expect, you can perform the same swap immediately to get your "last known good site" back.
 
 Each App Service plan tier supports a different number of deployment slots. There's no extra charge for using deployment slots. To find out the number of slots your app's tier supports, visit [App Service limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#app-service-limits).

learn-pr/wwl-azure/understand-app-service-deployment-slots/includes/2-app-service-staging-environments.md

@@ -43,7 +43,6 @@ units:
 - learn.wwl.understand-app-service-deployment-slots.explore-staging-environments
 - learn.wwl.understand-app-service-deployment-slots.examine-slot-swapping
 - learn.wwl.understand-app-service-deployment-slots.swap
-- learn.wwl.exercise-swap-deployment-slots
 - learn.wwl.understand-app-service-deployment-slots.route-traffic
 - learn.wwl.understand-app-service-deployment-slots.knowledge-check
 - learn.wwl.understand-app-service-deployment-slots.summary