Skip to content

Commit e116691

Browse files
authored
Fix explanation text for knowledge check question
1 parent d29af36 commit e116691

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

learn-pr/wwl-azure/protect-govern-ai-ready-infrastructure-azure/6-knowledge-check.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ quiz:
3131
explanation: "The first option implements least-privilege access by granting different permission levels based on environment sensitivity: Cognitive Services Contributor in development allows the team to create and configure resources for research, while Cognitive Services User in production provides read-only access for viewing configurations and consuming endpoints without modification capabilities. Separate resource groups create clear security boundaries that RBAC can enforce, preventing accidental or intentional cross-environment changes."
3232
- content: "Assign Owner role at the subscription scope to enable full development flexibility and rely on Azure Policy to prevent unauthorized production changes through approval workflows"
3333
isCorrect: false
34-
explanation: "he second option violates least-privilege principles by granting Owner role, which includes permissions to modify access controls, delete resources, and change billing settings far beyond what the research scenario requires."
34+
explanation: "The second option violates least-privilege principles by granting Owner role, which includes permissions to modify access controls, delete resources, and change billing settings far beyond what the research scenario requires."
3535
- content: "Create a custom role with wildcard permissions for all Cognitive Services operations and assign it at the resource group scope, then configure conditional access policies requiring manager approval for production resource access"
3636
isCorrect: false
37-
explanation: "The third option wildcard permissions eliminate granular control and still grant excessive access, while conditional access policies alone can't enforce resource-level permission restrictions—they control authentication and access conditions but don't replace RBAC for authorization decisions."
37+
explanation: "The third option wildcard permissions eliminate granular control and still grant excessive access, while conditional access policies alone can't enforce resource-level permission restrictions—they control authentication and access conditions but don't replace RBAC for authorization decisions."

0 commit comments

Comments
 (0)