A university operates AWS workloads for engineering, biology, and finance across dev and prod, needing chargeback by department and cost center plus automated cleanup of temporary lab environments. Which tagging strategy should the governance team implement to organize resources into groups for management?
Select an answer to reveal the explanation.
Short Explanation
You'll tame your campus cloud chaos like sorting laundry by color when you require department, cost-center, and environment tags everywhere. With tag policies plus Resource Groups, your bills and lab cleanups practically handle themselves.
Full Explanation
The correct strategy succeeds because it aligns all three business drivers with native AWS governance controls: department and cost-center tags enable granular chargeback and detailed billing reports for engineering, biology, and finance, environment tags distinguish dev, prod, and short-lived lab resources for automated expiration and cleanup, tag policies enforce consistent values and prevent drift at scale, and Resource Groups provide dynamic grouping for management, automation, and visibility. The alternative centered on department, project, and environment tags is operationally sound for lifecycle automation but fails financially because project does not substitute for cost-center in finance chargeback and cost allocation. The alternative centered on department, cost-center, and owner tags is strong for accountability and billing but fails operationally because owner cannot identify temporary versus persistent resources, so environment-driven cleanup cannot target labs reliably. The alternative that keeps all three required tags with tag policies but relies on Cost Explorer filters is analytically useful for reporting but fails managerially because Cost Explorer supports analysis, not operational grouping and bulk action like Resource Groups. An exam caveat is to distinguish reporting tools from management tools: Cost Explorer, Cost and Usage Reports, and detailed billing inform chargeback, while policies enforce and groups act. A practical check is to verify in the Tag Policies console that the three keys are enforced, confirm Resource Groups membership queries filter correctly on environment values, and validate a Cost Allocation Tag report splits spend by both department and cost-center before automating deletion.