Which of the following are some common reasons it can be harder to bill and report on Kubernetes costs? (Select Two)

Billing and reporting on Kubernetes costs are challenging primarily due to two factors. First, containerized environments are highly dynamic; containers and pods are ephemeral, scaling up and down rapidly, which complicates tracking resource consumption over a billing period. Second, Kubernetes clusters are often multi-tenant, with a single underlying node (the billable resource) running workloads for many different teams. This shared resource model means traditional one-to-one tagging strategies are insufficient for accurately allocating both direct workload costs and shared cluster costs (e.g., control plane, idle capacity, system overhead).

A. This is incorrect because Kubernetes clusters are very frequently shared among numerous teams and applications; this shared nature is a primary reason cost allocation is difficult, not the opposite.
D. This is factually incorrect. Containerized environments are significantly more dynamic and ephemeral than traditional, non-containerized virtual machine environments, which is a core source of the reporting complexity.

1. Storment, J.R., Fuller, M., & Quinn, C. (2023). Cloud FinOps: Collaborative, Real-Time Cloud Financial Management (2nd ed.). O'Reilly Media.

Page 219, Chapter 10, "Managing Containers and Kubernetes": "The dynamic nature of containers makes cost allocation a challenge... A single EC2 instance might be running containers from a dozen different teams, making it difficult to determine which team is responsible for the cost of the instance." This directly supports options B and C.

2. FinOps Foundation. (n.d.). Container Cost Allocation. FinOps Foundation Framework.

Under the "Getting Started" section: "The ephemeral and dynamic nature of containers makes it difficult to allocate costs accurately. Containers can be created and destroyed in seconds, and they can be moved between hosts or nodes in a cluster." This supports option B.

Under the "Getting Started" section: "Shared cluster costs, such as the control plane, networking, and storage, can be difficult to allocate to specific teams or applications." This supports the reasoning behind option C, where simple mappings fail.