A company's Azure environment includes a resource group named `rg-analytics-prod`. The resource group contains an Azure Cosmos DB account named `cosmos-prod-db`.
An administrator performs the following tasks:
- Assigns a tag named `CostCenter: 4002` to `rg-analytics-prod`.
- Configures a `ReadOnly` lock named `rg-lock` on `rg-analytics-prod`.
- Configures a `CanNotDelete` lock named `db-lock` on `cosmos-prod-db`.
Which of the following describes the final governance state and administrative permissions for `cosmos-prod-db`?
- The database account does not inherit the CostCenter tag, and administrators cannot modify the database account's settings.Cevap
- BThe database account automatically inherits the CostCenter tag, and administrators can modify but not delete the database account.
- CThe database account does not inherit the CostCenter tag, and administrators can modify the database account's settings because the ReadOnly lock applies only to the resource group itself.
- DThe database account does not inherit the CostCenter tag, and subscription Owners can modify the database account because Owner permissions bypass resource locks.
Cevap
The database account does not inherit the CostCenter tag, and administrators cannot modify the database account's settings.
The correct option is that the database account does not inherit the CostCenter tag, and administrators cannot modify the database account's settings. Azure tags are not inherited from resource groups to resources. Additionally, resource locks inherit down the resource hierarchy. The ReadOnly lock applied to the resource group is inherited by the Cosmos DB account. Since a ReadOnly lock prevents all write and delete operations, administrators are blocked from modifying the settings of the Cosmos DB account, regardless of the local CanNotDelete lock.
Adım Adım Çözüm
Anahtar Kavram
Resource lock inheritance and tag non-inheritance in Azure
Tahmini Süre:1m 30s