Examkin

Question

Difficulty: MediumResource Governance: Resource Groups, Tags, and Resource Locks

An administrator creates a resource group named rg-db-migration and applies a tag named CostCenter: Migrations and a CanNotDelete resource lock to it. Within rg-db-migration, the administrator deploys an Azure SQL Database named sqldb-prod. An Azure Policy is assigned to the subscription that audits any resource lacking the CostCenter tag. In this scenario, the sqldb-prod database will be flagged as non-compliant by Azure Policy, and authorized users are prevented from deleting sqldb-prod unless the resource lock on rg-db-migration is removed.

Answer: Answer

Answer

The statement is true.
The correct evaluation shows that tags are not inherited, causing the database to be non-compliant with the auditing policy, while locks are inherited, preventing deletion of the database.

Step-by-Step Solution

1
Evaluate the tag inheritance behavior for the Azure SQL Database resource inside the resource group.
The sqldb-prod database does not inherit the CostCenter: Migrations tag from the rg-db-migration resource group.
Azure resource tags applied at the resource group level do not automatically inherit to individual child resources.
2
Determine the compliance status of the database against the assigned Azure Policy.
The sqldb-prod database is flagged as non-compliant.
The policy audits resources lacking the CostCenter tag. Since the database did not inherit the tag and does not have it explicitly applied, it lacks the required tag.
3
Evaluate the resource lock inheritance behavior for the database.
The sqldb-prod database inherits the CanNotDelete lock from the rg-db-migration resource group.
Resource locks applied at the resource group level are inherited by all child resources within that group.

Key Concept

Resource lock and tag inheritance rules in Azure governance
Rate this question

Topics

Resource Governance: Resource Groups, Tags, and Resource Locks

More questions from this topic