Bitzu

AZ-305 ยท Governance and compliance design

Resource tagging strategy

Tag taxonomy (cost center, environment, owner), tag limits and non-inheritance by default, enforcing and inheriting tags with Azure Policy, using tags in cost reports.

Key points

  • Tags: name=value metadata on resources, resource groups, subscriptions (not management groups).
  • Limits: 50 pairs; name up to 512 characters (128 on storage accounts), value up to 256.
  • Names case-insensitive, values case-sensitive.
  • NOT inherited: use Azure Policy modify, e.g. 'Inherit a tag from the resource group if missing', plus a remediation task.
  • Appear in cost data; plain text, so never secrets.

Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tag-resources

Practice questions

Single choice

What is the maximum number of tag name-value pairs on a single Azure resource, resource group or subscription?

  1. 15
  2. 50
  3. 100
  4. 512
Show answer

Answer: B. 50

The general limit is 50 pairs. 15 applies only to a few resource types such as Azure Automation, and 512 is the tag name length limit, not a pair count.

Select all that apply

Which statements about Azure tags are true?

  1. Tags on a subscription are not applied to its resources automatically
  2. Tag values are case-sensitive
  3. Tags can be applied to management groups
  4. Tags are encrypted, so they can store connection strings
  5. Tags can be used to group costs in billing data
Show answer

Answer: A. Tags on a subscription are not applied to its resources automatically, B. Tag values are case-sensitive, E. Tags can be used to group costs in billing data

Subscription tags are not pushed down to resources, tag values are case-sensitive, and tags appear in billing and cost data where they can group usage. Management groups cannot be tagged, and tags are plain text that can leak through cost reports and logs, so they must never hold secrets.

True or false

Adding the tag Environment=Prod to a resource group automatically adds the same tag to every resource inside it.

Show answer

Answer: False

False. Resources do not inherit tags from their resource group or subscription. Inheritance has to be implemented with Azure Policy, for example a modify-effect inherit-tag definition.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More AZ-305 topics in this module