An on-premises TCO workshop lists rack space and generator maintenance among current costs. How should those items be categorized for cloud economics?
Select an answer to reveal the explanation.
Short Explanation
Rack space and generator maintenance are classic “keep the building alive” costs. When you leave that basement datacenter, those facility burdens often shrink. They are TCO reality, not mystery cloud line items.
Full Explanation
Rack space and generator maintenance are facility-related on-premises costs that often shrink after migrating away from a self-run datacenter. In a TCO workshop those line items belong in the facilities/ops burden column that cloud adoption can reduce when workloads leave the municipal machine room.
They are not AWS data-transfer fees that appear only after every workload is serverless. They are not mandatory CloudFront charges unrelated to any physical facility. They are not software license SKUs that cannot exist outside SaaS catalogs.
Exam caveat: Classify power/space/generator/rack labor as on-premises facilities costs in TCO contrasts. Operational check: pull facilities invoices tied to the room hosting migrating apps, mark which costs end after decommission, and keep residual shared-building costs honest if the room is not fully vacated.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.
Municipal teams should keep a one-page decision record linking this Cloud Practitioner concept to resident outcomes, revisit it after major traffic or compliance changes, and ensure runbooks still match the chosen design.