Start here! Get your feet wet with the Microsoft cloud and begin your journey to earning your Microsoft Certified: Azure Fundamentals certification!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An organization wants to track cloud spending across departments and projects by using Azure tags. To prevent human errors and ensure tagging consistency across all cloud deployments, the governance team needs to implement a standardized tagging strategy.
Which practice should the organization adopt to implement and maintain an effective tagging strategy?
Create separate resource groups for every department and avoid applying any metadata tags to individual resources
Define standardized tag naming conventions and use Azure Policy to automatically audit and enforce required tags across resources
Rely exclusively on manual tag entry in the Azure portal and delegate naming decisions to individual resource owners
Apply resource locks at the subscription level to restrict administrators from modifying existing tag values
Create separate resource groups for every department and avoid applying any metadata tags to individual resources
Define standardized tag naming conventions and use Azure Policy to automatically audit and enforce required tags across resources
A tagging strategy establishes a comprehensive taxonomy of metadata (key-value pairs) attached to Azure resources to support cost accounting, resource management, and operational governance. Combining a formal naming taxonomy with Azure Policy allows organizations to automate governance rules, ensuring resources conform to required tagging schemas without relying solely on manual processes.
StudyCerts
StudyCertsEnvironment, Department, and CostCenter) and allowed value formats prevents naming collisions, casing discrepancies (like dept vs. Department), and missing attributes.modify or append effects).Manual tagging is inherently prone to typos, omissions, and inconsistency. Automating tag enforcement through Azure Policy guarantees organizational alignment, maintains continuous compliance, and ensures cost allocation reporting is reliable and comprehensive.
Rely exclusively on manual tag entry in the Azure portal and delegate naming decisions to individual resource owners
Apply resource locks at the subscription level to restrict administrators from modifying existing tag values