Essential Tags for Multi-Cloud Cost Allocation
If you were designing a tagging standard for a company running on AWS, GCP, and Azure, which tags would you require on every resource and why?
If you were designing a tagging standard for a company running on AWS, GCP, and Azure, which tags would you require on every resource and why?
Keep the required set small. Five tags is my baseline: environment (prod, staging, dev, sandbox), team or owner (who pays and who to call at 3am), cost-center (the accounting code finance actually uses), application or service (which product this resource belongs to), and managed-by (terraform, pulumi, manual, console). Those five answer the questions finance asks every month and give engineering enough to drive ownership. Optional but common additions: project or ticket for short-lived resources, customer for multi-tenant SaaS workloads, and data-classification for compliance. Two rules I insist on. First, pick one casing and stick to it. team=payments, Team=Payments, and TEAM=PAYMENTS are three different values to the billing system and will fragment your reports. Lowercase with hyphens is the safest across AWS, GCP, and Azure since GCP labels reject uppercase anyway. Second, fewer mandatory tags means higher compliance. If you require 15 tags, engineers will copy-paste junk values to get past the policy. Start with 3 to 5 that finance and engineering agreed on together, then add more only when you have a concrete reporting need.
This question tests whether the candidate has actually shipped a tagging policy or just read about one. Strong candidates will explain the tradeoff between completeness and compliance, mention case sensitivity and the GCP label restrictions, and talk about getting finance involved early. Watch for candidates who list 12 required tags - they usually have not had to enforce them across a real org.
Terraform default tags for AWS and shared locals for Azure and GCP
Tagging standard documented for humans
- Requiring 10+ mandatory tags and wondering why compliance is at 40 percent
- Mixing casing conventions across clouds so team=Payments and team=payments show up as two teams in reports
- Not agreeing the tag values with finance first, so cost-center codes in the cloud do not match the ones in the ERP
- Why lowercase and hyphens instead of camelCase?
- How do you handle tag sprawl when every team wants to add their own?
- What do you do when finance wants a tag that engineering cannot answer at resource creation time?
More FinOps interview questions
Also worth your time on this topic
Enforcing Tagging Policies Across Clouds
How do you actually enforce that every resource in AWS, GCP, and Azure gets the required tags? Walk me through what you would put in place.
mid
How to Set Up Cloud Cost Allocation Tags Across AWS, GCP, and Azure
A practical guide to implementing consistent cost allocation tagging strategies across multi-cloud environments for accurate chargeback and showback.
60-120 minutes
How to Set Up Cloud Cost Allocation Tags Across AWS, GCP, and Azure
A working playbook for tagging resources across AWS, GCP, and Azure so finance can finally answer which team spent what, and engineers can prove their workload is not the expensive one.