BigQuery charges for data storage based on the amount of data stored. Which of the following best describes how BigQuery pricing works for storage?
Think about how cloud storage usually charges based on data size and duration.
BigQuery charges for storage based on the amount of data stored per month. There are different rates for active storage (recently modified data) and long-term storage (data not modified for 90 days), making option C correct.
Consider this BigQuery SQL query:
SELECT COUNT(*) AS total_rows FROM `bigquery-public-data.samples.shakespeare` WHERE word = 'cloud';
What does this query return?
Look at the WHERE clause filtering on the word column.
The query counts rows where the word column equals 'cloud'. It does not count all rows or unique words, and the table name is valid.
You run many small queries daily on a dataset. Which BigQuery pricing model helps minimize your cost?
Consider which pricing model offers predictable costs for frequent queries.
Flat-rate pricing lets you buy dedicated query capacity (slots) for predictable costs, which is better for frequent small queries than on-demand pricing.
A user tries to run a query on a BigQuery table they do not have access to. What is the expected behavior?
Think about how access control works in cloud services.
BigQuery enforces access control strictly. Users without permission get a permission denied error and cannot run the query.
You have a large dataset in BigQuery that is queried infrequently. Which approach best optimizes cost?
Think about storage costs and query efficiency for large datasets.
Partitioning tables and relying on long-term storage for older data reduces storage costs and improves query efficiency for infrequent queries.