Tags can be used to allocate costs and generate billing reports, Not every Azure resource type supports tagging, and Tag values are treated as case sensitive when stored are correct.

Tags can be used to allocate costs and generate billing reports is correct because Azure Cost Management and billing tools let you filter and group costs by tags so you can attribute spending to teams projects or cost centers. Using tags consistently enables more accurate cost reporting and automated chargeback or showback workflows.

Not every Azure resource type supports tagging is correct because some resource providers and specific resource types do not implement tag support. Tags are widely supported for most resource types but you must verify support for particular services and child resources before relying on tags for organization.

Tag values are treated as case sensitive when stored is correct because Azure preserves the letter case you provide for tag values in the resource metadata. That means stored values retain their case and can be distinct when case differs.

Tags applied at a resource group level automatically propagate to each resource in that group is incorrect because tags do not automatically inherit from a resource group to its contained resources. You can apply tags at the resource group level for convenience but propagation requires manual application automation or an Azure Policy to copy tags to resources.

All Azure resource types accept tags is incorrect because not every resource type accepts tags. Some services or older resource types do not support tagging and you should consult the documentation for each resource provider.

Tag values are compared without regard to letter case is incorrect because comparisons can be affected by case since Azure stores tag values with their original letter case. You should not assume case insensitive comparison for tag values when you build filtering or automation logic.

Full AWS Practitioner Certification Question