A data engineering team needs the most granular billing data AWS can provide, with hourly line items for every resource and usage type, delivered automatically to Amazon S3 so the team can load it into Amazon Athena and Amazon QuickSight for custom cost analysis. The built-in console views do not expose enough detail for the queries they want to run. Which AWS feature should the architect enable?
- AEnable cost allocation tags and export the activated tag list to Amazon S3 so the team can load the most granular hourly line items into Athena and QuickSight.
- BEnable AWS Budgets reports and have them delivered to Amazon S3 so the team can load the most granular hourly line items into Athena and QuickSight for analysis.
- CEnable the AWS Cost and Usage Report delivered to Amazon S3 so the team can load the most granular hourly line items into Athena and QuickSight for analysis. Correct
- DSchedule AWS Cost Explorer exports to Amazon S3 so the team can load the most granular hourly line items into Athena and QuickSight for their custom analysis.
Why A is wrong: Cost allocation tags only add labelling dimensions to cost data and do not by themselves produce hourly line-item files in S3, so they cannot supply the granular dataset the team needs to query.
Why B is wrong: Budgets reports summarise spend against thresholds and lack hourly resource-level line items, so the dataset delivered would be far too coarse for the custom queries the team intends to run.
Why C is correct: The Cost and Usage Report is the most detailed billing dataset, with hourly per-resource line items written to S3 and ready for Athena and QuickSight, which is precisely the granular custom analysis requested.
Why D is wrong: Cost Explorer is an interactive console with summarised data and limited exports, so it does not deliver the hourly resource-level line items to S3 that the team requires for detailed querying.