Soru

Zorluk: Çok zorResource Governance: Resource Groups, Tags, and Resource Locks

An Azure subscription contains a resource group named RG-Gov. A tag with the key-value pair Dept: Finance is applied to RG-Gov, and a ReadOnly lock is placed on the RG-Gov scope. Within RG-Gov, you deploy an Azure Storage account named store1 with no direct locks or tags.

An administrator asserts that if they query resources using the Dept: Finance tag, store1 will be included in the query results, and that they can rotate the access keys of store1 without removing the lock from RG-Gov.

Is the administrator's assertion correct?

Cevap: Cevap

Cevap

The administrator's assertion is incorrect.
The correct answer is False because tags are not inherited from resource groups to child resources, and the inherited ReadOnly lock prevents key listing and rotation operations on the storage account.

Adım Adım Çözüm

1
Evaluate tag inheritance from the resource group to the storage account.
The storage account store1 does not inherit the Dept: Finance tag.
Tags applied to an Azure resource group are not automatically inherited by the resources inside that resource group.
2
Evaluate lock inheritance from the resource group to the storage account.
The storage account store1 inherits the ReadOnly lock from RG-Gov.
Azure resource locks applied at a parent scope (resource group) propagate to all child resources within that scope.
3
Determine if key rotation is allowed under a ReadOnly lock.
Key rotation (which involves listing and regenerating keys) is blocked by the ReadOnly lock.
A ReadOnly lock restricts operations that modify the resource or use POST requests at the control plane level, including listing keys (listKeys) and regenerating keys.

Anahtar Kavram

Tags are not inherited from resource groups to child resources. Resource locks are inherited by child resources, and ReadOnly locks prevent control plane POST operations such as listing or rotating access keys.
Bu soruyu puanla