Module updates

Author: Rob-Barefoot

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/5-validate-success.yml

@@ -10,6 +10,6 @@ metadata:
   ms.topic: unit
   ms.custom:
   - N/A
-durationInMinutes: 10
+durationInMinutes: 2
 content: |
   [!include[](includes/5-validate-success.md)]

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/7-knowledge-check.yml

@@ -0,0 +1,51 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-organize-resources-tags-locks.knowledge-check
+title: Knowledge check
+metadata:
+  title: Knowledge check
+  description: "Knowledge check"
+  ms.date: 03/29/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 5
+content: |
+  [!include[](includes/7-knowledge-check.md)]
+quiz:
+  title: "Check your knowledge"
+  questions:
+  - content: "What is the primary purpose of applying resource tags in Azure?"
+    choices:
+    - content: "To restrict who can access a resource"
+      isCorrect: false
+      explanation: "Access control is managed through RBAC role assignments, not tags."
+    - content: "To organize resources for cost tracking and management"
+      isCorrect: true
+      explanation: "Tags are key-value pairs that help you categorize resources for cost allocation, automation, and operational management."
+    - content: "To prevent resources from being deleted"
+      isCorrect: false
+      explanation: "Resource locks prevent deletion, not tags."
+  - content: "What does a read-only resource lock prevent?"
+    choices:
+    - content: "Only deletion of the resource"
+      isCorrect: false
+      explanation: "A delete lock prevents only deletion. A read-only lock is more restrictive."
+    - content: "Modifications and deletion of the resource"
+      isCorrect: true
+      explanation: "A read-only lock prevents both changes and deletion. You can view the resource but cannot modify or delete it."
+    - content: "All access to the resource including viewing"
+      isCorrect: false
+      explanation: "A read-only lock still allows you to view the resource. It blocks modifications and deletion only."
+  - content: "What must you do before you can delete a resource that has a delete lock?"
+    choices:
+    - content: "Disable the lock temporarily using Azure Policy"
+      isCorrect: false
+      explanation: "Locks are not managed through Azure Policy. You must remove the lock directly."
+    - content: "Contact Azure Support to override the lock"
+      isCorrect: false
+      explanation: "Lock removal does not require Azure Support. Authorized users can remove locks directly."
+    - content: "Remove the lock first"
+      isCorrect: true
+      explanation: "You must explicitly remove a delete lock before you can delete the resource. This is a deliberate safeguard against accidental deletion."

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/8-summary.yml

@@ -0,0 +1,15 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.guided-project-organize-resources-tags-locks.summary
+title: Summary
+metadata:
+  title: Summary
+  description: "Summary"
+  ms.date: 03/25/2026
+  author: wwlpublish
+  ms.author: robbarefoot
+  ms.topic: unit
+  ms.custom:
+  - N/A
+durationInMinutes: 2
+content: |
+  [!include[](includes/8-summary.md)]

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/includes/2-exercise-create-resources-apply-tags.md

@@ -115,6 +115,4 @@ Use tags to filter the resource list and see only the resources that belong to a
 10. Select the **X** on the right side of the filter to clear it and show all resources again.
 
 > [!NOTE]
-> **Validation step:** Confirm filtering by **department** tag shows only the correct storage account for each department value.
-
-> [!NOTE]
+> **Validation step:** Confirm filtering by **department** tag shows only the correct storage account for each department value.

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/includes/3-exercise-apply-resource-locks.md

@@ -48,6 +48,4 @@ Add a read-only lock at the resource group level. A read-only lock prevents any
 > You should also see the **prevent-delete** lock listed here with a scope of the storage account—resource group locks inherit and display locks from child resources.
 
 > [!NOTE]
-> **Validation step:** Confirm the resource group Locks pane shows both the **read-only-rg** lock and the **prevent-delete** lock (scoped to the storage account).
-
-> [!NOTE]
+> **Validation step:** Confirm the resource group Locks pane shows both the **read-only-rg** lock and the **prevent-delete** lock (scoped to the storage account).

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/includes/4-exercise-test-lock-enforcement.md

@@ -70,6 +70,4 @@ Verify that removing the locks allows previously blocked operations to succeed.
 5.  Select the **delete** icon (trash can) next to the **lock-test** tag to remove it, then select **Apply** to clean up.
 
 > [!NOTE]
-> **Validation step:** Verify the **lock-test** tag was saved successfully, proving that removing the read-only lock restored write permissions.
-
-> [!NOTE]
+> **Validation step:** Verify the **lock-test** tag was saved successfully, proving that removing the read-only lock restored write permissions.

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/includes/5-validate-success.md

@@ -1,5 +1,3 @@
-## Validate success
-
 Review the validation steps you completed during the exercises. Confirm that each item below is true before moving on.
 
 -   [ ] The resource group displays both tags (**department: development** and **environment: test**).

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/includes/6-clean-up-resources.md

@@ -1,11 +1,9 @@
-## Clean up resources
-
 Complete these steps to avoid ongoing charges from the resources you created in this project.
 
 > [!WARNING]
 > Resource deletion is permanent. Verify that you're deleting only resources created for this guided project before you proceed.
 
-### Verify locks are removed
+## Verify locks are removed
 
 Resource locks block deletion. Confirm all locks are removed before you delete the resource group.
 
@@ -15,7 +13,7 @@ Resource locks block deletion. Confirm all locks are removed before you delete t
 4.  If any locks remain, select each lock and select **Delete** to remove it.
 5.  Open each storage account, select **Locks** in the left menu, and confirm no locks remain.
 
-### Delete the resource group
+## Delete the resource group
 
 Deleting the resource group removes both storage accounts and all tags automatically.
 
@@ -26,7 +24,7 @@ Deleting the resource group removes both storage accounts and all tags automatic
 4.  In the confirmation dialog that appears, select **Delete** again to confirm.
 5.  Wait for the notification that confirms the resource group is deleted.
 
-### Verify cleanup
+## Verify cleanup
 
 1.  In the portal search bar, search for **Resource groups** and confirm **rg-gp-tags-locks** no longer appears in the list.
 2.  In the portal search bar, search for **Storage accounts** and confirm neither **stgptagslock** nor **stgptagsops** appears in the list.

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/includes/7-knowledge-check.md

@@ -0,0 +1 @@
+Choose the best response for each question.

learn-pr/wwl-azure/guided-project-organize-resources-tags-locks/includes/8-summary.md

@@ -0,0 +1,11 @@
+You completed a full guided project that mapped to a real IT operations task.
+
+## What you accomplished
+
+-   Created resources and applied consistent organizational tags.
+-   Applied delete and read-only resource locks to protect infrastructure.
+-   Tested that locks enforced restrictions and then removed them when no longer needed.
+
+## Next step
+
+Repeat the project once from memory to reinforce the workflow and decision points.