An Azure subscription contains several existing storage accounts that do not have secure transfer enabled. An administrator who is assigned the Owner role at the subscription level applies a new Azure Policy to the subscription. The policy uses a 'Deny' effect to prevent the creation of storage accounts that have secure transfer disabled. The administrator then attempts to create a new storage account with secure transfer disabled. What is the outcome of the administrator's attempt to create the new storage account, and how are the existing storage accounts affected?
- The creation of the new storage account is blocked, and the existing storage accounts remain unchanged but are marked as non-compliant in the compliance dashboard.Cevap
- BThe new storage account is successfully created because the Owner role overrides Azure Policy, and the existing storage accounts remain marked as compliant.
- CThe creation of the new storage account is blocked, and the existing storage accounts are automatically updated by Azure Policy to enable secure transfer.
- DThe creation of the new storage account is blocked, and the existing storage accounts are automatically deleted by Azure Policy to enforce compliance.
Cevap
The creation of the new storage account is blocked, and the existing storage accounts remain unchanged but are marked as non-compliant in the compliance dashboard.
The correct answer correctly states that the creation of the new storage account is blocked because Azure Policy rules apply to all resource deployment attempts, regardless of the user's RBAC roles. Furthermore, Azure Policy does not automatically alter or delete existing resources that do not comply with the newly applied policy; it merely identifies them as non-compliant in reports.
Adım Adım Çözüm
Anahtar Kavram
Azure Policy effects and compliance behavior, and its relationship with Azure Role-Based Access Control (RBAC)