bug fixed

Author: DivyaGundreddy

learn-pr/wwl-azure/run-governed-ai-workloads-microsoft-foundry/5-knowledge-check.yml

@@ -35,14 +35,15 @@ quiz:
     - content: "Azure service updates changed default logging behavior; create an incident ticket for developers to manually restore logging on affected endpoints."
       isCorrect: false
       explanation: "Manual post-deployment changes causing drift is the most common cause, and autoremediation directly addresses it by automatically restoring compliant configurations. Changing policy enforcement mode to 'Deny' (option 2) prevents future violations but doesn't remediate existing drift—the 15 endpoints would remain noncompliant. Creating manual incident tickets (option 3) is reactive and doesn't prevent recurrence. The compliance scanner's autoremediation feature detects drift and automatically reapplies policy requirements, eliminating administrative overhead and closing the compliance gap within minutes rather than waiting for manual intervention."
-  - content: "Your development teams complain that approval workflows for experimental AI deployments take 2-3 days, slowing innovation velocity. Current policies routes all Azure OpenAI requests greater than $500 monthly cost to VP approval. Development deployments rarely exceed $1,000 monthly and have separate budget allocation from production. How should you optimize governance policies to enable faster development cycles without compromising production controls?"
+  - content: "Your development teams complain that approval workflows for experimental AI deployments take 2-3 days, slowing innovation velocity. Current policies routes all Azure OpenAI requests greater than **$500** monthly cost to VP approval. Development deployments rarely exceed **$1,000** monthly and have separate budget allocation from production. How should you optimize governance policies to enable faster development cycles without compromising production controls?"
     choices:
-    - content: "Increase the autoapproval threshold to $5,000 for all environments so both development and production teams can provision faster."
+    - content: "Increase the autoapproval threshold to **$5,000** for all environments so both development and production teams can provision faster."
       isCorrect: false
-      explanation: "Environment-specific approval thresholds balance innovation velocity with production risk management. Development environments need experimentation freedom with appropriate budget guardrails, while production requires stricter governance due to customer impact and compliance requirements. Raising thresholds universally (option 1) weakens production controls where VP oversight is necessary for risk management. Removing workflows entirely (option 2) eliminates governance visibility and creates audit gaps even with budget enforcement. The correct approach uses environment tags to apply different approval rules: development gets auto-approval under $2,000 (covering most experiments), production maintains VP approval, and budget enforcement prevents runaway costs in both environments."
+      explanation: "Environment-specific approval thresholds balance innovation velocity with production risk management. Development environments need experimentation freedom with appropriate budget guardrails, while production requires stricter governance due to customer impact and compliance requirements. Raising thresholds universally (option 1) weakens production controls where VP oversight is necessary for risk management. Removing workflows entirely (option 2) eliminates governance visibility and creates audit gaps even with budget enforcement. The correct approach uses environment tags to apply different approval rules: development gets auto-approval under **$2,000** (covering most experiments), production maintains VP approval, and budget enforcement prevents runaway costs in both environments."
     - content: "Remove approval workflows entirely for development environments and rely on budget enforcement policies to prevent overspending."
       isCorrect: false
-      explanation: "Environment-specific approval thresholds balance innovation velocity with production risk management. Development environments need experimentation freedom with appropriate budget guardrails, while production requires stricter governance due to customer impact and compliance requirements. Raising thresholds universally (option 1) weakens production controls where VP oversight is necessary for risk management. Removing workflows entirely (option 2) eliminates governance visibility and creates audit gaps even with budget enforcement. The correct approach uses environment tags to apply different approval rules: development gets auto-approval under $2,000 (covering most experiments), production maintains VP approval, and budget enforcement prevents runaway costs in both environments."
-    - content: "Create environment-specific policies where development environments autoapprove requests under $2,000 monthly cost while production maintains VP approval for all deployments."
+      explanation: "Environment-specific approval thresholds balance innovation velocity with production risk management. Development environments need experimentation freedom with appropriate budget guardrails, while production requires stricter governance due to customer impact and compliance requirements. Raising thresholds universally (option 1) weakens production controls where VP oversight is necessary for risk management. Removing workflows entirely (option 2) eliminates governance visibility and creates audit gaps even with budget enforcement. The correct approach uses environment tags to apply different approval rules: development gets auto-approval under **$2,000** (covering most experiments), production maintains VP approval, and budget enforcement prevents runaway costs in both environments."
+    - content: "Create environment-specific policies where development environments autoapprove requests under **$2,000** monthly cost while production maintains VP approval for all deployments."
       isCorrect: true
-      explanation: "Environment-specific approval thresholds balance innovation velocity with production risk management. Development environments need experimentation freedom with appropriate budget guardrails, while production requires stricter governance due to customer impact and compliance requirements. Raising thresholds universally (option 1) weakens production controls where VP oversight is necessary for risk management. Removing workflows entirely (option 2) eliminates governance visibility and creates audit gaps even with budget enforcement. The correct approach uses environment tags to apply different approval rules: development gets auto-approval under $2,000 (covering most experiments), production maintains VP approval, and budget enforcement prevents runaway costs in both environments."
+      explanation: "Environment-specific approval thresholds balance innovation velocity with production risk management. Development environments need experimentation freedom with appropriate budget guardrails, while production requires stricter governance due to customer impact and compliance requirements. Raising thresholds universally (option 1) weakens production controls where VP oversight is necessary for risk management. Removing workflows entirely (option 2) eliminates governance visibility and creates audit gaps even with budget enforcement. The correct approach uses environment tags to apply different approval rules: development gets auto-approval under **$2,000** (covering most experiments), production maintains VP approval, and budget enforcement prevents runaway costs in both environments."
+