A data governance lead wants to know which BigQuery datasets and tables consume the most logical and physical storage, so that cleanup work can be targeted. Which built-in source provides this view?
Show answer and explanation
Answer: B
BigQuery's INFORMATION_SCHEMA storage views, such as TABLE_STORAGE, report bytes per table in logical and physical form, which shows where space is used. Cost attribution across projects comes from Cloud Billing exports, which pair naturally with those views. Query history and table names contain no size figures, and IAM bindings describe access rather than storage.
Why the other options are wrong
- A. Query history shows who ran what, not how many bytes the tables hold. It cannot identify which tables are taking up storage.
- C. Listing table names gives no size information at all. Alphabetical order does not reveal which tables are large or expensive to keep.
- D. IAM bindings show which principals can access a dataset. They say nothing about the storage consumed by its tables.