Cloud Cost Allocation & Tagging Flashcards
7 cards from real FINOPS practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Cloud Cost Allocation & Tagging flashcards as text
What is the difference between 'showback' and 'chargeback' in FinOps cost allocation?
Answer: Showback reports costs to teams for awareness without financial transfer; chargeback actually bills teams for their usage
Showback provides visibility into costs without moving money, while chargeback transfers the actual financial liability to the consuming team or business unit.
When distributing shared infrastructure costs (e.g., a shared Kubernetes cluster) across teams, which allocation method is most commonly recommended?
Answer: Use a proportional split based on each team's actual resource consumption metrics
Proportional allocation based on measured consumption (CPU, memory, requests) ensures teams are held accountable for the resources they actually use.
Which cloud provider native tool helps AWS users allocate costs using tag-based groupings and filters?
Answer: AWS Cost Explorer with cost allocation tags
AWS Cost Explorer with activated cost allocation tags allows users to filter, group, and report spend by tag key-value pairs for detailed attribution.
What is a 'virtual tag' or 'tag mapping' capability used for in FinOps platforms?
Answer: To assign cost categories to resources retroactively without modifying the actual resource tags
Virtual tags or tag mappings allow FinOps teams to apply cost groupings retroactively in reporting tools, compensating for missing or inconsistent tags without changing live infrastructure.
Which of the following is a best practice for enforcing tagging compliance?
Answer: Use cloud policies or infrastructure-as-code guardrails to block or flag resource creation without required tags
Automated policy enforcement (e.g., AWS SCPs, Azure Policy, GCP Organization Policies, or IaC linting) prevents untagged resources from being created in the first place.
In a multi-cloud environment, what is the biggest challenge for a unified cost allocation strategy?
Answer: Each cloud provider has different tagging schemas, limits, and billing dimensions that must be normalized
Each cloud provider uses different conventions for tags, billing hierarchies, and metadata, requiring normalization before a consistent allocation view can be built.
What is the FinOps recommended approach when a resource cannot be tagged (e.g., some managed services or data transfer charges)?
Answer: Use proportional allocation rules or account/subscription-level attribution to distribute those costs
When direct tagging is impossible, FinOps practitioners use account-level attribution or proportional distribution rules to ensure no spend falls outside the allocation model.