FinOps Cloud Cost Allocation & Tagging

Question 1

What is the primary purpose of a cloud cost allocation strategy in FinOps?

Accepted Answer

To accurately assign cloud costs to the teams, products, or business units that incur them

Answer

Cost allocation maps cloud spending to the responsible teams or products so each stakeholder can see and act on their own costs.

Question 2

Which of the following best describes a 'shared cost' in cloud cost allocation?

Accepted Answer

A cost that is split across multiple teams because they all benefit from a common resource or service

Answer

Shared costs arise from resources like networking, support plans, or logging services that benefit multiple teams and must be distributed using an agreed methodology.

Question 3

In FinOps, what is a 'tagging taxonomy'?

Accepted Answer

A governance framework defining which tags are required, their allowed values, and naming conventions

Answer

A tagging taxonomy establishes the standardized set of tag keys, values, and rules that ensure consistent cost attribution across the organization.

Question 4

Which tagging strategy is considered most effective for enabling granular cost allocation?

Accepted Answer

Applying a minimum set of mandatory tags (e.g., team, environment, project) to every resource

Answer

Mandatory tags applied to every resource ensure no spend is unallocated and provide the granularity needed for accurate chargeback or showback.

Question 5

What percentage of cloud spend that is 'untagged' or 'unallocated' is commonly targeted as an acceptable threshold by mature FinOps teams?

Accepted Answer

Less than 10%

Answer

Most FinOps practitioners target less than 10% unallocated spend as a sign of mature cost allocation; reaching near 0% is aspirational but less than 10% is the common benchmark.

FinOps - FinOps Certified Practitioner Practice Test

FinOps - FinOps Certified Practitioner Practice Test

FinOps Cloud Cost Allocation & Tagging