changed files by pdets auto publish service, publishid[2fb3d136-0085-49b9-8987-02e22a352924] and do [publish].

Author: wwlpublish

learn-pr/wwl-azure/azure-event-grid/9-knowledge-check.yml

@@ -13,5 +13,60 @@ metadata:
   ms.custom:
   - N/A
 durationInMinutes: 3
-content: |
-  [!include[](includes/9-knowledge-check.md)]
+quiz:
+  questions:
+  - content: "Which of the following event schema properties requires a value?"
+    choices:
+    - content: "Topic"
+      isCorrect: false
+      explanation: "Incorrect. Event Grid will provide this value."
+    - content: "Data"
+      isCorrect: false
+      explanation: "Incorrect. A value isn't required in this property."
+    - content: "Subject"
+      isCorrect: true
+      explanation: "Correct. The subject property specifies the publisher-defined path to the event subject and is required."
+  - content: "Which of the following Event Grid built-in roles is appropriate for managing Event Grid resources?"
+    choices:
+    - content: "Event Grid Contributor"
+      isCorrect: true
+      explanation: "Correct. The Event Grid Contributor role has permissions to manage resources."
+    - content: "Event Grid Subscription Contributor"
+      isCorrect: false
+      explanation: "Incorrect. The Event Grid Subscription Contributor role has permissions to manage subscription operations."
+    - content: "Event Grid Data Sender"
+      isCorrect: false
+      explanation: "Incorrect. The Event Grid Data Sender role has permissions to send events to topics."
+  - content: "What is the purpose of the CloudEvents schema in Azure Event Grid?"
+    choices:
+    - content: "To provide a proprietary event schema specific to Azure services."
+      isCorrect: false
+      explanation: "Incorrect. The CloudEvents schema is an open specification, not proprietary to Azure."
+    - content: "To simplify interoperability by providing a common event schema for publishing and consuming cloud-based events."
+      isCorrect: true
+      explanation: "Correct. The CloudEvents schema enables uniform tooling and easier integration across platforms."
+    - content: "To replace the Event Grid event schema entirely for all event types."
+      isCorrect: false
+      explanation: "Incorrect. The CloudEvents schema complements the Event Grid schema but does not replace it."
+  - content: "What happens when Event Grid receives a 400 (Bad Request) or 413 (Request Entity Too Large) response code during event delivery?"
+    choices:
+    - content: "Event Grid retries the delivery indefinitely until the endpoint responds."
+      isCorrect: false
+      explanation: "Incorrect. Event Grid does not retry indefinitely for these error codes."
+    - content: "Event Grid schedules the event for dead-lettering if a dead-letter location is configured."
+      isCorrect: true
+      explanation: "Correct. These error codes indicate delivery failure, prompting dead-lettering if configured."
+    - content: "Event Grid immediately drops the event without further action."
+      isCorrect: false
+      explanation: "Incorrect. Event Grid does not drop the event immediately; it schedules it for dead-lettering if configured."
+  - content: "What is the purpose of the validation handshake in Azure Event Grid when using a custom webhook endpoint?"
+    choices:
+    - content: "To prove ownership of the webhook endpoint before delivering events"
+      isCorrect: true
+      explanation: "Correct. The validation handshake ensures that only the rightful owner receives events."
+    - content: "To ensure the webhook endpoint is hosted on Azure infrastructure"
+      isCorrect: false
+      explanation: "Incorrect. The validation handshake does not verify the hosting location of the endpoint."
+    - content: "To encrypt the event data being sent to the webhook endpoint"
+      isCorrect: false
+      explanation: "Incorrect. The validation handshake is not related to encryption of event data."

learn-pr/wwl-azure/azure-event-grid/includes/4-event-grid-delivery-retry.md

@@ -19,7 +19,7 @@ The following table describes the types of endpoints and errors for which retry
 > [!IMPORTANT]
 > If Dead-Letter isn't configured for an endpoint, events are dropped when the above errors happen. Consider configuring Dead-Letter if you don't want these kinds of events to be dropped.
 
-If the error returned by the subscribed endpoint isn't among the previous list, Event Grid waits 30 seconds for a response after delivering a message. After 30 seconds, if the endpoint fails to responded, the message is queued for retry. Event Grid uses an exponential backoff retry policy for event delivery. 
+If the error returned by the subscribed endpoint isn't among the previous list, Event Grid waits 30 seconds for a response after delivering a message. After 30 seconds, if the endpoint fails to respond, the message is queued for retry. Event Grid uses an exponential backoff retry policy for event delivery. 
 
 If the endpoint responds within 3 minutes, Event Grid attempts to remove the event from the retry queue on a best effort basis but duplicates might still be received. Event Grid adds a small randomization to all retry steps and might opportunistically skip certain retries if an endpoint is consistently unhealthy, down for a long period, or appears to be overwhelmed.
 

learn-pr/wwl-azure/azure-event-grid/includes/8-event-grid-custom-events.md

@@ -20,12 +20,11 @@ To complete the exercise you need:
 
 ## Get started
 
-Select the **Launch Exercise** button, it opens the exercise instructions in a new browser window. When you're finished with the exercise, return here for:
+Select the **Launch Exercise** button to open the exercise instructions in a new browser window. When you're finished with the exercise, return here to:
 
 > [!div class="checklist"]
-> * A quick assessment 
-> * A summary of what you've learned
-> * A badge for completing this module
+> * Complete the module
+> * Earn a badge for completing this module
 
 <br/>